On Sat, Mar 24, 2018 at 07:48:58PM +0100, Andrew Lunn wrote: > As far as i can see, you have three basic problems: > > 1) How do you associate the PTP device to the netdev? > 2) How do you get the information you need to configure the PTP device Yes, yes. > 3) How do you limit the MAC/PHY to what the PTP device can do. Hm, I don't think this is important. > phylib does have all this information. It is phylib that calls the MAC > with link speed information. When the MAC connects to the PHY, it > passes the MII mode, and when the PHY requests the MII mode changes, > phylib knows. The MAC has to call phy_init_eee() to see if the PHY is > EEE capable. phylib also tells the MAC what speeds the PHY is capable > off, so it is in the position to mask out speeds the PTP device does > not support, etc. Right, so phylib can operate on phydev->attached_dev->mdiots; > So i really think you need to cleanly integrate into phylib and > phylink. So I think I've done that, more or less, but I'd like to hear your ideas on how to make it cleaner... Thanks, Richard -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
