1 This document explains only the device tree data binding. For general
2 information about PHY subsystem refer to Documentation/phy.txt
8 #phy-cells: Number of cells in a PHY specifier; The meaning of all those
9 cells is defined by the binding for the phy node. The PHY
10 provider can use the values in cells to find the appropriate
25 That node describes an IP block (PHY provider) that implements 2 different PHYs.
26 In order to differentiate between these 2 PHYs, an additonal specifier should be
27 given while trying to get a reference to it.
33 phys : the phandle for the PHY device (used by the PHY subsystem)
34 phy-names : the names of the PHY corresponding to the PHYs present in the
38 usb1: usb_otg_ss@xxx {
43 phys = <&usb2_phy>, <&usb3_phy>;
44 phy-names = "usb2phy", "usb3phy";
49 This node represents a controller that uses two PHYs, one for usb2 and one for
53 usb2: usb_otg_ss@xxx {
64 This node represents a controller that uses one of the PHYs of the PHY provider
65 device defined previously. Note that the phy handle has an additional specifier
66 "1" to differentiate between the two PHYs.