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