On Thu, May 04, 2023 at 05:48:20PM +0800, Changhuang Liang wrote:
> On 2023/5/4 17:36, Krzysztof Kozlowski wrote:
> > On 04/05/2023 10:43, Changhuang Liang wrote:
> >> On 2023/5/4 15:26, Krzysztof Kozlowski wrote:
> >>>> aon_syscon: syscon@17010000 {
> >>>> compatible = "starfive,jh7110-aon-syscon", "syscon", "starfive,jh7110-aon-pmu";
> >>>> reg = <0x0 0x17010000 0x0 0x1000>;
> >>>> #power-domain-cells = <1>;
> >>>> };
> >>>>
> >>>> If right? I will tell the syscon patch's owner delete the "simple-mfd" in aon_syscon node.
> >>>
> >>> Yes, but your compatibles are now wrong. Just compatible =
> >>> "starfive,jh7110-aon-syscon", "syscon".
> >>>
> >>
> >> If compatible = "starfive,jh7110-aon-syscon", "syscon". My pmu drivers need use
> >> "starfive,jh7110-aon-syscon" to match.
> >
> > And how it would even work with your proposal
> > "starfive,jh7110-aon-syscon", "syscon", "starfive,jh7110-aon-pmu"?
> >
> > Try...
> >
> >> And my pmu series will add this
> >> aon_syscon in yaml and device tree, so the syscon patch's owner don't need
> >> to add the aon_syscon in its yaml and device tree?
> >
> > I don't understand. But if you need to drop syscon, sure, drop it.
> >
>
> Yes, I think it can drop aon_syscon node in syscon patch series. And maybe my
> compatible = "starfive,jh7110-aon-pmu", "syscon"; is better.
>
> aon_syscon: syscon@17010000 {
> compatible = "starfive,jh7110-aon-pmu", "syscon";
I don't really understand why you actually need to have this compatible.
Why not keep "starfive,jh7110-aon-syscon" & register the PMU using a
software mechanism?
> reg = <0x0 0x17010000 0x0 0x1000>;
> #power-domain-cells = <1>;
> };
>
> Best regards,
> Krzysztof
^^^^^^^^^^^^^^
btw, your mailer is doing something odd with quotation.
Cheers,
Conor.
Attachment:
signature.asc
Description: PGP signature
