On Thu, Feb 6, 2014 at 11:46 PM, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote: > This series reworks suspend/resume handling of Samsung clock drivers > to cover more SoC specific aspects that are beyond simple register > save and restore. The goal is to have all the suspend/resume code > that touches the clock controller in single place, which is the > clock driver. > > On Exynos4210-based Trats, Exynos4412-based Trats2 and Exynos5250-based > Arndale boards (except suspend/resume, which is broken because of > unrelated reasons): > > Tested-by: Tomasz Figa <t.figa@xxxxxxxxxxx> > > Tomasz Figa (9): > clk: exynos4: Remove remnants of non-DT support > clk: samsung: Provide common helpers for register save/restore > clk: samsung: exynos4: Move suspend/resume handling to SoC driver > clk: samsung: exynos5250: Move suspend/resume handling to SoC driver > clk: samsung: exynos5420: Move suspend/resume handling to SoC driver > clk: samsung: s3c64xx: Move suspend/resume handling to SoC driver > clk: samsung: Drop old suspend/resume code > clk: samsung: exynos4: Add remaining suspend/resume handling > ARM: EXYNOS: pm: Drop legacy Exynos4 clock suspend/resume code > > arch/arm/mach-exynos/pm.c | 148 +----------------------------- > drivers/clk/samsung/clk-exynos4.c | 172 +++++++++++++++++++++++++++++++---- > drivers/clk/samsung/clk-exynos5250.c | 49 +++++++++- > drivers/clk/samsung/clk-exynos5420.c | 49 +++++++++- > drivers/clk/samsung/clk-exynos5440.c | 2 +- > drivers/clk/samsung/clk-s3c64xx.c | 79 +++++++++++++--- > drivers/clk/samsung/clk.c | 71 ++++++--------- > drivers/clk/samsung/clk.h | 14 ++- > 8 files changed, 348 insertions(+), 236 deletions(-) Nice series! Reviewed-by: Thomas Abraham <thomas.ab@xxxxxxxxxxx> > > -- > 1.8.5.2 > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- 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
 |