Hi, I have rebased this on top of 3.19rc1 so all the cleanups have been dropped and only the meat remains.
The first patch actually moves the per-clock data that was stored in struct clk to a new struct clk_core and adds references to it from both struct clk and struct clk_hw. struct clk is now ready to contain information that is specific to a given clk consumer. The second patch adds API for setting floor and ceiling constraints and stores that information on the per-user struct clk, which is iterable from struct clk_core. The constraints are made available to clock implementations in the determine_rate callback. A rough test module was used to test this: http://cgit.collabora.com/git/user/tomeu/linux.git/commit/?h=per-user-clk-constraints-v8&id=b29ba5cc4b952072882916a2c76d54a221a1922c http://cgit.collabora.com/git/user/tomeu/linux.git/log/?h=per-user-clk-constraints-v8 Thanks, Tomeu Tomeu Vizoso (2): clk: Make clk API return per-user struct clk instances clk: Add floor and ceiling constraints to clock rates Documentation/clk.txt | 2 + arch/arm/mach-omap2/cclock3xxx_data.c | 108 +++-- arch/arm/mach-omap2/clock.h | 11 +- arch/arm/mach-omap2/clock_common_data.c | 5 +- arch/arm/mach-omap2/dpll3xxx.c | 2 + arch/arm/mach-omap2/dpll44xx.c | 2 + arch/mips/alchemy/common/clock.c | 8 + drivers/clk/at91/clk-programmable.c | 2 + drivers/clk/bcm/clk-kona.c | 2 + drivers/clk/clk-composite.c | 9 +- drivers/clk/clk.c | 792 +++++++++++++++++++++----------- drivers/clk/clk.h | 5 + drivers/clk/clkdev.c | 80 +++- drivers/clk/hisilicon/clk-hi3620.c | 2 + drivers/clk/mmp/clk-mix.c | 2 + drivers/clk/qcom/clk-pll.c | 1 + drivers/clk/qcom/clk-rcg.c | 10 +- drivers/clk/qcom/clk-rcg2.c | 6 + drivers/clk/sunxi/clk-factors.c | 2 + drivers/clk/sunxi/clk-sun6i-ar100.c | 2 + include/linux/clk-private.h | 41 +- include/linux/clk-provider.h | 20 +- include/linux/clk.h | 28 ++ include/linux/clk/ti.h | 4 + 24 files changed, 802 insertions(+), 344 deletions(-) -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
