Hi Andrew,
Thank you for your advice.
On Fri, 9 Feb 2018 15:59:54 +0100 wrote:
> > 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
> 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 bet
Hi Andrew,
On Thu, 8 Feb 2018 13:51:44 +0100 wrote:
> On Thu, Feb 08, 2018 at 07:09:25PM +0900, Kunihiko Hayashi wrote:
> > Hello,
> >
> > Is there a way to specify "phy is internal" to generic phy driver,
> > that is, to make phy_is_internal() function available?
> >
> > I found "phy-is-integ
On Thu, Feb 08, 2018 at 07:09:25PM +0900, Kunihiko Hayashi wrote:
> Hello,
>
> Is there a way to specify "phy is internal" to generic phy driver,
> that is, to make phy_is_internal() function available?
>
> I found "phy-is-integrated" DT property in
> Documentation/devicetree/bindings/net/phy.txt
Hello,
Is there a way to specify "phy is internal" to generic phy driver,
that is, to make phy_is_internal() function available?
I found "phy-is-integrated" DT property in
Documentation/devicetree/bindings/net/phy.txt, however, it seems
that the property is no effect for generic phy. And I think
