From: Alexandre Demers <alexandre.f.demers@gmail.com>
To: amd-gfx@lists.freedesktop.org
Subject: [PATCH v4 0/3] Uniformize defines between DCE6, DCE8 and DCE10
Date: Sun, 9 Mar 2025 12:48:49 -0400 [thread overview]
Message-ID: <20250309164852.3936628-1-alexandre.f.demers@gmail.com> (raw)
Keep a uniform way of where and how variables are defined between
DCE6, DCE8 and DCE10. It is easier to understand the code, their
similarities and their modifications.
Since sid.h is being wired up in dce_v6_0.c, duplicated defines need to be
cleaned up in sid.h and si_enums.h.
V4:
* Reorder patches so each one compiles properly.
* Remove drm-amdgpu-add-defines-for-pin_offsets-in-DCE8.patch since it was
already approved and applied.
A bigger round of cleanup is coming to remove more of the duplicated and
unused defines found in sid.h and si_enums.h and continue the uniformization.
Alexandre Demers (3):
drm/amdgpu: fix warning and errors caused by duplicated defines in
sid.h
drm/amdgpu: move and fix X_GB_ADDR_CONFIG_GOLDEN values
drm/amdgpu: add or move defines for DCE6 in sid.h
drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 73 ++---
drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 15 +-
drivers/gpu/drm/amd/amdgpu/si.c | 68 ++---
drivers/gpu/drm/amd/amdgpu/si_enums.h | 12 -
drivers/gpu/drm/amd/amdgpu/sid.h | 369 ++------------------------
5 files changed, 111 insertions(+), 426 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-09 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-09 16:48 Alexandre Demers [this message]
2025-03-09 16:48 ` [PATCH v4 1/3] drm/amdgpu: prepare DCE6 uniformisation with DCE8 and DCE10 Alexandre Demers
2025-03-09 16:48 ` [PATCH v4 2/3] drm/amdgpu: fix SI's GB_ADDR_CONFIG_GOLDEN values and wire up sid.h in GFX6 Alexandre Demers
2025-03-09 16:48 ` [PATCH v4 3/3] drm/amdgpu: finish wiring up sid.h in DCE6 Alexandre Demers
2025-03-10 15:08 ` Alex Deucher
2025-03-09 23:51 ` [PATCH v4 0/3] Uniformize defines between DCE6, DCE8 and DCE10 Alexandre Demers
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=20250309164852.3936628-1-alexandre.f.demers@gmail.com \
--to=alexandre.f.demers@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox