From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: Steven Price <steven.price@arm.com>,
dri-devel@lists.freedesktop.org, kernel@collabora.com
Subject: Re: [PATCH v2 2/5] drm/panthor: Be robust against runtime PM resume failures in the suspend path
Date: Fri, 29 Nov 2024 15:45:54 +0100 [thread overview]
Message-ID: <20241129154554.3d7a18fd@collabora.com> (raw)
In-Reply-To: <dyvywyidxz5scfg4fl4oqgcpg6qvh27wvekfovoomreriqqnim@3osvn3joyfeu>
On Fri, 29 Nov 2024 13:14:58 +0000
Adrián Larumbe <adrian.larumbe@collabora.com> wrote:
> Reviewed-by: Adrian Larumbe <adrian.larumbe@collabora.com>
>
> On 28.11.2024 12:02, Boris Brezillon wrote:
> > The runtime PM resume operation is not guaranteed to succeed, but if it
> > fails, the device should be in a suspended state. Make sure we're robust
> > to resume failures in the unplug path.
> >
> > v2:
> > - Move the bit that belonged in the next commit
> > - Drop the panthor_device_unplug() changes
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
> > ---
> > drivers/gpu/drm/panthor/panthor_fw.c | 14 +++++++++-----
> > drivers/gpu/drm/panthor/panthor_gpu.c | 3 ++-
> > drivers/gpu/drm/panthor/panthor_mmu.c | 3 ++-
> > 3 files changed, 13 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/panthor/panthor_fw.c b/drivers/gpu/drm/panthor/panthor_fw.c
> > index ebf8980ca9a3..f3d3d8fbe13d 100644
> > --- a/drivers/gpu/drm/panthor/panthor_fw.c
> > +++ b/drivers/gpu/drm/panthor/panthor_fw.c
> > @@ -12,6 +12,7 @@
> > #include <linux/iosys-map.h>
> > #include <linux/mutex.h>
> > #include <linux/platform_device.h>
> > +#include <linux/pm_runtime.h>
> >
> > #include <drm/drm_drv.h>
> > #include <drm/drm_managed.h>
> > @@ -1190,11 +1191,13 @@ void panthor_fw_unplug(struct panthor_device *ptdev)
> >
> > cancel_delayed_work_sync(&ptdev->fw->watchdog.ping_work);
> >
> > - /* Make sure the IRQ handler can be called after that point. */
> > - if (ptdev->fw->irq.irq)
> > - panthor_job_irq_suspend(&ptdev->fw->irq);
> > + if (!IS_ENABLED(CONFIG_PM) || pm_runtime_active(ptdev->base.dev)) {
> > + /* Make sure the IRQ handler can be called after that point. */
>
> Did you mean 'cannot be called' ?
Oops, indeed I meant 'cannot'.
next prev parent reply other threads:[~2024-11-29 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 11:02 [PATCH v2 0/5] drm/panthor: Be robust against failures in the resume path Boris Brezillon
2024-11-28 11:02 ` [PATCH v2 1/5] drm/panthor: Preserve the result returned by panthor_fw_resume() Boris Brezillon
2024-11-29 13:11 ` Adrián Larumbe
2024-11-28 11:02 ` [PATCH v2 2/5] drm/panthor: Be robust against runtime PM resume failures in the suspend path Boris Brezillon
2024-11-29 13:14 ` Adrián Larumbe
2024-11-29 14:45 ` Boris Brezillon [this message]
2024-11-29 15:21 ` Steven Price
2024-11-28 11:02 ` [PATCH v2 3/5] drm/panthor: Ignore devfreq_{suspend, resume}_device() failures Boris Brezillon
2024-11-29 13:46 ` [PATCH v2 3/5] drm/panthor: Ignore devfreq_{suspend,resume}_device() failures Adrián Larumbe
2024-11-28 11:02 ` [PATCH v2 4/5] drm/panthor: Be robust against resume failures Boris Brezillon
2024-11-29 13:59 ` Adrián Larumbe
2024-11-29 14:44 ` Boris Brezillon
2024-11-29 15:21 ` Steven Price
2024-11-28 11:02 ` [PATCH v2 5/5] drm/panthor: Fix the fast-reset logic Boris Brezillon
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=20241129154554.3d7a18fd@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.com \
--cc=steven.price@arm.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 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.