xref: /freebsd/sys/contrib/device-tree/Bindings/clock/silabs,si570.txt (revision a03411e84728e9b267056fd31c7d1d9d1dc1b01e)
1Binding for Silicon Labs 570, 571, 598 and 599 programmable
2I2C clock generators.
3
4Reference
5This binding uses the common clock binding[1]. Details about the devices can be
6found in the data sheets[2][3].
7
8[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
9[2] Si570/571 Data Sheet
10    https://www.silabs.com/Support%20Documents/TechnicalDocs/si570.pdf
11[3] Si598/599 Data Sheet
12    https://www.silabs.com/Support%20Documents/TechnicalDocs/si598-99.pdf
13
14Required properties:
15 - compatible: Shall be one of "silabs,si570", "silabs,si571",
16			       "silabs,si598", "silabs,si599"
17 - reg: I2C device address.
18 - #clock-cells: From common clock bindings: Shall be 0.
19 - factory-fout: Factory set default frequency. This frequency is part specific.
20		 The correct frequency for the part used has to be provided in
21		 order to generate the correct output frequencies. For more
22		 details, please refer to the data sheet.
23 - temperature-stability: Temperature stability of the device in PPM. Should be
24			  one of: 7, 20, 50 or 100.
25
26Optional properties:
27 - clock-output-names: From common clock bindings. Recommended to be "si570".
28 - clock-frequency: Output frequency to generate. This defines the output
29		    frequency set during boot. It can be reprogrammed during
30		    runtime through the common clock framework.
31 - silabs,skip-recall: Do not perform NVM->RAM recall operation. It will rely
32		       on hardware loading of RAM from NVM at power on.
33
34Example:
35	si570: clock-generator@5d {
36		#clock-cells = <0>;
37		compatible = "silabs,si570";
38		temperature-stability = <50>;
39		reg = <0x5d>;
40		factory-fout = <156250000>;
41	};
42