> With net drivers having PHY managed by the firmware or DSA, there is no linux > description of their PHYs. DSA should not be special, Linux is driving the PHY so it has to exist as a linux device. Firmware is a different case. If the firmware has decided to hide the PHY, the MAC driver is using a higher level API, generally just ksetting_set etc. It would be up to the MAC driver to export its PHY topology and provide whatever other firmware calls are needed. We should keep this in mind when designing the kAPI, but don't need to actually implement it. The kAPI should not directly reference a phydev/phylink instance, but an abstract object which represents a PHY. Andrew
