xref: /freebsd/sys/contrib/device-tree/Bindings/clock/rockchip,rk3128-cru.txt (revision c66ec88fed842fbaad62c30d510644ceb7bd2d71)
1*c66ec88fSEmmanuel Vadot* Rockchip RK3126/RK3128 Clock and Reset Unit
2*c66ec88fSEmmanuel Vadot
3*c66ec88fSEmmanuel VadotThe RK3126/RK3128 clock controller generates and supplies clock to various
4*c66ec88fSEmmanuel Vadotcontrollers within the SoC and also implements a reset controller for SoC
5*c66ec88fSEmmanuel Vadotperipherals.
6*c66ec88fSEmmanuel Vadot
7*c66ec88fSEmmanuel VadotRequired Properties:
8*c66ec88fSEmmanuel Vadot
9*c66ec88fSEmmanuel Vadot- compatible: should be "rockchip,rk3126-cru" or "rockchip,rk3128-cru"
10*c66ec88fSEmmanuel Vadot  "rockchip,rk3126-cru" - controller compatible with RK3126 SoC.
11*c66ec88fSEmmanuel Vadot  "rockchip,rk3128-cru" - controller compatible with RK3128 SoC.
12*c66ec88fSEmmanuel Vadot- reg: physical base address of the controller and length of memory mapped
13*c66ec88fSEmmanuel Vadot  region.
14*c66ec88fSEmmanuel Vadot- #clock-cells: should be 1.
15*c66ec88fSEmmanuel Vadot- #reset-cells: should be 1.
16*c66ec88fSEmmanuel Vadot
17*c66ec88fSEmmanuel VadotOptional Properties:
18*c66ec88fSEmmanuel Vadot
19*c66ec88fSEmmanuel Vadot- rockchip,grf: phandle to the syscon managing the "general register files"
20*c66ec88fSEmmanuel Vadot  If missing pll rates are not changeable, due to the missing pll lock status.
21*c66ec88fSEmmanuel Vadot
22*c66ec88fSEmmanuel VadotEach clock is assigned an identifier and client nodes can use this identifier
23*c66ec88fSEmmanuel Vadotto specify the clock which they consume. All available clocks are defined as
24*c66ec88fSEmmanuel Vadotpreprocessor macros in the dt-bindings/clock/rk3128-cru.h headers and can be
25*c66ec88fSEmmanuel Vadotused in device tree sources. Similar macros exist for the reset sources in
26*c66ec88fSEmmanuel Vadotthese files.
27*c66ec88fSEmmanuel Vadot
28*c66ec88fSEmmanuel VadotExternal clocks:
29*c66ec88fSEmmanuel Vadot
30*c66ec88fSEmmanuel VadotThere are several clocks that are generated outside the SoC. It is expected
31*c66ec88fSEmmanuel Vadotthat they are defined using standard clock bindings with following
32*c66ec88fSEmmanuel Vadotclock-output-names:
33*c66ec88fSEmmanuel Vadot - "xin24m" - crystal input - required,
34*c66ec88fSEmmanuel Vadot - "ext_i2s" - external I2S clock - optional,
35*c66ec88fSEmmanuel Vadot - "gmac_clkin" - external GMAC clock - optional
36*c66ec88fSEmmanuel Vadot
37*c66ec88fSEmmanuel VadotExample: Clock controller node:
38*c66ec88fSEmmanuel Vadot
39*c66ec88fSEmmanuel Vadot	cru: cru@20000000 {
40*c66ec88fSEmmanuel Vadot		compatible = "rockchip,rk3128-cru";
41*c66ec88fSEmmanuel Vadot		reg = <0x20000000 0x1000>;
42*c66ec88fSEmmanuel Vadot		rockchip,grf = <&grf>;
43*c66ec88fSEmmanuel Vadot
44*c66ec88fSEmmanuel Vadot		#clock-cells = <1>;
45*c66ec88fSEmmanuel Vadot		#reset-cells = <1>;
46*c66ec88fSEmmanuel Vadot	};
47*c66ec88fSEmmanuel Vadot
48*c66ec88fSEmmanuel VadotExample: UART controller node that consumes the clock generated by the clock
49*c66ec88fSEmmanuel Vadot  controller:
50*c66ec88fSEmmanuel Vadot
51*c66ec88fSEmmanuel Vadot	uart2: serial@20068000 {
52*c66ec88fSEmmanuel Vadot		compatible = "rockchip,serial";
53*c66ec88fSEmmanuel Vadot		reg = <0x20068000 0x100>;
54*c66ec88fSEmmanuel Vadot		interrupts = <GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>;
55*c66ec88fSEmmanuel Vadot		clock-frequency = <24000000>;
56*c66ec88fSEmmanuel Vadot		clocks = <&cru SCLK_UART2>, <&cru PCLK_UART2>;
57*c66ec88fSEmmanuel Vadot		clock-names = "sclk_uart", "pclk_uart";
58*c66ec88fSEmmanuel Vadot	};
59