From: Ioana Ciornei <ciorneiioana@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Ioana Ciornei <ciorneiioana@gmail.com>,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
calvin.johnson@oss.nxp.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH net-next] mdio: mdiobus: setup of_node for the MDIO device
Date: Tue, 15 Jun 2021 19:49:05 +0300 [thread overview]
Message-ID: <20210615164905.62f7m4k5ezpm7vhm@skbuf> (raw)
In-Reply-To: <YMjTDkJU58E3ITCJ@lunn.ch>
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@nxp.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
next prev parent reply other threads:[~2021-06-15 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 15:44 [PATCH net-next] mdio: mdiobus: setup of_node for the MDIO device Ioana Ciornei
2021-06-15 16:19 ` Andrew Lunn
2021-06-15 16:49 ` Ioana Ciornei [this message]
2021-06-15 17:13 ` Russell King (Oracle)
2021-06-15 17:24 ` Ioana Ciornei
2021-06-15 18:25 ` Russell King (Oracle)
2021-06-15 18:31 ` Andrew Lunn
2021-06-15 21:09 ` Russell King (Oracle)
2021-06-15 21:21 ` Ioana Ciornei
2021-06-15 21:31 ` Andrew Lunn
2021-06-16 8:20 ` Ioana Ciornei
2021-06-16 9:40 ` Russell King (Oracle)
2021-06-16 11:01 ` Ioana Ciornei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210615164905.62f7m4k5ezpm7vhm@skbuf \
--to=ciorneiioana@gmail.com \
--cc=andrew@lunn.ch \
--cc=calvin.johnson@oss.nxp.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox