Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID

2017-01-24 Thread David Miller
From: Martin Blumenstingl Date: Sun, 22 Jan 2017 17:41:32 +0100 > The old description basically read like "ethernet-phy-id." can > be specified when you know the actual PHY ID. However, specifying this > has a side-effect: it forces Linux to bind to a certain PHY driver (the > one that ma

Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID

2017-01-23 Thread Florian Fainelli
On 01/22/2017 08:41 AM, Martin Blumenstingl wrote: > The old description basically read like "ethernet-phy-id." can > be specified when you know the actual PHY ID. However, specifying this > has a side-effect: it forces Linux to bind to a certain PHY driver (the > one that matches the ID gi

Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID

2017-01-23 Thread Rob Herring
On Sun, Jan 22, 2017 at 05:41:32PM +0100, Martin Blumenstingl wrote: > The old description basically read like "ethernet-phy-id." can > be specified when you know the actual PHY ID. However, specifying this > has a side-effect: it forces Linux to bind to a certain PHY driver (the > one that

Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID

2017-01-22 Thread Andrew Lunn
On Sun, Jan 22, 2017 at 05:41:32PM +0100, Martin Blumenstingl wrote: > The old description basically read like "ethernet-phy-id." can > be specified when you know the actual PHY ID. However, specifying this > has a side-effect: it forces Linux to bind to a certain PHY driver (the > one that

[PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID

2017-01-22 Thread Martin Blumenstingl
The old description basically read like "ethernet-phy-id." can be specified when you know the actual PHY ID. However, specifying this has a side-effect: it forces Linux to bind to a certain PHY driver (the one that matches the ID given in the compatible string), ignoring the ID which is rep