Re: [PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

On Thu, 2019-08-08 at 21:32 +0200, Heiner Kallweit wrote: > [External] > > On 08.08.2019 17:24, Andrew Lunn wrote: > > On Thu, Aug 08, 2019 at 03:30:13PM +0300, Alexandru Ardelean wrote: > > > The ADIN PHYs can operate with Clause 45, however they are not typical for > > > how phylib considers

Re: [PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

On 08.08.2019 17:24, Andrew Lunn wrote: > On Thu, Aug 08, 2019 at 03:30:13PM +0300, Alexandru Ardelean wrote: >> The ADIN PHYs can operate with Clause 45, however they are not typical for >> how phylib considers Clause 45 PHYs. >> >> If the `features` field & the `get_features` hook are

Re: [PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

On Thu, Aug 08, 2019 at 03:30:13PM +0300, Alexandru Ardelean wrote: > The ADIN PHYs can operate with Clause 45, however they are not typical for > how phylib considers Clause 45 PHYs. > > If the `features` field & the `get_features` hook are unspecified, and the > device wants to operate via

[PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

The ADIN PHYs can operate with Clause 45, however they are not typical for how phylib considers Clause 45 PHYs. If the `features` field & the `get_features` hook are unspecified, and the device wants to operate via Clause 45, it would also try to read features via the