Sometimes the specific interaction between the platform and the PHY requires special handling.
For instance, to change where the PHY's clock input is, or to add a delay to account for latency issues in the data path.
In order to support such contingencies, the PHY Layer allows platform code to register fixups to be run when the PHY is brought up (or subsequently reset).
When the PHY Layer brings up a PHY it checks to see if there are any fixups registered for it,
matching based on UID (contained in the PHY device's phy_id field) and the bus identifier (contained in phydev->dev.bus_id).
Both must match, however two constants, PHY_ANY_ID and PHY_ANY_UID, are provided as wildcards for the bus ID and UID, respectively.
When a match is found, the PHY layer will invoke the run function associated with the fixup.
This function is passed a pointer to the phy_device of interest.
It should therefore only operate on that PHY.
Have a great day,
Victor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
