Lines Matching refs:PHY

1 			    PHY SUBSYSTEM
4 This document explains the Generic PHY Framework along with the APIs provided,
9 *PHY* is the abbreviation for physical layer. It is used to connect a device
10 to the physical medium e.g., the USB controller has a PHY to provide functions
13 controllers have PHY functionality embedded into it and others use an external
14 PHY. Other peripherals that use PHY include Wireless LAN, Ethernet,
17 The intention of creating this framework is to bring the PHY drivers spread
21 This framework will be of use only to devices that use external PHY (PHY
24 2. Registering/Unregistering the PHY provider
26 PHY provider refers to an entity that implements one or more PHY instances.
27 For the simple case where the PHY provider implements only a single instance of
28 the PHY, the framework provides its own implementation of of_xlate in
29 of_phy_simple_xlate. If the PHY provider implements multiple instances, it
41 arguments. For the dt boot case, all PHY providers should use one of the above
42 2 macros to register the PHY provider.
49 unregister the PHY.
51 3. Creating the PHY
53 The PHY driver should create the PHY in order for other peripheral controllers
54 to make use of it. The PHY framework provides 2 APIs to create the PHY.
61 The PHY drivers can use one of the above 2 APIs to create the PHY by passing
63 phy_ops is a set of function pointers for performing PHY operations such as
67 can use phy_set_drvdata() after creating the PHY and use phy_get_drvdata() in
70 4. Getting a reference to the PHY
72 Before the controller can make use of the PHY, it has to get a reference to
73 it. This framework provides the following APIs to get a reference to the PHY.
83 be used to get the PHY. In the case of dt boot, the string arguments
85 non-dt boot, it should contain the label of the PHY.  The two
86 devm_phy_get associates the device with the PHY using devres on
87 successful PHY get. On driver detach, release function is invoked on
102 5. Releasing a reference to the PHY
104 When the controller no longer needs the PHY, it has to release the reference
105 to the PHY it has obtained using the APIs mentioned in the above section. The
106 PHY framework provides 2 APIs to release a reference to the PHY.
111 Both these APIs are used to release a reference to the PHY and devm_phy_put
112 destroys the devres associated with this PHY.
114 6. Destroying the PHY
116 When the driver that created the PHY is unloaded, it should destroy the PHY it
122 Both these APIs destroy the PHY and devm_phy_destroy destroys the devres
123 associated with this PHY.
127 This subsystem is pm runtime enabled. So while creating the PHY,
129 while destroying the PHY, pm_runtime_disable is called. Note that the phy
131 phy_create (PHY provider device).
134 pm_runtime_get_sync of PHY provider device because of parent-child relationship.
141 8. PHY Mappings
143 In order to get reference to a PHY without help from DeviceTree, the framework
156 The documentation for PHY dt binding can be found @