From: Alex Deucher <alexdeucher@gmail.com>
To: Alexandre Demers <alexandre.f.demers@gmail.com>
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com
Subject: Re: [PATCH 0/4] Add and use "name" member to radeon_ring struct
Date: Wed, 13 Aug 2025 10:15:27 -0400 [thread overview]
Message-ID: <CADnq5_M8gjwe8q1ZZABOSz42RDCzDPjQGQQdQ0OxLV2BB8y38A@mail.gmail.com> (raw)
In-Reply-To: <20250813000141.105508-1-alexandre.f.demers@gmail.com>
On Tue, Aug 12, 2025 at 8:08 PM Alexandre Demers
<alexandre.f.demers@gmail.com> wrote:
>
> This series adds a "name" member to the radeon_ring structure and
> uses it instead of ring indexes in logs and std outputs. This change is
> proposed for better logs readability and ring identification as much
> for the average user as for debugging purposes.
>
> It uses the same naming convention as the one used under amdgpu for
> coherence between the two drivers.
What about the other devices supported by radeon? If you are going to
change this, it would be good to fully convert the driver.
Alex
>
> Alexandre Demers (4):
> drm/radeon: add name member to radeon_ring structure
> drm/radeon: rename ring to ring_idx in
> radeon_fence_driver_start_ring()
> drm/radeon: name rings
> drm/radeon: switch from ring->idx to ring->name for printouts
>
> drivers/gpu/drm/radeon/cik.c | 33 +++++++++++++++------
> drivers/gpu/drm/radeon/cik_sdma.c | 6 ++--
> drivers/gpu/drm/radeon/ni.c | 10 +++++--
> drivers/gpu/drm/radeon/r600.c | 8 ++---
> drivers/gpu/drm/radeon/r600_dma.c | 8 ++---
> drivers/gpu/drm/radeon/radeon.h | 1 +
> drivers/gpu/drm/radeon/radeon_fence.c | 42 ++++++++++++++-------------
> drivers/gpu/drm/radeon/radeon_ring.c | 4 +--
> drivers/gpu/drm/radeon/radeon_vce.c | 13 +++++----
> drivers/gpu/drm/radeon/si.c | 36 +++++++++++++++++------
> drivers/gpu/drm/radeon/uvd_v1_0.c | 14 ++++-----
> 11 files changed, 109 insertions(+), 66 deletions(-)
>
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-08-13 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 0:01 [PATCH 0/4] Add and use "name" member to radeon_ring struct Alexandre Demers
2025-08-13 0:01 ` [PATCH 1/4] drm/radeon: add name member to radeon_ring structure Alexandre Demers
2025-08-13 0:01 ` [PATCH 2/4] drm/radeon: rename ring to ring_idx in radeon_fence_driver_start_ring() Alexandre Demers
2025-08-13 0:01 ` [PATCH 3/4] drm/radeon: name rings Alexandre Demers
2025-08-13 0:01 ` [PATCH 4/4] drm/radeon: switch from ring->idx to ring->name for printouts Alexandre Demers
2025-08-13 0:15 ` [PATCH 4/4 - V2] " Alexandre Demers
2025-08-13 14:15 ` Alex Deucher [this message]
2025-08-13 20:56 ` [PATCH 0/4] Add and use "name" member to radeon_ring struct 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=CADnq5_M8gjwe8q1ZZABOSz42RDCzDPjQGQQdQ0OxLV2BB8y38A@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).