mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Adrián Larumbe" <adrian.larumbe@collabora.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
	Steven Price <steven.price@arm.com>,
	 Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	 Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>,
	 Simona Vetter <simona@ffwll.ch>,
	Faith Ekstrand <faith.ekstrand@collabora.com>,
	 "Marty E. Plummer" <hanetzer@startmail.com>,
	Tomeu Vizoso <tomeu@tomeuvizoso.net>,
	 Eric Anholt <eric@anholt.net>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
	 Robin Murphy <robin.murphy@arm.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	 dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	 Collabora Kernel Team <kernel@collabora.com>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v9 10/16] drm/panfrost: Add debugfs knob for manually triggering a GPU reset
Date: Wed, 23 Sep 2026 21:22:32 +0100	[thread overview]
Message-ID: <arQzC4I98fFgVelc@sobremesa> (raw)
In-Reply-To: <20260923091010.58b8e677@fedora-21.home>

> On 23.09.2026 09:10, Boris Brezillon wrote:
> On Tue, 22 Sep 2026 20:54:11 +0100
> Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> 
> > On 14.09.2026 11:39, Boris Brezillon wrote:
> > > On Sat, 12 Sep 2026 00:28:11 +0100
> > > Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> > >   
> > > > This will be of great help when testing potential races between the GPU
> > > > reset sequence and other parts of the code accessing HW registers.
> > > > 
> > > > Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>  
> > > 
> > > Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> > > 
> > > One comment below.
> > >   
> > > > ---
> > > >  drivers/gpu/drm/panfrost/panfrost_device.c | 37 ++++++++++++++++++++++++++++++
> > > >  1 file changed, 37 insertions(+)
> > > > 
> > > > diff --git a/drivers/gpu/drm/panfrost/panfrost_device.c b/drivers/gpu/drm/panfrost/panfrost_device.c
> > > > index d75566a45392..0aee1d87a7ab 100644
> > > > --- a/drivers/gpu/drm/panfrost/panfrost_device.c
> > > > +++ b/drivers/gpu/drm/panfrost/panfrost_device.c
> > > > @@ -2,6 +2,7 @@
> > > >  /* Copyright 2018 Marty E. Plummer <hanetzer@startmail.com> */
> > > >  /* Copyright 2019 Linaro, Ltd, Rob Herring <robh@kernel.org> */
> > > >  
> > > > +#include <linux/debugfs.h>
> > > >  #include <linux/clk.h>
> > > >  #include <linux/reset.h>
> > > >  #include <linux/platform_device.h>
> > > > @@ -583,9 +584,45 @@ EXPORT_GPL_DEV_PM_OPS(panfrost_pm_ops) = {
> > > >  };
> > > >  
> > > >  #ifdef CONFIG_DEBUG_FS
> > > > +static int reset_get(void *data, u64 *val)
> > > > +{
> > > > +	struct panfrost_device *pfdev =
> > > > +		container_of(data, struct panfrost_device, base);
> > > > +
> > > > +	*val = atomic_read(&pfdev->reset.pending);
> > > > +	return 0;
> > > > +}
> > > > +
> > > > +static int reset_set(void *data, u64 val)
> > > > +{
> > > > +	struct panfrost_device *pfdev =
> > > > +		container_of(data, struct panfrost_device, base);
> > > > +	int ret = pm_runtime_get_if_active(pfdev->base.dev);
> > > > +
> > > > +	if (ret) {
> > > > +		panfrost_device_schedule_reset(pfdev);  
> > > 
> > > It feels weird to schedule a reset if the device is suspended, because
> > > a suspend/resume cycle already acts as a reset. Any particular reason
> > > you'd want to do that? If not, I'd suggest going for:  
> > 
> > That's been my goal all along, for the knob to trigger a reset only when
> > the device isn't suspended. pm_runtime_get_if_active() docs states that:
> > 
> > """
> > Increment the runtime PM usage counter of @dev if its runtime PM status is
> > %RPM_ACTIVE, in which case it returns 1. If the device is in a different
> > state, 0 is returned. -EINVAL is returned if runtime PM is disabled for the
> > device, in which case also the usage_count will remain unmodified.
> > """
> > 
> > So (ret != 0) means the device either doesn't support RPM or else it
> > was in the ACTIVE state. In both cases, that means the device is powered
> > so we can proceed with the reset. However, I only decrement the usage
> > counter when kernel RPM is enabled (ret > 1).
> 
> Okay, I see. Can we have a comment explaining that? Also, I think I
> prefer an early bail out over the extra indentation level added here.
> 
> 	if (!ret)
> 		return 0;

Will do.

> Oh, and we should probably make this knob inactive in the device removal
> path (with a disable_work()?), otherwise -EINVAL will be returned as
> soon as pm_runtime_disable() is called, and this might cause a reset to
> be scheduled, which we probably don't want, since it would interfere
> with our device_fini() logic.

I think replacing cancel_work_sync() with disable_work_sync() in panfrost_jm_fini()
should be enough to this end. In that case, both queue_work() and flush_work()
will do nothing and no PM reference will be taken, so the whole thing effective
becomes a NOP.

> > 
> > > 	if (ret <= 0)
> > > 		return ret;
> > > 
> > > 	panfrost_device_schedule_reset(pfdev);
> > > 	pm_runtime_put(pfdev->base.dev);
> > > 	return 0;
> > >   
> > > > +		flush_work(&pfdev->reset.work);
> > > > +		if (ret > 0)
> > > > +			pm_runtime_put(pfdev->base.dev);
> > > > +	}
> > > > +
> > > > +	return 0;
> > > > +}
> > > > +
> > > > +DEFINE_DEBUGFS_ATTRIBUTE(panfrost_reset_debugfs_fops,
> > > > +			 reset_get, reset_set,
> > > > +			 "0x%08llx\n");
> > > > +
> > > > +static void panfrost_reset_debugfs_init(struct drm_minor *minor)
> > > > +{
> > > > +	debugfs_create_file("reset", 0600, minor->debugfs_root,
> > > > +			    minor->dev, &panfrost_reset_debugfs_fops);
> > > > +}
> > > > +
> > > >  void panfrost_device_debugfs_init(struct drm_minor *minor)
> > > >  {
> > > >  	panfrost_gem_debugfs_init(minor);
> > > >  	panfrost_sched_debugfs_init(minor);
> > > > +	panfrost_reset_debugfs_init(minor);
> > > >  }
> > > >  #endif // CONFIG_DEBUG_FS
> > > >   
> > 
> > Adrian Larumbe


