* Sven Peter <sven@xxxxxxxxxxxxx> [210605 12:13]:
> Hi Tony,
>
> On Fri, Jun 4, 2021, at 09:43, Tony Lindgren wrote:
> > Hi,
> >
> > How about the following where you set up the gate clocks as separate
> > child nodes:
> >
> > pmgr0: clock-controller@23b700000 {
> > compatible = "apple,foo-clock-controller";
> > #clock-cells = <1>;
> > reg = <0x2 0x3b700000 0x0 0x4000>;
> >
> > clk_uart0: clock@270 {
> > compatible = "apple,t8103-gate-clock";
> > #clock-cells = <0>;
> > assigned-clock-parents = <&pmgr0 APPLE_CLK_SIO>,
> > <&pmgr0 APPLE_CLK_UART_P>;
> > // ...
> > };
> >
> > };
> >
> > Keep the clock controller still addressable by offset from base as discussed,
> > and additionally have the driver parse and set up the child node clocks.
>
> Nice, I like that one even better! We can keep the internal clocks "hidden"
> inside the parent node and only need to model the actual consumer clocks
> as separate nodes.
I guess the child nodes could also use just a clocks property above
instead of assigned-clock related properties if there are no configurable
source clock mux registers.
> Are you aware of any clock driver that implements something similar?
> I'd like to avoid reinventing the wheel if it's already been done before.
I'm only aware of a partial implementation so far :) The "offset from
clock controller base" approach has worked well for the TI clkctrl
clocks. The clkctrl gate clocks still have the SoC specific source
clock data build into the clock driver(s).
That's the Documentation/devicetree/bindings/clock/ti-clkctrl.txt
binding. For the clkctrl clocks, the SoC specific source clock data
is in drivers/clk/ti/clk-*.c files.
With the Apple dtb describing the gate clock parents, you might be
able to leave out most of the SoC specific built-in driver data
sounds like.
Regards,
Tony
