[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAP6Zq1jtYAg11EDrhJtzEOM+trKSpLuSbHPOx5ON93UDtr9JVg@mail.gmail.com>
Date: Sun, 25 Feb 2024 20:06:47 +0200
From: Tomer Maimon <tmaimon77@...il.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: benjaminfair@...gle.com, joel@....id.au, krzysztof.kozlowski+dt@...aro.org,
mturquette@...libre.com, robh+dt@...nel.org, tali.perry1@...il.com,
venture@...gle.com, yuenn@...gle.com, openbmc@...ts.ozlabs.org,
linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v23 1/3] dt-bindings: clock: npcm845: Add reference 25m
clock property
Hi Stephen,
The plan is for both the clock and reset will be under only the memory
region handle like
sysctrl: system-controller@...01000 {
compatible = "syscon", "simple-mfd";
reg = <0x0 0xf0801000 0x0 0x1000>;
rstc: reset-controller {
compatible = "nuvoton,npcm845-reset";
reg = <0x0 0xf0801000 0x0 0xC4>;
#reset-cells = <2>;
nuvoton,sysgcr = <&gcr>;
};
clk: clock-controller {
compatible = "nuvoton,npcm845-clk";
#clock-cells = <1>;
clocks = <&refclk>;
clock-names = "refclk";
};
};
is it problematic?
But this commit is not related to it.
Thanks,
Tomer
On Thu, 22 Feb 2024 at 07:58, Stephen Boyd <sboyd@...nel.org> wrote:
>
> Quoting Tomer Maimon (2024-01-31 10:26:51)
> > diff --git a/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml b/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml
> > index b901ca13cd25..7060891d0c32 100644
> > --- a/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml
> > +++ b/Documentation/devicetree/bindings/clock/nuvoton,npcm845-clk.yaml
> > @@ -44,6 +54,8 @@ examples:
> > compatible = "nuvoton,npcm845-clk";
> > reg = <0x0 0xf0801000 0x0 0x1000>;
> > #clock-cells = <1>;
> > + clocks = <&refclk>;
> > + clock-names = "refclk";
>
> The driver seems to want this to be a child of the mfd syscon. Is that
> right?
Powered by blists - more mailing lists