Adrian Larumbe

  reply	other threads:[~2026-09-23 20:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 23:28 [PATCH v9 00/16] Collection of fixes for Panfrost: Perfcnt, RPM, refactorings Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 01/16] drm/panfrost: Move shrinker initialization and unplug one level down Adrián Larumbe
2026-09-14  8:36   ` Boris Brezillon
2026-09-22 19:48     ` Adrián Larumbe
2026-09-23  6:58       ` Boris Brezillon
2026-09-11 23:28 ` [PATCH v9 02/16] drm/panfrost: Move lock and modparam initialisations into their subsystems Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 03/16] drm/panfrost: Move debugfs initialisation to relevant subsystems Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 04/16] drm/panfrost: Skip NULL checks for clock enable/disabling Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 05/16] drm/panfrost: Consolidate device clock management and reset Adrián Larumbe
2026-09-14  8:45   ` Boris Brezillon
2026-09-22 19:50     ` Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 06/16] drm/panfrost: Fix PM refcnt and autosuspend issues at device probe/remove Adrián Larumbe
2026-09-14  9:22   ` Boris Brezillon
2026-09-22 19:51     ` Adrián Larumbe
2026-09-23  8:00       ` Boris Brezillon
2026-09-23 20:46         ` Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 07/16] drm/panfrost: Explicitly enable MMU interrupts at device init Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 08/16] drm/panfrost: Move all DRM device initialisation into device_init() Adrián Larumbe
2026-09-14  9:31   ` Boris Brezillon
2026-09-11 23:28 ` [PATCH v9 09/16] drm/panfrost: Add warning messages to fatal error conditions Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 10/16] drm/panfrost: Add debugfs knob for manually triggering a GPU reset Adrián Larumbe
2026-09-14  9:39   ` Boris Brezillon
2026-09-22 19:54     ` Adrián Larumbe
2026-09-23  7:10       ` Boris Brezillon
2026-09-23 20:22         ` Adrián Larumbe [this message]
2026-09-11 23:28 ` [PATCH v9 11/16] drm/panfrost: Move perfcnt GPU disable sequence into a helper Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 12/16] drm/panfrost: Skip cache flush/invalidate when enabling perfcnt Adrián Larumbe
2026-09-14  9:41   ` Boris Brezillon
2026-09-11 23:28 ` [PATCH v9 13/16] drm/panfrost: Avoid cache flush after perfcnt sample in fully coherent systems Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 14/16] drm/panfrost: Introduce a reset lock Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 15/16] drm/panfrost: Fix races between perfcnt and reset sequence Adrián Larumbe
2026-09-14 10:16   ` Boris Brezillon
2026-09-23  1:39     ` Adrián Larumbe
2026-09-23  8:08       ` Boris Brezillon
2026-09-23 21:51         ` Adrián Larumbe
2026-09-11 23:28 ` [PATCH v9 16/16] drm/panfrost: Bump driver minor to reflect new DUMP IOCTL req field Adrián Larumbe
2026-09-14 10:19   ` Boris Brezillon
2026-09-22 19:54     ` Adrián Larumbe

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=arQzC4I98fFgVelc@sobremesa \
    --to=adrian.larumbe@collabora.com \
    --cc=airlied@gmail.com \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=boris.brezillon@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eric@anholt.net \
    --cc=faith.ekstrand@collabora.com \
    --cc=hanetzer@startmail.com \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=simona@ffwll.ch \
    --cc=steven.price@arm.com \
    --cc=tomeu@tomeuvizoso.net \
    --cc=tzimmermann@suse.de \
    /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

all inboxes | Powered by JetHome®