From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Shenwei Wang <shenwei.wang@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH 1/2] dt-bindings: power: Add regulator-pd yaml file
Date: Mon, 28 Aug 2023 12:45:20 +0200 [thread overview]
Message-ID: <8f9f24c7-c93f-4cb8-bbd2-f0a8502d5f1b@linaro.org> (raw)
In-Reply-To: <CAPDyKFro6roynXuS1caARpMK08hvARQ7mQfiJcDgCyJXiw=nzw@mail.gmail.com>
On 28/08/2023 11:59, Ulf Hansson wrote:
> On Sat, 26 Aug 2023 at 19:31, Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 25/08/2023 17:44, Shenwei Wang wrote:
>>>>
>>>> The genpd provider then needs to be a consumer of the resources it needs. In
>>>> this case a couple of regulators it seems like.
>>>>
>>>
>>> If I understood your reply correctly, it seems that the current implementation of
>>> regulator-pd is what you have described. Please correct me if I'm mistaken.
>>>
>>> The following are the diff of scu-pd and this regulator-pd.
>>>
>>> power-controller { power-controller {
>>> compatible = "fsl,imx8qxp-scu-pd", "fsl,scu-pd"; | compatible = "regulator-power-domain";
>>> #power-domain-cells = <1>; #power-domain-cells = <1>;
>>> >
>>> > regulator-number = <2>;
>>> > regulator-0-supply = <®1>;
>>> > regulator-1-supply = <®2>;
>>> }; };
>>>
>>> Are you suggesting to move the regulator-pd to the imx directory and add a company prefix
>>> to the compatible string?
>>
>> There is no such part of iMX processor as such regulator-power-domain,
>> so I don't recommend that approach. DTS nodes represent hardware, not
>> your SW layers.
>
> I would agree if this was pure SW layers, but I don't think it is. At
> least, if I have understood the earlier discussions correctly [1],
> there are certainly one or more power-domains here. The power-domains
> just happen to be powered through something that can be modelled as a
> regular regulator(s). No?
No. It was for controlling power of multiple devices, supplied by
multiple different or similar regulators, where Linux drivers for these
devices (so not even all drivers...) do not have regulator control. The
bindings for these devices allow power-domains, but not regulator.
There are no multiple power domains in the problem. Even term "power
domain" is questionable here, because we tend to look power domain as
part of SoC. Here it is some selected part of the circuitry, like few
totally independent devices which share purpose and power rails.
But more important is my first paragraph - this is purely to avoid
adding regulators to these devices.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-28 10:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 15:34 [PATCH 1/2] dt-bindings: power: Add regulator-pd yaml file Shenwei Wang
2023-08-18 15:34 ` [PATCH 2/2] genpd: regulator-pd: add regulator-pd driver Shenwei Wang
2023-08-18 20:51 ` [PATCH 1/2] dt-bindings: power: Add regulator-pd yaml file Rob Herring
2023-08-18 21:06 ` Shenwei Wang
2023-08-19 8:04 ` Krzysztof Kozlowski
2023-08-21 13:22 ` Shenwei Wang
2023-08-21 18:49 ` Rob Herring
2023-08-22 15:18 ` Shenwei Wang
2023-08-22 15:25 ` Krzysztof Kozlowski
2023-08-22 15:50 ` [EXT] " Shenwei Wang
2023-08-22 15:57 ` Krzysztof Kozlowski
2023-08-22 16:14 ` Shenwei Wang
2023-08-24 9:26 ` Ulf Hansson
2023-08-24 16:35 ` Shenwei Wang
2023-08-25 12:24 ` Ulf Hansson
2023-08-25 15:44 ` Shenwei Wang
2023-08-26 17:31 ` Krzysztof Kozlowski
2023-08-28 9:59 ` Ulf Hansson
2023-08-28 10:45 ` Krzysztof Kozlowski [this message]
2023-08-28 14:14 ` Shenwei Wang
2023-08-28 14:04 ` Shenwei Wang
2023-08-28 17:10 ` Krzysztof Kozlowski
2023-08-28 18:39 ` Shenwei Wang
2023-08-28 18:42 ` Krzysztof Kozlowski
2023-08-28 18:50 ` Shenwei Wang
2023-08-28 18:52 ` Krzysztof Kozlowski
2023-08-28 19:09 ` Shenwei Wang
2023-08-28 19:11 ` Krzysztof Kozlowski
2023-08-28 19:23 ` [EXT] " Shenwei Wang
2023-08-28 19:30 ` Krzysztof Kozlowski
2023-08-28 19:49 ` Shenwei Wang
2023-08-28 21:13 ` Rob Herring
2023-08-29 13:21 ` Shenwei Wang
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=8f9f24c7-c93f-4cb8-bbd2-f0a8502d5f1b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shenwei.wang@nxp.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).