From: Alex Deucher <alexander.deucher@amd.com>
To: <amd-gfx@lists.freedesktop.org>
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [PATCH 2/4] drm/gfx11: Program DB_RING_CONTROL
Date: Fri, 26 Jun 2026 16:40:59 -0400 [thread overview]
Message-ID: <20260626204101.31172-2-alexander.deucher@amd.com> (raw)
In-Reply-To: <20260626204101.31172-1-alexander.deucher@amd.com>
This is needed to allocate occlusion counters across
both gfx pipes. No functional change since we only
use one gfx pipe at the moment (default value is 1).
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
---
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
index d171d41654980..5e7d0cd85c365 100644
--- a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
@@ -2178,6 +2178,9 @@ static void gfx_v11_0_constants_init(struct amdgpu_device *adev)
tmp = RREG32_SOC15(GC, 0, regTA_CNTL2);
adev->gfx.config.ta_cntl2_truncate_coord_mode =
REG_GET_FIELD(tmp, TA_CNTL2, TRUNCATE_COORD_MODE);
+ /* program DB_RING_CONTROL for multiple GFX pipes */
+ WREG32_FIELD15_PREREG(GC, 0, DB_RING_CONTROL, COUNTER_CONTROL,
+ (adev->gfx.me.num_pipe_per_me > 1) ? 0 : 1);
/* XXX SH_MEM regs */
/* where to put LDS, scratch, GPUVM in FSA64 space */
--
2.54.0
next prev parent reply other threads:[~2026-06-26 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 20:40 [PATCH 1/4] drm/gfx10: Program DB_RING_CONTROL Alex Deucher
2026-06-26 20:40 ` Alex Deucher [this message]
2026-06-26 20:41 ` [PATCH 3/4] drm/gfx12: " Alex Deucher
2026-06-26 20:41 ` [PATCH 4/4] drm/amdgpu/gfx11: enable gfx pipe1 hardware support Alex Deucher
2026-07-07 8:08 ` Timur Kristóf
2026-07-06 15:00 ` [PATCH 1/4] drm/gfx10: Program DB_RING_CONTROL Alex Deucher
2026-07-07 8:06 ` Timur Kristóf
2026-07-07 13:44 ` Alex Deucher
2026-07-07 15:14 ` Timur Kristóf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260626204101.31172-2-alexander.deucher@amd.com \
--to=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.