Quoting Maxime Ripard (2020-06-15 01:40:44) > The current firmware clock driver for the RaspberryPi can only be probed by > manually registering an associated platform_device. > > While this works fine for cpufreq where the device gets attached a clkdev > lookup, it would be tedious to maintain a table of all the devices using > one of the clocks exposed by the firmware. > > Since the DT on the other hand is the perfect place to store those > associations, make the firmware clocks driver probe-able through the device > tree so that we can represent it as a node. > > Cc: Michael Turquette <[email protected]> > Cc: [email protected] > Reviewed-by: Nicolas Saenz Julienne <[email protected]> > Reviewed-by: Stephen Boyd <[email protected]> > Tested-by: Nicolas Saenz Julienne <[email protected]> > Signed-off-by: Maxime Ripard <[email protected]> > ---
Applied to clk-next
