Quoting Sylwester Nawrocki (2015-06-03 09:09:39) > > The following changes since commit 20db7092e478c33a2bf5254063c51f5db6443959: > > Merge branch 'clk-next-hi6220' into clk-next (2015-05-27 22:06:42 -0700) > > are available in the git repository at: > > > git://linuxtv.org/snawrocki/samsung.git tags/clk-samsung-for-4.2 Sylwester, Pulled towards 4.2. Thanks for the pull request. One small thing: clk-next isn't considered stable. I had some stuff in there (Stephen's amba assigned-clock-rates patch) which I had to pull out (no ACK from maintainer) and it crept back in because this PR was based on top of it. No big deal because I caught it when it happened (this time). In the future I am always happy to take PRs based on -rc1 (or any -rc that is already present in clk-next). Of course if you have a dependency on stuff already merged in clk-next then just let me know. Regards, Mike > > for you to fetch changes up to e5c6fc4f271a27d5b236b5f4929bf0f2dab80a7d: > > clk: exynos5433: Add CLK_IGNORE_UNUSED flag to clocks for SMC (2015-06-02 > 14:52:12 +0200) > > ---------------------------------------------------------------- > Updates of the exynos5433 clock definitions for proper support of SMC, > DVFS of GPU and CPU big.LITTLE cores and a fix for system suspend adding > one of the clock controller's registers to save/restore list. > > ---------------------------------------------------------------- > Chanwoo Choi (1): > clk: exynos5433: Add CLK_SET_RATE_PARENT to support DVFS for big.LITTLE core > > Hyungwon Hwang (1): > clk: exynos5433: Add DIV_CPIF to the list of stored registers on suspend > > Jonghwa Lee (1): > clk: exynos5433: Add CLK_IGNORE_UNUSED flag to clocks for SMC > > Joonyoung Shim (1): > clk: exynos5433: Add clock flag to support the DVFS of GPU > > drivers/clk/samsung/clk-exynos5433.c | 81 +++++++++++++++++----------------- > 1 file changed, 40 insertions(+), 41 deletions(-) > > -- > Thanks, > Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |