1 This document explains only the device tree da 1 This document explains only the device tree data binding. For general
2 information about PHY subsystem refer to Docum 2 information about PHY subsystem refer to Documentation/driver-api/phy/phy.rst
3 3
4 PHY device node 4 PHY device node
5 =============== 5 ===============
6 6
7 Required Properties: 7 Required Properties:
8 #phy-cells: Number of cells in a PHY speci 8 #phy-cells: Number of cells in a PHY specifier; The meaning of all those
9 cells is defined by the bindin 9 cells is defined by the binding for the phy node. The PHY
10 provider can use the values in 10 provider can use the values in cells to find the appropriate
11 PHY. 11 PHY.
12 12
13 Optional Properties: 13 Optional Properties:
14 phy-supply: Phandle to a regulator that pr 14 phy-supply: Phandle to a regulator that provides power to the PHY. This
15 regulator will be managed duri 15 regulator will be managed during the PHY power on/off sequence.
16 16
17 For example: 17 For example:
18 18
19 phys: phy { 19 phys: phy {
20 compatible = "xxx"; 20 compatible = "xxx";
21 reg = <...>; 21 reg = <...>;
22 . 22 .
23 . 23 .
24 #phy-cells = <1>; 24 #phy-cells = <1>;
25 . 25 .
26 . 26 .
27 }; 27 };
28 28
29 That node describes an IP block (PHY provider) 29 That node describes an IP block (PHY provider) that implements 2 different PHYs.
30 In order to differentiate between these 2 PHYs 30 In order to differentiate between these 2 PHYs, an additional specifier should be
31 given while trying to get a reference to it. 31 given while trying to get a reference to it.
32 32
33 PHY user node 33 PHY user node
34 ============= 34 =============
35 35
36 Required Properties: 36 Required Properties:
37 phys : the phandle for the PHY device (used by 37 phys : the phandle for the PHY device (used by the PHY subsystem; not to be
38 confused with the Ethernet specific 'ph 38 confused with the Ethernet specific 'phy' and 'phy-handle' properties,
39 see Documentation/devicetree/bindings/n 39 see Documentation/devicetree/bindings/net/ethernet.txt for these)
40 phy-names : the names of the PHY corresponding 40 phy-names : the names of the PHY corresponding to the PHYs present in the
41 *phys* phandle 41 *phys* phandle
42 42
43 Example 1: 43 Example 1:
44 usb1: usb_otg_ss@xxx { 44 usb1: usb_otg_ss@xxx {
45 compatible = "xxx"; 45 compatible = "xxx";
46 reg = <xxx>; 46 reg = <xxx>;
47 . 47 .
48 . 48 .
49 phys = <&usb2_phy>, <&usb3_phy>; 49 phys = <&usb2_phy>, <&usb3_phy>;
50 phy-names = "usb2phy", "usb3phy"; 50 phy-names = "usb2phy", "usb3phy";
51 . 51 .
52 . 52 .
53 }; 53 };
54 54
55 This node represents a controller that uses tw 55 This node represents a controller that uses two PHYs, one for usb2 and one for
56 usb3. 56 usb3.
57 57
58 Example 2: 58 Example 2:
59 usb2: usb_otg_ss@xxx { 59 usb2: usb_otg_ss@xxx {
60 compatible = "xxx"; 60 compatible = "xxx";
61 reg = <xxx>; 61 reg = <xxx>;
62 . 62 .
63 . 63 .
64 phys = <&phys 1>; 64 phys = <&phys 1>;
65 phy-names = "usbphy"; 65 phy-names = "usbphy";
66 . 66 .
67 . 67 .
68 }; 68 };
69 69
70 This node represents a controller that uses on 70 This node represents a controller that uses one of the PHYs of the PHY provider
71 device defined previously. Note that the phy h 71 device defined previously. Note that the phy handle has an additional specifier
72 "1" to differentiate between the two PHYs. 72 "1" to differentiate between the two PHYs.
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.