From: Francesco Dolcini <francesco.dolcini@toradex.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Max Krummenacher <max.oss.09@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Max Krummenacher <max.krummenacher@toradex.com>,
Linux PM list <linux-pm@vger.kernel.org>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Mark Brown <broonie@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Kevin Hilman <khilman@kernel.org>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Will Deacon <will@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/5] power: domain: Add driver for a PM domain provider which controls
Date: Tue, 26 Jul 2022 18:03:37 +0200 [thread overview]
Message-ID: <20220726160337.GA41736@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <CAPDyKFrEYCx3L94gz27Pk_=HdwA4GNGE9Lvz+HGUW0P7Qt-mBw@mail.gmail.com>
Hello Ulf and everybody,
On Wed, Jul 13, 2022 at 01:43:28PM +0200, Ulf Hansson wrote:
> On Thu, 23 Jun 2022 at 18:14, Max Krummenacher <max.oss.09@gmail.com> wrote:
> > So our plan is to explicitly handle a (shared) regulator in every
> > driver involved, adding that regulator capability for drivers not
> > already having one.
>
> Please don't! I have recently rejected a similar approach for Tegra
> platforms, which now have been converted into using the power domain
> approach.
Just to quickly re-iterate how our hardware design looks like, we do
have a single gpio that control the power of a whole board area that is
supposed to be powered-off in suspend mode, this area could contains
devices that have a proper Linux driver and some passive driver-less
components (e.g. level shifter) - the exact mix varies.
Our proposal in this series was to model this as a power domain that
could be controlled with a regulator. Krzysztof, Robin and others
clearly argued against this idea.
The other approach would be to have a single regulator shared with the
multiple devices we have there (still not clear how that would work in
case we have only driver-less passive components). This is just a
device-tree matter, maybe we would need to add support for a supply to
some device drivers.
Honestly my conclusion from this discussion is that the only viable
option is this second one, do I miss something?
> If it's a powerail that is shared between controllers (devices), used
> to keep their registers values for example, that should be modelled as
> a power domain. Moreover for power domains, we can support
> voltage/frequency (performance) scaling, which isn't really applicable
> to a plain regulator.
>
> However, if the actual powerrail fits well to be modelled as
> regulator, please go ahead. Although, in this case, the regulator must
> only be controlled behind a genpd provider's on/off callback, so you
> still need the power domain approach, rather than using the regulator
> in each driver and for each device.
Francesco
next prev parent reply other threads:[~2022-07-26 16:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 15:08 Max Krummenacher
2022-06-09 15:08 ` [PATCH v1 1/5] dt-bindings: power: Add bindings for a power domain controlled by a regulator Max Krummenacher
2022-06-10 2:57 ` Rob Herring
2022-06-15 15:19 ` Max Krummenacher
2022-06-15 17:16 ` Krzysztof Kozlowski
2022-06-14 7:23 ` Geert Uytterhoeven
2022-06-15 15:18 ` Max Krummenacher
2022-06-09 15:08 ` [PATCH v1 2/5] pm: add regulator power domain controller Max Krummenacher
2022-06-09 15:08 ` [PATCH v1 3/5] MAINTAINERS: add REGULATOR POWER DOMAIN Max Krummenacher
2022-06-09 15:08 ` [RFC PATCH v1 4/5] arm64: defconfig: Enable generic power domain controller controlling a regulator Max Krummenacher
2022-06-09 15:08 ` [RFC PATCH v1 5/5] ARM64: verdin-imx8mm: use regulator power domain to model sleep-moci Max Krummenacher
2022-06-14 7:29 ` Geert Uytterhoeven
2022-06-15 15:32 ` Max Krummenacher
2022-06-13 19:15 ` [PATCH v1 0/5] power: domain: Add driver for a PM domain provider which controls Rob Herring
2022-06-14 7:22 ` Geert Uytterhoeven
2022-06-15 16:10 ` Max Krummenacher
2022-06-15 17:15 ` Krzysztof Kozlowski
2022-06-15 17:31 ` Marcel Ziswiler
2022-06-15 17:37 ` Krzysztof Kozlowski
2022-06-15 18:13 ` Marcel Ziswiler
2022-06-15 18:48 ` Dmitry Baryshkov
2022-06-15 20:48 ` Krzysztof Kozlowski
2022-06-15 18:24 ` Robin Murphy
2022-06-15 19:12 ` Mark Brown
2022-06-15 21:14 ` Ulf Hansson
2022-06-16 12:50 ` Linus Walleij
2022-06-23 16:14 ` Max Krummenacher
2022-07-13 11:43 ` Ulf Hansson
2022-07-18 9:49 ` Linus Walleij
2022-07-26 16:03 ` Francesco Dolcini [this message]
2022-07-28 9:37 ` Ulf Hansson
2022-07-28 11:21 ` Francesco Dolcini
2022-08-26 13:50 ` Ulf Hansson
2022-09-09 14:22 ` Francesco Dolcini
2022-09-22 13:49 ` Ulf Hansson
2022-09-23 18:00 ` Krzysztof Kozlowski
2022-09-26 10:12 ` Ulf Hansson
2022-09-26 15:11 ` Krzysztof Kozlowski
2022-09-27 9:48 ` Ulf Hansson
2022-09-27 12:49 ` Geert Uytterhoeven
2022-09-27 14:26 ` Krzysztof Kozlowski
2022-09-28 7:59 ` Ulf Hansson
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=20220726160337.GA41736@francesco-nb.int.toradex.com \
--to=francesco.dolcini@toradex.com \
--cc=andrejs.cainikovs@toradex.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=max.krummenacher@toradex.com \
--cc=max.oss.09@gmail.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.org \
/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®