From: "Timur Kristóf" <timur.kristof@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>,
Rodrigo Siqueira <siqueira@igalia.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org, kernel-dev@igalia.com
Subject: Re: [PATCH v3 3/5] Documentation/gpu: Expand generic block information
Date: Tue, 21 Oct 2025 11:30:34 +0200 [thread overview]
Message-ID: <70dd27f5-a72f-4c0d-9c74-996c005655e6@gmail.com> (raw)
In-Reply-To: <CADnq5_N--t-WbwRC9fuo55cfP8p4Cc-MsdYG11rt0zqaXnkSFQ@mail.gmail.com>
On 10/20/25 22:28, Alex Deucher wrote:
> On Mon, Oct 20, 2025 at 3:56 PM Rodrigo Siqueira <siqueira@igalia.com> wrote:
>>
>> This commit expands the overall explanation about AMD GPU IPs by adding
>> more details about their interconnection. Note that this commit includes
>> a diagram that provides additional information.
>>
>> Cc: Alex Deucher <alexander.deucher@amd.com>
>> Cc: Christian König <christian.koenig@amd.com>
>> Cc: Timur Kristóf <timur.kristof@gmail.com>
>> Signed-off-by: Rodrigo Siqueira <siqueira@igalia.com>
>> ---
>> .../gpu/amdgpu/amd_overview_block.svg | 674 ++++++++++++++++++
>> Documentation/gpu/amdgpu/amdgpu-glossary.rst | 3 +
>> Documentation/gpu/amdgpu/driver-core.rst | 25 +
>> 3 files changed, 702 insertions(+)
>> create mode 100644 Documentation/gpu/amdgpu/amd_overview_block.svg
>>
>> diff --git a/Documentation/gpu/amdgpu/amd_overview_block.svg b/Documentation/gpu/amdgpu/amd_overview_block.svg
>> new file mode 100644
>> index 000000000000..8d9ae95bd9a5
>> --- /dev/null
>> +++ b/Documentation/gpu/amdgpu/amd_overview_block.svg
>
> Got a link to the diagram anywhere? These looked good at XDC.
>
The cover letter of the series has links to all the diagrams.
next prev parent reply other threads:[~2025-10-21 9:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 19:38 [PATCH v3 0/5] Expand kernel-doc with more generic details and info about ring buffers Rodrigo Siqueira
2025-10-20 19:38 ` [PATCH v3 1/5] drm/amdgpu: Expand kernel-doc in amdgpu_ring Rodrigo Siqueira
2025-10-20 20:30 ` Alex Deucher
2025-10-21 9:23 ` Timur Kristóf
2025-10-21 13:11 ` Rodrigo Siqueira
2025-10-28 13:01 ` Christian König
2025-10-20 19:38 ` [PATCH v3 2/5] Documentation/gpu: Add new glossary entries from UMR Rodrigo Siqueira
2025-10-20 20:17 ` Alex Deucher
2025-10-21 5:16 ` Lazar, Lijo
2025-10-21 13:25 ` Rodrigo Siqueira
2025-10-21 14:46 ` Alex Deucher
2025-10-28 13:10 ` Christian König
2025-10-28 14:36 ` Rodrigo Siqueira
2025-10-20 19:38 ` [PATCH v3 3/5] Documentation/gpu: Expand generic block information Rodrigo Siqueira
2025-10-20 20:28 ` Alex Deucher
2025-10-21 9:30 ` Timur Kristóf [this message]
2025-10-21 14:55 ` Rodrigo Siqueira
2025-10-21 21:34 ` Alex Deucher
2025-10-21 5:24 ` Lazar, Lijo
2025-10-20 19:38 ` [PATCH v3 4/5] Documentation/gpu: Add more information about GC Rodrigo Siqueira
2025-10-20 20:30 ` Alex Deucher
2025-10-20 19:38 ` [PATCH v3 5/5] Documentation/gpu: Add documentation about ring buffer Rodrigo Siqueira
2025-10-20 20:53 ` Alex Deucher
2025-10-21 12:52 ` [PATCH v3 0/5] Expand kernel-doc with more generic details and info about ring buffers Alex Deucher
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=70dd27f5-a72f-4c0d-9c74-996c005655e6@gmail.com \
--to=timur.kristof@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=kernel-dev@igalia.com \
--cc=siqueira@igalia.com \
/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