From: Steven Price <steven.price@arm.com>
To: Philippe Simons <simons.philippe@gmail.com>,
Andre Przywara <andre.przywara@arm.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Rob Herring <robh@kernel.org>
Cc: "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>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-sunxi@lists.linux.dev,
"Jernej Škrabec" <jernej.skrabec@gmail.com>
Subject: Re: [PATCH 1/2] drm/panfrost: Add PM runtime flags
Date: Mon, 31 Mar 2025 12:02:32 +0100 [thread overview]
Message-ID: <c4620199-79da-413f-807d-f99a751c1e43@arm.com> (raw)
In-Reply-To: <edf101e3-c638-45fa-8f5d-48247b9e0c9d@gmail.com>
On 31/03/2025 11:49, Philippe Simons wrote:
>
> On 3/31/25 12:32, Steven Price wrote:
>> On 27/03/2025 12:36, Andre Przywara wrote:
>>> On Thu, 13 Mar 2025 00:23:18 +0100
>>> Philippe Simons <simons.philippe@gmail.com> wrote:
>>>
>>> Hi Rob, Boris, Steven,
>>>
>>>> When the GPU is the only device attached to a single power domain,
>>>> core genpd disable and enable it when gpu enter and leave runtime
>>>> suspend.
>>>>
>>>> Some power-domain requires a sequence before disabled,
>>>> and the reverse when enabled.
>>>>
>>>> Add PM flags for CLK and RST, and implement in
>>>> panfrost_device_runtime_suspend/resume.
>>> So some Mali configuration and integration manual I am looking at says
>>> that this sequence should be always observed, as the powerdown sequence
>>> would include disabling the clocks first, then asserting the reset, then
>>> turning the power switches off (and the inverse sequence on powerup).
>>>
>>> So should we make this unconditional, not depending on implementation
>>> specific flags?
>> I think you're right, this probably should be unconditional. My only
>> reservation is that "it works" currently and we'd need to test this
>> doesn't cause regressions on existing platforms. So unless someone with
>> a reasonable board farm is able to do that testing I think this solution
>> is reasonable. So:
>
> Should I merge both flags together then ? something like GPU_PM_RT ?
Yes, that would probably be a good idea and might simplify things a little.
Thanks,
Steve
>>
>> Reviewed-by: Steven Price <steven.price@arm.com>
>>
>>> And also I am wondering if panfrost_device_init() gets this wrong as
>>> well?
>>> As I see it enabling clock first, then reset, then pm_domain, where it
>>> should be exactly the opposite?
>> I agree, that looks very wrong - the power needs to be enabled before
>> reset is deasserted. I'm somewhat surprised we've got away with that.
>> Fancy writing a patch? ;)
>>
>> Steve
>>
>>> Cheers,
>>> Andre
>>>
>>>> Signed-off-by: Philippe Simons <simons.philippe@gmail.com>
>>>> ---
>>>> drivers/gpu/drm/panfrost/panfrost_device.c | 37 ++++++++++++++++++
>>>> ++++
>>>> drivers/gpu/drm/panfrost/panfrost_device.h | 4 +++
>>>> 2 files changed, 41 insertions(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/panfrost/panfrost_device.c b/drivers/
>>>> gpu/drm/panfrost/panfrost_device.c
>>>> index a45e4addcc19..189ad2ad2b32 100644
>>>> --- a/drivers/gpu/drm/panfrost/panfrost_device.c
>>>> +++ b/drivers/gpu/drm/panfrost/panfrost_device.c
>>>> @@ -406,11 +406,38 @@ void panfrost_device_reset(struct
>>>> panfrost_device *pfdev)
>>>> static int panfrost_device_runtime_resume(struct device *dev)
>>>> {
>>>> struct panfrost_device *pfdev = dev_get_drvdata(dev);
>>>> + int ret;
>>>> +
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_RST_ASRT)) {
>>>> + ret = reset_control_deassert(pfdev->rstc);
>>>> + if (ret)
>>>> + return ret;
>>>> + }
>>>> +
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_CLK_DIS)) {
>>>> + ret = clk_enable(pfdev->clock);
>>>> + if (ret)
>>>> + goto err_clk;
>>>> +
>>>> + if (pfdev->bus_clock) {
>>>> + ret = clk_enable(pfdev->bus_clock);
>>>> + if (ret)
>>>> + goto err_bus_clk;
>>>> + }
>>>> + }
>>>> panfrost_device_reset(pfdev);
>>>> panfrost_devfreq_resume(pfdev);
>>>> return 0;
>>>> +
>>>> +err_bus_clk:
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_CLK_DIS))
>>>> + clk_disable(pfdev->clock);
>>>> +err_clk:
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_RST_ASRT))
>>>> + reset_control_assert(pfdev->rstc);
>>>> + return ret;
>>>> }
>>>> static int panfrost_device_runtime_suspend(struct device *dev)
>>>> @@ -426,6 +453,16 @@ static int
>>>> panfrost_device_runtime_suspend(struct device *dev)
>>>> panfrost_gpu_suspend_irq(pfdev);
>>>> panfrost_gpu_power_off(pfdev);
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_CLK_DIS)) {
>>>> + if (pfdev->bus_clock)
>>>> + clk_disable(pfdev->bus_clock);
>>>> +
>>>> + clk_disable(pfdev->clock);
>>>> + }
>>>> +
>>>> + if (pfdev->comp->pm_features & BIT(GPU_PM_RT_RST_ASRT))
>>>> + reset_control_assert(pfdev->rstc);
>>>> +
>>>> return 0;
>>>> }
>>>> diff --git a/drivers/gpu/drm/panfrost/panfrost_device.h b/drivers/
>>>> gpu/drm/panfrost/panfrost_device.h
>>>> index cffcb0ac7c11..f372d4819262 100644
>>>> --- a/drivers/gpu/drm/panfrost/panfrost_device.h
>>>> +++ b/drivers/gpu/drm/panfrost/panfrost_device.h
>>>> @@ -36,10 +36,14 @@ enum panfrost_drv_comp_bits {
>>>> * enum panfrost_gpu_pm - Supported kernel power management features
>>>> * @GPU_PM_CLK_DIS: Allow disabling clocks during system suspend
>>>> * @GPU_PM_VREG_OFF: Allow turning off regulators during system
>>>> suspend
>>>> + * @GPU_PM_RT_CLK_DIS: Allow disabling clocks during system runtime
>>>> suspend
>>>> + * @GPU_PM_RST_ASRT: Allow asserting the reset control during
>>>> runtime suspend
>>>> */
>>>> enum panfrost_gpu_pm {
>>>> GPU_PM_CLK_DIS,
>>>> GPU_PM_VREG_OFF,
>>>> + GPU_PM_RT_CLK_DIS,
>>>> + GPU_PM_RT_RST_ASRT
>>>> };
>>>> struct panfrost_features {
next prev parent reply other threads:[~2025-03-31 11:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 23:23 [PATCH 0/2] drm/panfrost: Philippe Simons
2025-03-12 23:23 ` [PATCH 1/2] drm/panfrost: Add PM runtime flags Philippe Simons
2025-03-27 12:36 ` Andre Przywara
2025-03-31 10:32 ` Steven Price
2025-03-31 10:49 ` Philippe Simons
2025-03-31 11:02 ` Steven Price [this message]
2025-03-31 11:13 ` Andre Przywara
2025-03-12 23:23 ` [PATCH 2/2] drm/panfrost: add h616 compatible string Philippe Simons
2025-03-31 10:32 ` Steven Price
2025-03-31 10:57 ` Andre Przywara
2025-03-31 11:02 ` 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=c4620199-79da-413f-807d-f99a751c1e43@arm.com \
--to=steven.price@arm.com \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=simons.philippe@gmail.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