[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e2c18e3-b1ed-6361-3998-5de060d2bcf0@linaro.org>
Date: Sat, 26 Aug 2023 19:31:35 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Shenwei Wang <shenwei.wang@....com>,
Ulf Hansson <ulf.hansson@...aro.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
"imx@...ts.linux.dev" <imx@...ts.linux.dev>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 1/2] dt-bindings: power: Add regulator-pd yaml file
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.
Best regards,
Krzysztof
Powered by blists - more mailing lists