Hi Stephen, The plan is for both the clock and reset will be under only the memory region handle like sysctrl: system-controller@f0801000 { 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@xxxxxxxxxx> 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?