From: sashiko-bot@kernel.org
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v14 06/15] drm/panfrost: Fix PM refcnt and autosuspend issues at device probe/remove
Date: Fri, 09 Oct 2026 13:23:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-165626@kernel.org> (raw)
In-Reply-To: <20261009-claude-fixes-v14-6-cb743b3b973b@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] drm/panfrost: fatal bus fault on pm_runtime_get_sync() failure during teardown
--
commit b75b37397a751cf9b55bbc2c3a99131de6b299ec
Author: Adrián Larumbe <adrian.larumbe@collabora.com>
drm/panfrost: Fix PM refcnt and autosuspend issues at device probe/remove
This commit manually adjusts the PM usage counter during device probe and
removal to ensure autosuspend works correctly. It calls
pm_runtime_dont_use_autosuspend() in the wind-down path to fix devfreq
spam and job timeouts.
> diff --git a/drivers/gpu/drm/panfrost/panfrost_drv.c b/drivers/gpu/drm/panfrost/panfrost_drv.c
> --- a/drivers/gpu/drm/panfrost/panfrost_drv.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_drv.c
[ ... ]
> @@ -884,9 +892,12 @@ static void panfrost_remove(struct platform_device *pdev)
> drm_dev_unregister(&pfdev->base);
>
> pm_runtime_get_sync(pfdev->base.dev);
[Severity: High]
If pm_runtime_get_sync() fails here, could this lead to a fatal bus fault?
In panfrost_remove() in drivers/gpu/drm/panfrost/panfrost_drv.c, the return
value of pm_runtime_get_sync() is ignored. If the resume operation fails,
the device remains in a suspended state with its clocks and power domains
disabled.
The code then unconditionally calls panfrost_device_fini(), which executes
hardware teardown functions like panfrost_jm_fini(), panfrost_mmu_fini(),
and panfrost_gpu_fini(). These functions read and write MMIO registers.
Accessing unclocked or unpowered MMIO registers on ARM SoC architectures
triggers a fatal synchronous external abort (SError) or data abort, which
brings down the entire system. Should hardware register accesses be
explicitly skipped if power could not be restored?
> + pm_runtime_dont_use_autosuspend(pfdev->base.dev);
> pm_runtime_disable(pfdev->base.dev);
> panfrost_device_fini(pfdev);
> pm_runtime_set_suspended(pfdev->base.dev);
> + pm_runtime_put_noidle(pfdev->base.dev);
> +
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009-claude-fixes-v14-0-cb743b3b973b@collabora.com?part=6
next prev parent reply other threads:[~2026-10-09 13:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 12:33 [PATCH v14 00/15] Collection of fixes for Panfrost: Perfcnt, RPM, refactorings Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 01/15] drm/panfrost: Move shrinker initialization and unplug one level down Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 02/15] drm/panfrost: Move lock and modparam initialisations into their subsystems Adrián Larumbe
2026-10-09 12:55 ` sashiko-bot
2026-10-09 12:33 ` [PATCH v14 03/15] drm/panfrost: Move debugfs initialisation to relevant subsystems Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 04/15] drm/panfrost: Skip NULL checks for clock enable/disabling Adrián Larumbe
2026-10-09 13:08 ` sashiko-bot
2026-10-09 12:33 ` [PATCH v14 05/15] drm/panfrost: Consolidate device clock management and reset Adrián Larumbe
2026-10-09 13:14 ` sashiko-bot
2026-10-09 12:33 ` [PATCH v14 06/15] drm/panfrost: Fix PM refcnt and autosuspend issues at device probe/remove Adrián Larumbe
2026-10-09 13:23 ` sashiko-bot [this message]
2026-10-09 12:33 ` [PATCH v14 07/15] drm/panfrost: Explicitly enable MMU interrupts at device init Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 08/15] drm/panfrost: Move all DRM device initialisation into device_init() Adrián Larumbe
2026-10-09 13:39 ` sashiko-bot
2026-10-09 12:33 ` [PATCH v14 09/15] drm/panfrost: Warn of RPM get failure at device remove time Adrián Larumbe
2026-10-09 13:47 ` sashiko-bot
2026-10-12 11:29 ` Steven Price
2026-10-09 12:33 ` [PATCH v14 10/15] drm/panfrost: Add debugfs knob for manually triggering a GPU reset Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 11/15] drm/panfrost: Move perfcnt GPU disable sequence into a helper Adrián Larumbe
2026-10-09 12:33 ` [PATCH v14 12/15] drm/panfrost: Skip cache flush/invalidate when enabling perfcnt Adrián Larumbe
2026-10-12 11:29 ` Steven Price
2026-10-09 12:34 ` [PATCH v14 13/15] drm/panfrost: Avoid cache flush after perfcnt sample in fully coherent systems Adrián Larumbe
2026-10-09 14:25 ` sashiko-bot
2026-10-09 12:34 ` [PATCH v14 14/15] drm/panfrost: Introduce a reset lock Adrián Larumbe
2026-10-09 12:34 ` [PATCH v14 15/15] drm/panfrost: Fix races between perfcnt and reset sequence Adrián Larumbe
2026-10-09 14:39 ` sashiko-bot
2026-10-12 11:29 ` Steven Price
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=sashiko-outbox-165626@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=adrian.larumbe@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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