xref: /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/clock/ti,sci-clk.txt (revision 4882a59341e53eb6f0b4789bf948001014eff981)
1*4882a593SmuzhiyunTexas Instruments TI-SCI Clocks
2*4882a593Smuzhiyun===============================
3*4882a593Smuzhiyun
4*4882a593SmuzhiyunAll clocks on Texas Instruments' SoCs that contain a System Controller,
5*4882a593Smuzhiyunare only controlled by this entity. Communication between a host processor
6*4882a593Smuzhiyunrunning an OS and the System Controller happens through a protocol known
7*4882a593Smuzhiyunas TI-SCI[1]. This clock implementation plugs into the common clock
8*4882a593Smuzhiyunframework and makes use of the TI-SCI protocol on clock API requests.
9*4882a593Smuzhiyun
10*4882a593Smuzhiyun[1] Documentation/devicetree/bindings/arm/keystone/ti,sci.txt
11*4882a593Smuzhiyun
12*4882a593SmuzhiyunRequired properties:
13*4882a593Smuzhiyun-------------------
14*4882a593Smuzhiyun- compatible: Must be "ti,k2g-sci-clk"
15*4882a593Smuzhiyun- #clock-cells: Shall be 2.
16*4882a593Smuzhiyun  In clock consumers, this cell represents the device ID and clock ID
17*4882a593Smuzhiyun  exposed by the PM firmware. The list of valid values for the device IDs
18*4882a593Smuzhiyun  and clocks IDs for 66AK2G SoC are documented at
19*4882a593Smuzhiyun  http://processors.wiki.ti.com/index.php/TISCI#66AK2G02_Data
20*4882a593Smuzhiyun
21*4882a593SmuzhiyunExamples:
22*4882a593Smuzhiyun--------
23*4882a593Smuzhiyun
24*4882a593Smuzhiyunpmmc: pmmc {
25*4882a593Smuzhiyun	compatible = "ti,k2g-sci";
26*4882a593Smuzhiyun
27*4882a593Smuzhiyun	k2g_clks: clocks {
28*4882a593Smuzhiyun		compatible = "ti,k2g-sci-clk";
29*4882a593Smuzhiyun		#clock-cells = <2>;
30*4882a593Smuzhiyun	};
31*4882a593Smuzhiyun};
32*4882a593Smuzhiyun
33*4882a593Smuzhiyunuart0: serial@2530c00 {
34*4882a593Smuzhiyun	compatible = "ns16550a";
35*4882a593Smuzhiyun	clocks = <&k2g_clks 0x2c 0>;
36*4882a593Smuzhiyun};
37