From: Michael Riesch <michael.riesch@wolfvision.net>
To: Mark Brown <broonie@kernel.org>, Robin Murphy <robin.murphy@arm.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>,
kernel@pengutronix.de
Subject: Re: [PATCH 3/4] soc: rockchip: power-domain: Add regulator support
Date: Wed, 22 Dec 2021 14:29:23 +0100 [thread overview]
Message-ID: <73caef1d-7e55-57f5-5912-b056fff73a06@wolfvision.net> (raw)
In-Reply-To: <YcMnNXu9Iun71uCG@sirena.org.uk>
Hi Robin and Mark,
On 12/22/21 2:25 PM, Mark Brown wrote:
> On Wed, Dec 22, 2021 at 01:19:23PM +0000, Robin Murphy wrote:
>> On 2021-12-22 13:00, Mark Brown wrote:
>
>>> Does the SoC actually support the supply being completely off in
>>> operation? A lot of devices want everything powered even if idle during
>>> full operation since keeping voltage differentials smaller makes it a
>>> lot easier to design to avoid leakage current type issues at the points
>>> where the different power domains connect.
>
>> I don't know TBH - the available documentation doesn't seem to go into quite
>> that much detail.
>
> In that case I would tend to assume that unless otherwise stated it's
> safer to keep the supply enabled when everything else is enabled. It's
> the default thing and so is more likely to be what was designed for and
> less likely to result in nasty surprises.
Based on my experience with the RK3568 EVB1 the vdd_gpu supply turns
after startup if it is unused and the SoC works fine. Let's take the
energy efficient route here :-)
Best regards,
Michael
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2021-12-22 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 13:09 [PATCH 0/4] soc: rockchip: power-domain: Add regulator support Sascha Hauer
2021-12-17 13:09 ` [PATCH 1/4] soc: rockchip: power-domain: register device for each domain Sascha Hauer
2021-12-17 13:09 ` [PATCH 2/4] soc: rockchip: power-domain: Use devm_clk_bulk_get_all() Sascha Hauer
2021-12-17 13:09 ` [PATCH 3/4] soc: rockchip: power-domain: Add regulator support Sascha Hauer
2021-12-20 9:44 ` Sascha Hauer
2021-12-20 10:46 ` Robin Murphy
2021-12-20 12:56 ` Mark Brown
2021-12-20 12:53 ` Mark Brown
2021-12-22 10:40 ` Sascha Hauer
2021-12-22 12:54 ` Robin Murphy
2021-12-22 13:00 ` Mark Brown
2021-12-22 13:19 ` Robin Murphy
2021-12-22 13:25 ` Mark Brown
2021-12-22 13:29 ` Michael Riesch [this message]
2021-12-22 13:37 ` Michael Riesch
2021-12-22 13:40 ` Mark Brown
2022-02-23 8:51 ` Michael Riesch
2021-12-17 13:09 ` [PATCH 4/4] dt-bindings: power: rockchip: Add power-supply to domain nodes Sascha Hauer
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=73caef1d-7e55-57f5-5912-b056fff73a06@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=s.hauer@pengutronix.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).