From: Andrew Lunn <andrew@lunn.ch>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: netdev@vger.kernel.org
Subject: Re: net: phy: question about phy_is_internal for generic-phy
Date: Fri, 9 Feb 2018 15:59:54 +0100 [thread overview]
Message-ID: <20180209145954.GA29333@lunn.ch> (raw)
In-Reply-To: <20180209143157.11B8.4A936039@socionext.com>
> There are some SoCs that have a built-in phy, and sometimes
> these SoCs can choose to use built-in phy or external phy.
O.K. This is the same use case we had at the end of last year.
How are the MDIO busses arranged? Is there an internal MDIO bus and an
external MDIO bus? How do you change between the internal and the
external? Or is it one bus, with the two PHYs having different
addresses?
For the hardware in question last year, an MDIO MUX was implemented.
The MAC has a phy-handle pointing to either the internal PHY on the
internal MDIO bus, or the external PHY on the external MDIO bus. The
MDIO MUX layer would then set the register to select between the two.
https://patchwork.kernel.org/patch/10025279/
Andrew
next prev parent reply other threads:[~2018-02-09 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:09 net: phy: question about phy_is_internal for generic-phy Kunihiko Hayashi
2018-02-08 12:51 ` Andrew Lunn
2018-02-09 5:31 ` Kunihiko Hayashi
2018-02-09 14:59 ` Andrew Lunn [this message]
2018-02-13 5:15 ` Kunihiko Hayashi
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=20180209145954.GA29333@lunn.ch \
--to=andrew@lunn.ch \
--cc=hayashi.kunihiko@socionext.com \
--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;
as well as URLs for NNTP newsgroup(s).