The Design and Implementation of the FreeBSD Operating System, Second Edition
Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition)


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]

FreeBSD/Linux Kernel Cross Reference
sys/contrib/device-tree/Bindings/phy/phy-bindings.txt

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

    1 This document explains only the device tree data binding. For general
    2 information about PHY subsystem refer to Documentation/driver-api/phy/phy.rst
    3 
    4 PHY device node
    5 ===============
    6 
    7 Required Properties:
    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
   11                 PHY.
   12 
   13 Optional Properties:
   14 phy-supply:     Phandle to a regulator that provides power to the PHY. This
   15                 regulator will be managed during the PHY power on/off sequence.
   16 
   17 For example:
   18 
   19 phys: phy {
   20     compatible = "xxx";
   21     reg = <...>;
   22     .
   23     .
   24     #phy-cells = <1>;
   25     .
   26     .
   27 };
   28 
   29 That node describes an IP block (PHY provider) that implements 2 different 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.
   32 
   33 PHY user node
   34 =============
   35 
   36 Required Properties:
   37 phys : the phandle for the PHY device (used by the PHY subsystem; not to be
   38        confused with the Ethernet specific 'phy' and 'phy-handle' properties,
   39        see Documentation/devicetree/bindings/net/ethernet.txt for these)
   40 phy-names : the names of the PHY corresponding to the PHYs present in the
   41             *phys* phandle
   42 
   43 Example 1:
   44 usb1: usb_otg_ss@xxx {
   45     compatible = "xxx";
   46     reg = <xxx>;
   47     .
   48     .
   49     phys = <&usb2_phy>, <&usb3_phy>;
   50     phy-names = "usb2phy", "usb3phy";
   51     .
   52     .
   53 };
   54 
   55 This node represents a controller that uses two PHYs, one for usb2 and one for
   56 usb3.
   57 
   58 Example 2:
   59 usb2: usb_otg_ss@xxx {
   60     compatible = "xxx";
   61     reg = <xxx>;
   62     .
   63     .
   64     phys = <&phys 1>;
   65     phy-names = "usbphy";
   66     .
   67     .
   68 };
   69 
   70 This node represents a controller that uses one of the PHYs of the PHY provider
   71 device defined previously. Note that the phy handle has an additional specifier
   72 "1" to differentiate between the two PHYs.

Cache object: b5886cb9f1fad1a92c0ae07c48069bbe


[ source navigation ] [ diff markup ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]


This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.