Clock bindings got acked and then essentially unacked, while the clock driver never made it upstream. In the meantime, the initial DTS file made it upstream. This latest patch series includes a patch to go back and correct the DTS files to reflect the new clock bindings in this patch series. This series still uses the CLK_OF_DECLARE approach despite not being regarded as the best approach. On MIPS/PIC32 the first call of clk_get() happens from "start_kernel -> time_init() -> plat_time_init()" which is very early in boot sequence even before execution of early_initcall(). In short, by platform_driver way I was not able to register clock(s) before the first clock user becomes ready. With CLK_OF_DECLARE() I can explicitly call of_clk_init() in plat_time_init() just before calling clk_get(). Purna Chandra Mandal (3): dt/bindings: Add PIC32 clock binding documentation clk: clk-pic32: Add PIC32 clock driver MIPS: dts: pic32: Update dts to reflect new PIC32MZDA clk binding .../devicetree/bindings/clock/microchip,pic32.txt | 39 + arch/mips/boot/dts/pic32/pic32mzda-clk.dtsi | 236 ----- arch/mips/boot/dts/pic32/pic32mzda.dtsi | 63 +- arch/mips/boot/dts/pic32/pic32mzda_sk.dts | 5 +- drivers/clk/Kconfig | 3 + drivers/clk/Makefile | 1 + drivers/clk/microchip/Makefile | 2 + drivers/clk/microchip/clk-core.c | 954 ++++++++++++++++++++ drivers/clk/microchip/clk-core.h | 78 ++ drivers/clk/microchip/clk-pic32mzda.c | 214 +++++ include/dt-bindings/clock/microchip,pic32-clock.h | 42 + 11 files changed, 1378 insertions(+), 259 deletions(-) create mode 100644 Documentation/devicetree/bindings/clock/microchip,pic32.txt delete mode 100644 arch/mips/boot/dts/pic32/pic32mzda-clk.dtsi create mode 100644 drivers/clk/microchip/Makefile create mode 100644 drivers/clk/microchip/clk-core.c create mode 100644 drivers/clk/microchip/clk-core.h create mode 100644 drivers/clk/microchip/clk-pic32mzda.c create mode 100644 include/dt-bindings/clock/microchip,pic32-clock.h -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
