From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] net: phy: micrel: Try default PHY ofnode first
Date: Wed, 27 Jan 2021 14:22:15 -0500 [thread overview]
Message-ID: <20210127192215.GK7530@bill-the-cat> (raw)
In-Reply-To: <20210116231616.302205-1-marex@denx.de>
On Sun, Jan 17, 2021 at 12:16:16AM +0100, Marek Vasut wrote:
> The phydev structure has a PHY OF node pointer in it, use that OF node
> first when looking up PHY OF node properties, since that is likely the
> correct PHY OF node pointer. If the pointer is not valid, which is the
> case e.g. on legacy DTs, fall back to parsing MAC ethernet-phy subnode.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Joe Hershberger <joe.hershberger@ni.com>
> Cc: Ramon Fried <rfried.dev@gmail.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210127/6315928e/attachment.sig>
prev parent reply other threads:[~2021-01-27 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 23:16 [PATCH] net: phy: micrel: Try default PHY ofnode first Marek Vasut
2021-01-27 19:22 ` Tom Rini [this message]
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=20210127192215.GK7530@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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