From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Fainelli Subject: Re: [PATCH] Documentation: net: phy: improve explanation when to specify the PHY ID Date: Mon, 23 Jan 2017 12:33:14 -0800 Message-ID: <58e8429a-7159-471c-7507-3fde566939a8@gmail.com> References: <20170122164132.13967-1-martin.blumenstingl@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org To: Martin Blumenstingl , andrew-g2DYL2Zd6BY@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org Return-path: In-Reply-To: <20170122164132.13967-1-martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On 01/22/2017 08:41 AM, Martin Blumenstingl wrote: > The old description basically read like "ethernet-phy-idAAAA.BBBB" 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 reported by the actual PHY. > Whenever a device is shipped with (multiple) different PHYs during it's > production lifetime then explicitly specifying > "ethernet-phy-idAAAA.BBBB" could break certain revisions of that device. > > Signed-off-by: Martin Blumenstingl Reviewed-by: Florian Fainelli -- Florian -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html