From: Alex Deucher Date: Thu, 13 Apr 2017 18:35:02 +0000 (-0400) Subject: drm/amdgpu/gfx8: move CP_PQ_STATUS after doorbell range setting (v2) X-Git-Tag: v4.13-rc1~45^2~24^2~326 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6a124e675aa4e0b3cc6f96aca8fe2b7fd3c00ae2;p=platform%2Fkernel%2Flinux-exynos.git drm/amdgpu/gfx8: move CP_PQ_STATUS after doorbell range setting (v2) I'm not sure if the order matters, but it seems like it makes more sense to set this after the range is programmed. v2: rebase (Alex) Signed-off-by: Alex Deucher --- diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c index a9cc3d7..8a9202d 100644 --- a/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c +++ b/drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c @@ -4961,9 +4961,6 @@ static int gfx_v8_0_kiq_init_register(struct amdgpu_ring *ring) /* activate the queue */ WREG32(mmCP_HQD_ACTIVE, mqd->cp_hqd_active); - if (ring->use_doorbell) - WREG32_FIELD(CP_PQ_STATUS, DOORBELL_ENABLE, 1); - return 0; } @@ -5040,6 +5037,8 @@ static void gfx_v8_0_set_mec_doorbell_range(struct amdgpu_device *adev) WREG32(mmCP_MEC_DOORBELL_RANGE_LOWER, AMDGPU_DOORBELL_KIQ << 2); WREG32(mmCP_MEC_DOORBELL_RANGE_UPPER, AMDGPU_DOORBELL_MEC_RING7 << 2); } + /* enable doorbells */ + WREG32_FIELD(CP_PQ_STATUS, DOORBELL_ENABLE, 1); } static int gfx_v8_0_kiq_resume(struct amdgpu_device *adev)