[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210615164905.62f7m4k5ezpm7vhm@skbuf>
Date: Tue, 15 Jun 2021 19:49:05 +0300
From: Ioana Ciornei <ciorneiioana@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Ioana Ciornei <ciorneiioana@...il.com>, davem@...emloft.net,
kuba@...nel.org, netdev@...r.kernel.org,
calvin.johnson@....nxp.com, hkallweit1@...il.com,
linux@...linux.org.uk, Ioana Ciornei <ioana.ciornei@....com>
Subject: Re: [PATCH net-next] mdio: mdiobus: setup of_node for the MDIO device
On Tue, Jun 15, 2021 at 06:19:26PM +0200, Andrew Lunn wrote:
> On Tue, Jun 15, 2021 at 06:44:01PM +0300, Ioana Ciornei wrote:
> > From: Ioana Ciornei <ioana.ciornei@....com>
> >
> > By mistake, the of_node of the MDIO device was not setup in the patch
> > linked below. As a consequence, any PHY driver that depends on the
> > of_node in its probe callback was not be able to successfully finish its
> > probe on a PHY
>
> Do you mean the PHY driver was looking for things like RGMII delays,
> skew values etc?
In my case, the VSC8514 PHY driver was looking for the led modes
(vsc8531,led-%d-mode").
>
> If the PHY driver fails to load because of missing OF properties, i
> guess this means the PHY driver will also fail in an ACPI system?
>
Yes, it will.
The PHY drivers were not changed to use the fwnode_* calls
instead of the of_* ones. Unfortunately, I cannot test this with ACPI
since the boards that have this PHY (that I have access to) do not
support ACPI yet.
Ioana
Powered by blists - more mailing lists