From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org
Cc: Marek Vasut <marex@denx.de>,
Boris Brezillon <boris.brezillon@collabora.com>,
Conor Dooley <conor+dt@kernel.org>,
David Airlie <airlied@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Sebastian Reichel <sre@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Simona Vetter <simona@ffwll.ch>,
Steven Price <steven.price@arm.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
imx@lists.linux.dev, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH 5/9] drm/panthor: Implement support for multiple power domains
Date: Fri, 28 Feb 2025 11:10:02 +0100 [thread overview]
Message-ID: <2848587.BEx9A2HvPv@steina-w> (raw)
In-Reply-To: <20250227170012.124768-6-marex@denx.de>
Am Donnerstag, 27. Februar 2025, 17:58:05 CET schrieb Marek Vasut:
> The driver code power domain binding to driver instances only works
> for single power domain, in case there are multiple power domains,
> it is necessary to explicitly attach via dev_pm_domain_attach*().
> As DT bindings list support for up to 5 power domains, add support
> for attaching them all. This is useful on Freescale i.MX95 which
> does have two power domains.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Boris Brezillon <boris.brezillon@collabora.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: David Airlie <airlied@gmail.com>
> Cc: Fabio Estevam <festevam@gmail.com>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <mripard@kernel.org>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Sebastian Reichel <sre@kernel.org>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Simona Vetter <simona@ffwll.ch>
> Cc: Steven Price <steven.price@arm.com>
> Cc: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: devicetree@vger.kernel.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: imx@lists.linux.dev
> Cc: linux-arm-kernel@lists.infradead.org
> ---
> drivers/gpu/drm/panthor/panthor_device.c | 56 ++++++++++++++++++++++++
> drivers/gpu/drm/panthor/panthor_device.h | 5 +++
> 2 files changed, 61 insertions(+)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_device.c b/drivers/gpu/drm/panthor/panthor_device.c
> index 51ee9cae94504..4348b7e917b64 100644
> --- a/drivers/gpu/drm/panthor/panthor_device.c
> +++ b/drivers/gpu/drm/panthor/panthor_device.c
> @@ -75,6 +75,58 @@ static int panthor_reset_init(struct panthor_device *ptdev)
> return 0;
> }
>
> +/* Generic power domain handling code, see drivers/gpu/drm/tiny/simpledrm.c */
> +static void panthor_detach_genpd(void *res)
> +{
> + struct panthor_device *ptdev = res;
> + int i;
> +
> + if (ptdev->pwr_dom_count <= 1)
> + return;
> +
> + for (i = ptdev->pwr_dom_count - 1; i >= 0; i--)
> + dev_pm_domain_detach(ptdev->pwr_dom_devs[i], true);
> +}
> +
> +static int panthor_genpd_init(struct panthor_device *ptdev)
> +{
> + struct device *dev = ptdev->base.dev;
> + int i, ret;
> +
> + ptdev->pwr_dom_count = of_count_phandle_with_args(dev->of_node, "power-domains",
> + "#power-domain-cells");
> + /*
> + * Single power-domain devices are handled by driver core nothing to do
> + * here. The same for device nodes without "power-domains" property.
> + */
> + if (ptdev->pwr_dom_count <= 1)
> + return 0;
> +
> + if (ptdev->pwr_dom_count > ARRAY_SIZE(ptdev->pwr_dom_devs)) {
> + drm_warn(&ptdev->base, "Too many power domains (%d) for this device\n",
> + ptdev->pwr_dom_count);
> + return -EINVAL;
> + }
> +
> + for (i = 0; i < ptdev->pwr_dom_count; i++) {
> + ptdev->pwr_dom_devs[i] = dev_pm_domain_attach_by_id(dev, i);
> + if (!IS_ERR(ptdev->pwr_dom_devs[i]))
> + continue;
> +
> + ret = PTR_ERR(ptdev->pwr_dom_devs[i]);
> + if (ret != -EPROBE_DEFER) {
> + drm_warn(&ptdev->base, "pm_domain_attach_by_id(%u) failed: %d\n", i, ret);
> + continue;
Is it a good idea to continue if a power-domain is missing? Any access might
stuck completely. IMHO returning an error is more sensible.
Also some dev_err_probe() should be added here.
Best regards
Alexander
> + }
> +
> + /* Missing dependency, try again. */
> + panthor_detach_genpd(ptdev);
> + return ret;
> + }
> +
> + return devm_add_action_or_reset(dev, panthor_detach_genpd, ptdev);
> +}
> +
> void panthor_device_unplug(struct panthor_device *ptdev)
> {
> /* This function can be called from two different path: the reset work
> @@ -232,6 +284,10 @@ int panthor_device_init(struct panthor_device *ptdev)
> if (ret)
> return ret;
>
> + ret = panthor_genpd_init(ptdev);
> + if (ret)
> + return ret;
> +
> ret = panthor_devfreq_init(ptdev);
> if (ret)
> return ret;
> diff --git a/drivers/gpu/drm/panthor/panthor_device.h b/drivers/gpu/drm/panthor/panthor_device.h
> index fea3a05778e2e..7fb65447253e9 100644
> --- a/drivers/gpu/drm/panthor/panthor_device.h
> +++ b/drivers/gpu/drm/panthor/panthor_device.h
> @@ -114,6 +114,11 @@ struct panthor_device {
> /** @resets: GPU reset. */
> struct reset_control *resets;
>
> + /** @pwr_dom_count: Power domain count */
> + int pwr_dom_count;
> + /** @pwr_dom_dev: Power domain devices */
> + struct device *pwr_dom_devs[5];
> +
> /** @coherent: True if the CPU/GPU are memory coherent. */
> bool coherent;
>
>
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2025-02-28 10:13 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 16:58 [PATCH 0/9] arm64: dts: imx95: Add support for Mali G310 GPU Marek Vasut
2025-02-27 16:58 ` [PATCH 1/9] dt-bindings: reset: imx95-gpu-blk-ctrl: Document Freescale i.MX95 GPU reset Marek Vasut
2025-02-27 17:30 ` Frank Li
2025-02-27 20:22 ` Marek Vasut
2025-02-27 18:38 ` Rob Herring (Arm)
2025-02-27 16:58 ` [PATCH 2/9] reset: simple: Add support for " Marek Vasut
2025-02-27 17:32 ` Frank Li
2025-02-28 9:58 ` Alexander Stein
2025-02-28 16:43 ` Marek Vasut
2025-02-27 16:58 ` [PATCH 3/9] dt-bindings: gpu: mali-valhall-csf: Document optional reset Marek Vasut
2025-02-27 17:33 ` Frank Li
2025-02-27 18:38 ` Rob Herring (Arm)
2025-02-28 12:25 ` Rob Herring (Arm)
2025-02-27 16:58 ` [PATCH 4/9] drm/panthor: Implement " Marek Vasut
2025-02-28 10:06 ` Alexander Stein
2025-02-28 16:48 ` Marek Vasut
2025-03-01 21:45 ` kernel test robot
2025-02-27 16:58 ` [PATCH 5/9] drm/panthor: Implement support for multiple power domains Marek Vasut
2025-02-28 10:10 ` Alexander Stein [this message]
2025-02-28 17:00 ` Marek Vasut
2025-02-27 16:58 ` [PATCH 6/9] drm/panthor: Reset GPU after L2 cache power off Marek Vasut
2025-02-27 17:17 ` Boris Brezillon
2025-02-27 17:26 ` Marek Vasut
2025-02-28 11:06 ` Liviu Dudau
2025-02-28 17:05 ` Marek Vasut
2025-03-03 12:08 ` Liviu Dudau
2025-03-03 12:35 ` Boris Brezillon
2025-03-03 12:42 ` Boris Brezillon
2025-03-21 20:00 ` Marek Vasut
2025-03-21 19:54 ` Marek Vasut
2025-02-27 16:58 ` [PATCH 7/9] dt-bindings: gpu: mali-valhall-csf: Document i.MX95 support Marek Vasut
2025-02-27 17:34 ` Frank Li
2025-02-27 18:38 ` Rob Herring (Arm)
2025-02-27 20:31 ` Marek Vasut
2025-02-28 12:28 ` Rob Herring
2025-02-28 10:12 ` Alexander Stein
2025-02-28 12:30 ` Rob Herring
2025-02-28 17:17 ` Marek Vasut
2025-02-27 16:58 ` [PATCH 8/9] drm/panthor: Add " Marek Vasut
2025-02-27 17:35 ` Frank Li
2025-02-27 20:17 ` Marco Felsch
2025-02-27 20:39 ` Marek Vasut
2025-02-28 10:33 ` Marco Felsch
2025-02-28 17:20 ` Marek Vasut
2025-02-28 10:21 ` Alexander Stein
2025-02-28 11:23 ` Florent Tomasin
2025-02-28 17:26 ` Marek Vasut
2025-03-03 13:55 ` Florent Tomasin
2025-02-28 17:21 ` Marek Vasut
2025-02-27 16:58 ` [PATCH 9/9] arm64: dts: imx95: Describe Mali G310 GPU Marek Vasut
2025-02-27 17:43 ` Frank Li
2025-02-27 20:36 ` Marek Vasut
2025-02-27 21:27 ` Frank Li
2025-02-27 21:34 ` Marek Vasut
2025-02-27 22:21 ` Frank Li
2025-02-28 10:39 ` Alexander Stein
2025-02-28 17:33 ` Marek Vasut
2025-02-28 10:36 ` Alexander Stein
2025-02-28 17:43 ` Marek Vasut
2025-03-03 15:04 ` Liviu Dudau
2025-03-21 19:37 ` Marek Vasut
2025-02-28 14:23 ` [PATCH 0/9] arm64: dts: imx95: Add support for " Rob Herring (Arm)
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=2848587.BEx9A2HvPv@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=simona@ffwll.ch \
--cc=sre@kernel.org \
--cc=steven.price@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).