From: Steven Price <steven.price@arm.com>
To: Philippe Simons <simons.philippe@gmail.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>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-sunxi@lists.linux.dev,
"Andre Przywara" <andre.przywara@arm.com>,
"Jernej Škrabec" <jernej.skrabec@gmail.com>
Subject: Re: [PATCH v2 0/3] drm/panfrost: enable G31 on H616
Date: Mon, 28 Apr 2025 10:26:47 +0100 [thread overview]
Message-ID: <a7ae0472-5003-40a5-9dfa-7e279b4a611f@arm.com> (raw)
In-Reply-To: <3aea4181-427f-4859-8a89-54c139775da6@gmail.com>
On 28/04/2025 07:10, Philippe Simons wrote:
> Hi, is there any issue with this serie
Hi,
Sorry, no nothing wrong - it's just slipped through. Thanks for the
reminder. I've applied it to drm-misc-next.
Thanks,
Steve
> Thanks,
>
> Philippe
>
> On 4/3/25 07:52, Philippe Simons wrote:
>> Allwinner H616 has a dedicated power domain for its Mali G31.
>>
>> Currently after probe, the GPU is put in runtime suspend which
>> disable the power domain.
>> On first usage of GPU, the power domain enable hangs the system.
>>
>> This series adds the necessary calls to enable the clocks and
>> deasserting the reset line after the power domain enabling and
>> asserting the reset line and disabling the clocks prior to the
>> power domain disabling.
>>
>> This allows to use the Mali GPU on all Allwinner H616
>> boards and devices.
>>
>> Changelog v1 .. v2:
>> - merge flags to a single GPU_PM_RT flag
>> - reorder init/deinit powerup/down sequences according to
>> Mali manuals.
>> Link to v1:
>> https://lore.kernel.org/linux-sunxi/20250312232319.25712-1-
>> simons.philippe@gmail.com/
>>
>> Philippe Simons (3):
>> drm/panfrost: Add PM runtime flag
>> drm/panfrost: add h616 compatible string
>> drm/panfrost: reorder pd/clk/rst sequence
>>
>> drivers/gpu/drm/panfrost/panfrost_device.c | 71 ++++++++++++++++------
>> drivers/gpu/drm/panfrost/panfrost_device.h | 3 +
>> drivers/gpu/drm/panfrost/panfrost_drv.c | 8 +++
>> 3 files changed, 63 insertions(+), 19 deletions(-)
>>
>>
>> base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
>> prerequisite-patch-id: eb8a11e2b24bb282970d8b8528834dea7ee392cc
prev parent reply other threads:[~2025-04-28 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 5:52 Philippe Simons
2025-04-03 5:52 ` [PATCH v2 1/3] drm/panfrost: Add PM runtime flag Philippe Simons
2025-04-03 5:52 ` [PATCH v2 2/3] drm/panfrost: add h616 compatible string Philippe Simons
2025-04-03 5:52 ` [PATCH v2 3/3] drm/panfrost: reorder pd/clk/rst sequence Philippe Simons
2025-04-18 13:38 ` John Williams
2025-04-28 6:10 ` [PATCH v2 0/3] drm/panfrost: enable G31 on H616 Philippe Simons
2025-04-28 9:26 ` Steven Price [this message]
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=a7ae0472-5003-40a5-9dfa-7e279b4a611f@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
all inboxes | Powered by JetHome®