Lines Matching refs:PHY
3 PHY Abstraction Layer
10 PHY. The PHY concerns itself with negotiating link parameters with the link
17 the PHY management code with the network driver. This has resulted in large
23 accessed are, in fact, busses, the PHY Abstraction Layer treats them as such.
30 Basically, this layer is meant to provide an interface to PHY devices which
36 Most network devices are connected to a PHY by means of a management bus.
46 mii_id is the address on the bus for the PHY, and regnum is the register
68 Connecting to a PHY
71 between the PHY device, and the network device. At this time, the PHY's bus
73 At this point, there are several ways to connect to the PHY:
86 manually calling functions to update status, and configure the PHY
89 Letting the PHY Abstraction Layer do Everything
92 useful to drivers that can't), connecting to the PHY is simple:
99 Next, you need to know the device name of the PHY connected to this device.
101 bus id, and the second is the PHY's address on that bus. Typically,
108 phydev is a pointer to the phy_device structure which represents the PHY. If
111 PHY's software state machine, and registered for the PHY's interrupt, if it
113 current state, though the PHY will not yet be truly operational at this
116 PHY-specific flags should be set in phydev->dev_flags prior to the call
117 to phy_connect() such that the underlying PHY driver can check for flags
120 the PHY/controller, of which the PHY needs to be aware.
123 between the controller and the PHY. Examples are GMII, MII,
128 controller may be connected to a gigabit capable PHY, so you would need to
130 for these bitfields. Note that you should not SET any bits, or the PHY may
135 PHY to connect to the network. If you want to handle your own interrupts,
145 keep your network device and the PHY properly in sync. If so, you can
146 register a helper function when connecting to the PHY, which will be called
159 the complex interactions between the PHY and your network device. If this is
181 A convenience function to print out the PHY status neatly.
186 Requests the IRQ for the PHY interrupts, then enables them for
192 Attaches a network device to a particular PHY, binding the PHY to a generic
204 settings in the PHY.
220 PHY Device Drivers
222 With the PHY Abstraction Layer, adding support for new PHYs is
226 Generic PHY driver
228 If the desired PHY doesn't have any errata, quirks, or special
230 support, and let the PHY Abstraction Layer's Generic PHY Driver
233 Writing a PHY driver
235 If you do need to write a PHY driver, the first thing to do is
236 make sure it can be matched with an appropriate PHY device.
250 etc) your PHY device and driver support. Most PHYs support
256 soft_reset: perform a PHY software reset
257 config_init: configures PHY into a sane state after a reset.
258 For instance, a Davicom PHY requires descrambling disabled.
260 PHY may not have been reset or had fixups run yet.
266 did_interrupt: Checks if the PHY generated an interrupt
270 hwtstamp: Set the PHY HW timestamping configuration
271 rxtstamp: Requests a receive timestamp at the PHY level for a 'skb'
272 txtsamp: Requests a transmit timestamp at the PHY level for a 'skb'
273 set_wol: Enable Wake-on-LAN at the PHY level
274 get_wol: Get the Wake-on-LAN status at the PHY level
275 read_mmd_indirect: Read PHY MMD indirect register
276 write_mmd_indirect: Write PHY MMD indirect register
291 The PHY's MMD register accesses are handled by the PAL framework
292 by default, but can be overridden by a specific PHY driver if
293 required. This could be the case if a PHY was released for
294 manufacturing before the MMD PHY register definitions were
296 the generic PAL framework for accessing the PHY's MMD registers.
299 registers for EEE query and configuration if the PHY supports
300 the IEEE standard access mechanisms, or can use the PHY's specific
301 access interfaces if overridden by the specific PHY driver. See
307 Sometimes the specific interaction between the platform and the PHY requires
308 special handling. For instance, to change where the PHY's clock input is,
310 to support such contingencies, the PHY Layer allows platform code to register
311 fixups to be run when the PHY is brought up (or subsequently reset).
313 When the PHY Layer brings up a PHY it checks to see if there are any fixups
314 registered for it, matching based on UID (contained in the PHY device's phy_id
319 When a match is found, the PHY layer will invoke the run function associated
321 interest. It should therefore only operate on that PHY.