From: "Sven Peter" <sven@svenpeter.dev>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
"Janne Grunau" <j@jannau.net>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
asahi@lists.linux.dev
Subject: Re: [PATCH v2] drm/simpledrm: Add support for multiple "power-domains"
Date: Tue, 19 Sep 2023 15:34:56 +0200 [thread overview]
Message-ID: <c6dd2daf-f833-4c2f-9a67-640fb2c424fc@app.fastmail.com> (raw)
In-Reply-To: <ff8e4a01-9a58-45bf-a743-08f4f6027251@suse.de>
Hi,
On Mon, Sep 18, 2023, at 09:11, Thomas Zimmermann wrote:
> Hi
>
> Am 12.09.23 um 22:22 schrieb Janne Grunau via B4 Relay:
>> From: Janne Grunau <j@jannau.net>
>>
>> Multiple power domains need to be handled explicitly in each driver. The
>> driver core can not handle it automatically since it is not aware of
>> power sequencing requirements the hardware might have. This is not a
>> problem for simpledrm since everything is expected to be powered on by
>> the bootloader. simpledrm has just ensure it remains powered on during
>> its lifetime.
>> This is required on Apple silicon M2 and M2 Pro/Max/Ultra desktop
>> systems. The HDMI output initialized by the bootloader requires keeping
>> the display controller and a DP phy power domain on.
>>
>> Signed-off-by: Janne Grunau <j@jannau.net>
>
> As a simpledrm patch:
>
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
>
> Do you want to wait for another review from someone with
> power-management expertise?
I can't claim to have a lot of genpd experience but we use very similar
code in a few other M1/M2 drivers that also require multiple power domains
to be up without any sequencing constraints. So for whatever it's worth:
Reviewed-by: Sven Peter <sven@svenpeter.dev>
Best,
Sven
next prev parent reply other threads:[~2023-09-19 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 20:22 Janne Grunau via B4 Relay
2023-09-12 20:36 ` Eric Curtin
2023-09-12 22:46 ` Neal Gompa
2023-09-18 7:11 ` Thomas Zimmermann
2023-09-19 13:34 ` Sven Peter [this message]
2023-09-19 13:50 ` Javier Martinez Canillas
2023-09-26 7:32 ` Geert Uytterhoeven
2023-09-27 11:41 ` Ulf Hansson
2023-09-25 11:35 ` Thomas Zimmermann
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=c6dd2daf-f833-4c2f-9a67-640fb2c424fc@app.fastmail.com \
--to=sven@svenpeter.dev \
--cc=airlied@gmail.com \
--cc=asahi@lists.linux.dev \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=j@jannau.net \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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®