From: "Timur Kristóf" <timur.kristof@gmail.com>
To: amd-gfx@lists.freedesktop.org, Alexander.Deucher@amd.com,
"Natalie Vock" <natalie.vock@gmx.de>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
"Lijo Lazar" <lijo.lazar@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 1/5] drm/amdgpu: Delete SI/CIK/VI IH soft_reset() code
Date: Mon, 21 Sep 2026 12:37:43 +0200 [thread overview]
Message-ID: <RY2IRd_oQXa3Lr23bQzSrw@gmail.com> (raw)
In-Reply-To: <77bd73f2-3e33-4c78-adaa-634b381ea5b8@amd.com>
On Monday, September 7, 2026 9:43:55 AM Central European Summer Time Christian
König wrote:
> On 9/4/26 20:34, Timur Kristóf wrote:
> > The code for SI/CIK/VI IH (interrupt handler) IP blocks
> > has a soft_reset() function for each block.
> > These functions are not called from anywhere and are
> > dead code. It's unclear what the original intention
> > was or why the IH block would ever need to be reset.
> >
> > All SI/CIK/VI GPUs have been working well for
> > 10+ years without ever resetting the IH block
> > so it's time to just delete the dead code.
> >
> > Signed-off-by: Timur Kristóf <timur.kristof@gmail.com>
>
> Acked-by: Christian König <christian.koenig@amd.com> for the entire series.
>
> @Alex do you pick them up or should I?
>
> Thanks,
> Christian.
Hi Alex & Christian,
Ping. Is there anything I need to do to move forward with this series?
next prev parent reply other threads:[~2026-09-21 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:34 [PATCH 1/5] drm/amdgpu: Delete SI/CIK/VI IH soft_reset() code Timur Kristóf
2026-09-04 18:34 ` [PATCH 2/5] drm/amdgpu: Delete unimplemented " Timur Kristóf
2026-09-04 18:34 ` [PATCH 3/5] drm/amdgpu: Delete GMC v6-v7 " Timur Kristóf
2026-09-04 18:34 ` [PATCH 4/5] drm/amdgpu: Delete unimplemented GMC v9 " Timur Kristóf
2026-09-04 18:34 ` [PATCH 5/5] drm/amdgpu: Delete unimplemented DM " Timur Kristóf
2026-09-07 7:43 ` [PATCH 1/5] drm/amdgpu: Delete SI/CIK/VI IH " Christian König
2026-09-21 10:37 ` Timur Kristóf [this message]
2026-09-21 20:52 ` 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=RY2IRd_oQXa3Lr23bQzSrw@gmail.com \
--to=timur.kristof@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=lijo.lazar@amd.com \
--cc=natalie.vock@gmx.de \
--cc=tursulin@ursulin.net \
/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.