Re: [PATCH v6 2/3] drm/tyr: add GPU reset infrastructure

Onur Özkan <[email protected]>
Newsgroups org.kernel.vger.rust-for-linux,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Fri, 21 Aug 2026 12:31:03 -0300
Daniel Almeida <[email protected]> wrote:

> Hi Onur,
> 
> > On 19 Aug 2026, at 15:45, Onur Özkan <[email protected]> wrote:
> > 
> > Add support for scheduling GPU resets on a dedicated workqueue. Track
> > the reset state to avoid queueing another reset while one is already
> > pending or in progress.
> > 
> > Use an SRCU based gate with mutex-protected reader admission to block
> > hardware accesses while reset work runs and wait for current users
> > before resetting.
> > 
> > Stop new reset requests during teardown and drain any queued or running
> > reset work before releasing the device resources.
> > 
> > This is the initial reset infrastructure only. It is not wired to a reset
> > source yet as those will follow in separate work.
> > 
> > Link: https://gitlab.freedesktop.org/panfrost/linux/-/work_items/28
> > Signed-off-by: Onur Özkan <[email protected]>
> 
> I’d use dev_info instead, I don’t think a reset belongs in dev_dbg.

It was dev_dbg initially, Danillo said otherwise and I changed it. I have no
strong feeling on both.

Does it deserve a new version to switch back into dev_dbg again? I think we can
easily switch that when pulling this series.

> 
> Otherwise, this looks good to go from my POV.
> 
> Tested-by: Daniel Almeida <[email protected]>
> Reviewed-by: Daniel Almeida <[email protected]>

Thanks for testing and reviewing it.

Best,
Onur
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.