aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorXing Zheng <zhengxing@rock-chips.com>2016-03-28 05:51:35 -0400
committerHeiko Stuebner <heiko@sntech.de>2016-03-28 08:56:57 -0400
commit485a40d7cd4aab5ae939320278809776388f5c06 (patch)
treed8e8f064ed9b35214992faa7080ae86675addd6b
parent1c234eba6219839dd75466e56cb28df08ac45edd (diff)
dt-bindings: add bindings for rk3399 clock controller
Add devicetree bindings for Rockchip cru which found on Rockchip SoCs. Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
-rw-r--r--Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt62
1 files changed, 62 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt
new file mode 100644
index 000000000000..3888dd33fcbd
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/rockchip,rk3399-cru.txt
@@ -0,0 +1,62 @@
1* Rockchip RK3399 Clock and Reset Unit
2
3The RK3399 clock controller generates and supplies clock to various
4controllers within the SoC and also implements a reset controller for SoC
5peripherals.
6
7Required Properties:
8
9- compatible: PMU for CRU should be "rockchip,rk3399-pmucru"
10- compatible: CRU should be "rockchip,rk3399-cru"
11- reg: physical base address of the controller and length of memory mapped
12 region.
13- #clock-cells: should be 1.
14- #reset-cells: should be 1.
15
16Each clock is assigned an identifier and client nodes can use this identifier
17to specify the clock which they consume. All available clocks are defined as
18preprocessor macros in the dt-bindings/clock/rk3399-cru.h headers and can be
19used in device tree sources. Similar macros exist for the reset sources in
20these files.
21
22External clocks:
23
24There are several clocks that are generated outside the SoC. It is expected
25that they are defined using standard clock bindings with following
26clock-output-names:
27 - "xin24m" - crystal input - required,
28 - "xin32k" - rtc clock - optional,
29 - "clkin_gmac" - external GMAC clock - optional,
30 - "clkin_i2s" - external I2S clock - optional,
31 - "pclkin_cif" - external ISP clock - optional,
32 - "clk_usbphy0_480m" - output clock of the pll in the usbphy0
33 - "clk_usbphy1_480m" - output clock of the pll in the usbphy1
34
35Example: Clock controller node:
36
37 pmucru: pmu-clock-controller@ff750000 {
38 compatible = "rockchip,rk3399-pmucru";
39 reg = <0x0 0xff750000 0x0 0x1000>;
40 #clock-cells = <1>;
41 #reset-cells = <1>;
42 };
43
44 cru: clock-controller@ff760000 {
45 compatible = "rockchip,rk3399-cru";
46 reg = <0x0 0xff760000 0x0 0x1000>;
47 #clock-cells = <1>;
48 #reset-cells = <1>;
49 };
50
51Example: UART controller node that consumes the clock generated by the clock
52 controller:
53
54 uart0: serial@ff1a0000 {
55 compatible = "rockchip,rk3399-uart", "snps,dw-apb-uart";
56 reg = <0x0 0xff180000 0x0 0x100>;
57 clocks = <&cru SCLK_UART0>, <&cru PCLK_UART0>;
58 clock-names = "baudclk", "apb_pclk";
59 interrupts = <GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>;
60 reg-shift = <2>;
61 reg-io-width = <4>;
62 };