From: Steven Price <steven.price@arm.com>
To: "Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"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>,
"Robin Murphy" <robin.murphy@arm.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>
Cc: 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 v12 08/15] drm/panfrost: Move all DRM device initialisation into device_init()
Date: Fri, 2 Oct 2026 15:37:08 +0100 [thread overview]
Message-ID: <6c2953cd-ec0e-4579-ad7a-be189fa1838a@arm.com> (raw)
In-Reply-To: <20260929-claude-fixes-v12-8-62beb08de207@collabora.com>
On 29/09/2026 04:44, Adrián Larumbe wrote:
> Ideally the probe() function will do as little as possible, and all device
> initialisation and registration should happen inside the panfrost device
> subsystem, just like it's done in Panthor. This also simplifies resource
> unwinding in the error path.
>
> Do the same thing for DRM driver remove, as in, sweep most of the action
> into panfrost_device_fini(), just like we did for device probe.
>
> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
> Signed-off-by: Adrián Larumbe <adrian.larumbe@collabora.com>
Reviewed-by: Steven Price <steven.price@arm.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_device.c | 49 ++++++++++++++++++++++++++++
> drivers/gpu/drm/panfrost/panfrost_drv.c | 52 +-----------------------------
> 2 files changed, 50 insertions(+), 51 deletions(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_device.c b/drivers/gpu/drm/panfrost/panfrost_device.c
> index 9f2b1967a398..c6bf3d0663df 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_device.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_device.c
> @@ -8,6 +8,7 @@
> #include <linux/pm_domain.h>
> #include <linux/pm_runtime.h>
> #include <linux/regulator/consumer.h>
> +#include <drm/drm_drv.h>
>
> #include "panfrost_device.h"
> #include "panfrost_devfreq.h"
> @@ -228,8 +229,15 @@ static int panfrost_pm_domain_init(struct panfrost_device *pfdev)
>
> int panfrost_device_init(struct panfrost_device *pfdev)
> {
> + bool device_initialised = false;
> int err;
>
> + pfdev->comp = of_device_get_match_data(pfdev->base.dev);
> + if (!pfdev->comp)
> + return -ENODEV;
> +
> + pfdev->coherent = device_get_dma_attr(pfdev->base.dev) == DEV_DMA_COHERENT;
> +
> #ifdef CONFIG_DEBUG_FS
> mutex_init(&pfdev->debugfs.gems_lock);
> INIT_LIST_HEAD(&pfdev->debugfs.gems_list);
> @@ -291,8 +299,35 @@ int panfrost_device_init(struct panfrost_device *pfdev)
> if (err)
> goto out_perfcnt;
>
> + device_initialised = true;
> +
> + /* The reason we must manually set the PM status and usage counter is
> + * we have just powered the device up but did not go through the PM
> + * runtime resume callback, so we need to update these ourselves.
> + */
> + pm_runtime_get_noresume(pfdev->base.dev);
> + pm_runtime_set_active(pfdev->base.dev);
> + pm_runtime_mark_last_busy(pfdev->base.dev);
> + pm_runtime_enable(pfdev->base.dev);
> + pm_runtime_set_autosuspend_delay(pfdev->base.dev, 50); /* ~3 frames */
> + pm_runtime_use_autosuspend(pfdev->base.dev);
> +
> + /*
> + * Register the DRM device with the core and the connectors with
> + * sysfs
> + */
> + err = drm_dev_register(&pfdev->base, 0);
> + if (err < 0)
> + goto err_disable_rpm;
> +
> + pm_runtime_put_autosuspend(pfdev->base.dev);
> +
> return 0;
>
> +err_disable_rpm:
> + pm_runtime_dont_use_autosuspend(pfdev->base.dev);
> + pm_runtime_disable(pfdev->base.dev);
> + panfrost_gem_fini(pfdev);
> out_perfcnt:
> panfrost_perfcnt_fini(pfdev);
> out_job:
> @@ -311,11 +346,22 @@ int panfrost_device_init(struct panfrost_device *pfdev)
> panfrost_reset_fini(pfdev);
> out_pm_domain:
> panfrost_pm_domain_fini(pfdev);
> +
> + if (device_initialised) {
> + pm_runtime_set_suspended(pfdev->base.dev);
> + pm_runtime_put_noidle(pfdev->base.dev);
> + }
> +
> return err;
> }
>
> void panfrost_device_fini(struct panfrost_device *pfdev)
> {
> + pm_runtime_get_sync(pfdev->base.dev);
> +
> + pm_runtime_dont_use_autosuspend(pfdev->base.dev);
> + pm_runtime_disable(pfdev->base.dev);
> +
> panfrost_gem_fini(pfdev);
> panfrost_perfcnt_fini(pfdev);
> panfrost_jm_fini(pfdev);
> @@ -326,6 +372,9 @@ void panfrost_device_fini(struct panfrost_device *pfdev)
> panfrost_clk_fini(pfdev);
> panfrost_reset_fini(pfdev);
> panfrost_pm_domain_fini(pfdev);
> +
> + pm_runtime_set_suspended(pfdev->base.dev);
> + pm_runtime_put_noidle(pfdev->base.dev);
> }
>
> #define PANFROST_EXCEPTION(id) \
> diff --git a/drivers/gpu/drm/panfrost/panfrost_drv.c b/drivers/gpu/drm/panfrost/panfrost_drv.c
> index 907d4a14a0b5..f77780c72a1a 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_drv.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_drv.c
> @@ -830,7 +830,6 @@ static const struct drm_driver panfrost_drm_driver = {
> static int panfrost_probe(struct platform_device *pdev)
> {
> struct panfrost_device *pfdev;
> - int err;
>
> pfdev = devm_drm_dev_alloc(&pdev->dev, &panfrost_drm_driver,
> struct panfrost_device, base);
> @@ -839,50 +838,7 @@ static int panfrost_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, pfdev);
>
> - pfdev->comp = of_device_get_match_data(&pdev->dev);
> - if (!pfdev->comp)
> - return -ENODEV;
> -
> - pfdev->coherent = device_get_dma_attr(&pdev->dev) == DEV_DMA_COHERENT;
> -
> - err = panfrost_device_init(pfdev);
> - if (err) {
> - if (err != -EPROBE_DEFER)
> - dev_err(&pdev->dev, "Fatal error during GPU init\n");
> - goto err_out0;
> - }
> -
> - /* The reason we must manually set the PM status and usage counter is
> - * we have just powered the device up but did not go through the PM
> - * runtime resume callback, so we need to update these ourselves.
> - */
> - pm_runtime_get_noresume(pfdev->base.dev);
> - pm_runtime_set_active(pfdev->base.dev);
> - pm_runtime_mark_last_busy(pfdev->base.dev);
> - pm_runtime_enable(pfdev->base.dev);
> - pm_runtime_set_autosuspend_delay(pfdev->base.dev, 50); /* ~3 frames */
> - pm_runtime_use_autosuspend(pfdev->base.dev);
> -
> - /*
> - * Register the DRM device with the core and the connectors with
> - * sysfs
> - */
> - err = drm_dev_register(&pfdev->base, 0);
> - if (err < 0)
> - goto err_out1;
> -
> - pm_runtime_put_autosuspend(pfdev->base.dev);
> -
> - return 0;
> -
> -err_out1:
> - 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);
> -err_out0:
> - return err;
> + return panfrost_device_init(pfdev);
> }
>
> static void panfrost_remove(struct platform_device *pdev)
> @@ -891,13 +847,7 @@ static void panfrost_remove(struct platform_device *pdev)
>
> drm_dev_unregister(&pfdev->base);
>
> - pm_runtime_get_sync(pfdev->base.dev);
> - 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);
> -
> }
>
> static ssize_t profiling_show(struct device *dev,
>
next prev parent reply other threads:[~2026-10-02 14:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 3:44 [PATCH v12 00/15] Collection of fixes for Panfrost: Perfcnt, RPM, refactorings Adrián Larumbe
2026-09-29 3:44 ` [PATCH v12 01/15] drm/panfrost: Move shrinker initialization and unplug one level down Adrián Larumbe
2026-10-02 13:58 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 02/15] drm/panfrost: Move lock and modparam initialisations into their subsystems Adrián Larumbe
2026-10-02 14:06 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 03/15] drm/panfrost: Move debugfs initialisation to relevant subsystems Adrián Larumbe
2026-10-02 14:10 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 04/15] drm/panfrost: Skip NULL checks for clock enable/disabling Adrián Larumbe
2026-10-02 14:14 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 05/15] drm/panfrost: Consolidate device clock management and reset Adrián Larumbe
2026-10-02 14:20 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 06/15] drm/panfrost: Fix PM refcnt and autosuspend issues at device probe/remove Adrián Larumbe
2026-10-02 14:21 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 07/15] drm/panfrost: Explicitly enable MMU interrupts at device init Adrián Larumbe
2026-10-02 14:26 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 08/15] drm/panfrost: Move all DRM device initialisation into device_init() Adrián Larumbe
2026-10-02 14:37 ` Steven Price [this message]
2026-09-29 3:44 ` [PATCH v12 09/15] drm/panfrost: Add warning messages to fatal error conditions Adrián Larumbe
2026-10-02 14:59 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 10/15] drm/panfrost: Add debugfs knob for manually triggering a GPU reset Adrián Larumbe
2026-10-02 15:10 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 11/15] drm/panfrost: Move perfcnt GPU disable sequence into a helper Adrián Larumbe
2026-09-29 3:44 ` [PATCH v12 12/15] drm/panfrost: Skip cache flush/invalidate when enabling perfcnt Adrián Larumbe
2026-10-02 15:14 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 13/15] drm/panfrost: Avoid cache flush after perfcnt sample in fully coherent systems Adrián Larumbe
2026-10-02 15:28 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 14/15] drm/panfrost: Introduce a reset lock Adrián Larumbe
2026-10-02 15:34 ` Steven Price
2026-09-29 3:44 ` [PATCH v12 15/15] drm/panfrost: Fix races between perfcnt and reset sequence Adrián Larumbe
2026-10-02 15:44 ` 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=6c2953cd-ec0e-4579-ad7a-be189fa1838a@arm.com \
--to=steven.price@arm.com \
--cc=adrian.larumbe@collabora.com \
--cc=airlied@gmail.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=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®