Mike, On 05/06/2014 04:31 PM, Nishanth Menon wrote: > On 16:24-20140506, Peter Ujfalusi wrote: >> Hi, >> >> Changes since v1: >> - binding documentation and driver has been separated based on Nishanth Menon's >> comment Could you take a look at this series please? I really hoped that it would make it to 3.16... Thanks, Péter >> >> v1 of the driver can be found: >> https://lkml.org/lkml/2014/4/3/104 >> >> Palmas class of devices can provide 32K clock(s) to be used by other devices >> on the board. Depending on the actual device the provided clocks can be: >> CLK32K_KG and CLK32K_KGAUDIO >> or only one: >> CLK32K_KG (TPS659039 for example) >> >> Use separate compatible flags for the two 32K clock. >> A system which needs or have only one of the 32k clock from >> Palmas will need to add node(s) for each clock as separate section >> in the dts file. >> The two compatible property is: >> "ti,palmas-clk32kg" for clk32kg clock >> "ti,palmas-clk32kgaudio" for clk32kgaudio clock >> >> Apart from the register control of the clocks - which is done via >> the clock API there is a posibility to enable the external sleep >> control. In this way the clock can be enabled/disabled on demand by the >> user of the clock. >> >> Regards, >> Peter >> --- >> Peter Ujfalusi (2): >> dt/bindings: Binding documentation for Palmas clk32kg and clk32kgaudio >> clocks >> clk: Add driver for Palmas clk32kg and clk32kgaudio clocks >> >> .../bindings/clock/clk-palmas-clk32kg-clocks.txt | 35 +++ >> drivers/clk/Kconfig | 7 + >> drivers/clk/Makefile | 1 + >> drivers/clk/clk-palmas.c | 307 +++++++++++++++++++++ >> include/dt-bindings/mfd/palmas.h | 18 ++ >> 5 files changed, 368 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/clock/clk-palmas-clk32kg-clocks.txt >> create mode 100644 drivers/clk/clk-palmas.c >> create mode 100644 include/dt-bindings/mfd/palmas.h >> >> -- >> 1.9.2 >> > > Series: > Reviewed-by: Nishanth Menon <nm@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
