[PATCH v3 0/9] clk: samsung: Add clocks for remaining domains of Exynos5433

From: Chanwoo Choi
Date: Mon Feb 02 2015 - 19:16:24 EST


This patchset adds the support for following clock domains of Exynos5433
and clkout drvier.

Following clock domains has clocks for each IP.
- CMU_APOLLO : clocks for Cortex-A53 Quad-core processor.
- CMU_ATLAS : clocks for Cortex-A57 Quad-core processor, CoreSight and
L2 cache controller.
- CMU_MSCL : clocks for M2M (Memory to Memory) scaler and JPEG IPs.
- CMU_MFC : clocks for MFC (Multi-Format Codec) IP.
- CMU_HEVC : clocks for HEVC(High Efficiency Video Codec) decoder IP.
- CMU_ISP : clocks for FIMC-ISP/DRC/SCLC/DIS/3DNR IPs.
- CMU_CAM0 : clocks for MIPI_CSIS{0|1}/FIMC_LITE_{A|B|D}/FIMC_3AA{0|1} IPs.
- CMU_CAM1 : clocks for COrtex-A5/MIPI_CSIS2/FIMC_LITE_C/FIMC-FD IPs.

Depend on:
[PATCH v5 00/13] clk: samsung: Add the support for exynos5433 clocks
- https://lkml.org/lkml/2015/2/2/368

Changelog:

Changes from v2:
- Add input clocks information to binding document

Changes from v1:
- Use 'oscclk' clock name instead of 'fin_pll'
- Add the clock dependencies between clock domains

Chanwoo Choi (8):
clk: samsung: exynos5433: Add clocks for CMU_APOLLO domain
clk: samsung: exynos5433: Add clocks for CMU_ATLAS domain
clk: samsung: exynos5433: Add clocks for CMU_MSCL domain
clk: samsung: exynos5433: Add clocks for CMU_MFC domain
clk: samsung: exynos5433: Add clocks for CMU_HEVC domain
clk: samsung: exynos5433: Add clocks for CMU_ISP domain
clk: samsung: exynos5433: Add clocks for CMU_CAM0 domain
clk: samsung: exynos5433: Add clocks for CMU_CAM1 domain

Inha Song (1):
clk: samsung: Add CLKOUT driver support for Exynos5433 SoC.

.../devicetree/bindings/clock/exynos5433-clock.txt | 157 ++
drivers/clk/samsung/clk-exynos-clkout.c | 2 +
drivers/clk/samsung/clk-exynos5433.c | 2028 ++++++++++++++++++++
include/dt-bindings/clock/exynos5433.h | 548 +++++-
4 files changed, 2734 insertions(+), 1 deletion(-)

--
1.8.5.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/