From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode
Date: Fri, 28 Jul 2017 15:47:36 +0200 [thread overview]
Message-ID: <20170728134736.GC32230@lunn.ch> (raw)
In-Reply-To: <CAGb2v66=h_5df=B0Us-kvvFg9r_qSUroDzn-xvQLSpD1d8DhBQ@mail.gmail.com>
On Fri, Jul 28, 2017 at 05:53:40PM +0800, Chen-Yu Tsai wrote:
> On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe
> <clabbe.montjoie@gmail.com> wrote:
> > Hello
> >
> > The current way to find if the phy is internal is to compare DT phy-mode
> > and emac_variant/internal_phy.
> > But it will negate a possible future SoC where an external PHY use the
> > same phy mode than the internal one.
> >
> > This patchs series adds a new way to find if the PHY is internal, via its
> > compatible.
>
> You've already joined in on the discussion for the patch "net: stmmac:
> dwmac-rk: Add internal phy support". It is pretty much the same issue.
> Please wait for it to come to a proper conclusion. At least then we can
> agree on something so different platforms with the same problem don't
> have diverging solutions.
Yes, this is important.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
To: Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org>
Cc: Corentin Labbe
<clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
alexandre.torgue-qxv4g6HH51o@public.gmane.org,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sunxi <linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
Russell King <linux-I+IVW8TIWO2tmTQ+vhA3Yw@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Giuseppe Cavallaro <peppe.cavallaro-qxv4g6HH51o@public.gmane.org>,
Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org>
Subject: Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode
Date: Fri, 28 Jul 2017 15:47:36 +0200 [thread overview]
Message-ID: <20170728134736.GC32230@lunn.ch> (raw)
In-Reply-To: <CAGb2v66=h_5df=B0Us-kvvFg9r_qSUroDzn-xvQLSpD1d8DhBQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Jul 28, 2017 at 05:53:40PM +0800, Chen-Yu Tsai wrote:
> On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe
> <clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > Hello
> >
> > The current way to find if the phy is internal is to compare DT phy-mode
> > and emac_variant/internal_phy.
> > But it will negate a possible future SoC where an external PHY use the
> > same phy mode than the internal one.
> >
> > This patchs series adds a new way to find if the PHY is internal, via its
> > compatible.
>
> You've already joined in on the discussion for the patch "net: stmmac:
> dwmac-rk: Add internal phy support". It is pretty much the same issue.
> Please wait for it to come to a proper conclusion. At least then we can
> agree on something so different platforms with the same problem don't
> have diverging solutions.
Yes, this is important.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree <devicetree@vger.kernel.org>,
alexandre.torgue@st.com, netdev <netdev@vger.kernel.org>,
linux-sunxi <linux-sunxi@googlegroups.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Icenowy Zheng <icenowy@aosc.io>
Subject: Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode
Date: Fri, 28 Jul 2017 15:47:36 +0200 [thread overview]
Message-ID: <20170728134736.GC32230@lunn.ch> (raw)
In-Reply-To: <CAGb2v66=h_5df=B0Us-kvvFg9r_qSUroDzn-xvQLSpD1d8DhBQ@mail.gmail.com>
On Fri, Jul 28, 2017 at 05:53:40PM +0800, Chen-Yu Tsai wrote:
> On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe
> <clabbe.montjoie@gmail.com> wrote:
> > Hello
> >
> > The current way to find if the phy is internal is to compare DT phy-mode
> > and emac_variant/internal_phy.
> > But it will negate a possible future SoC where an external PHY use the
> > same phy mode than the internal one.
> >
> > This patchs series adds a new way to find if the PHY is internal, via its
> > compatible.
>
> You've already joined in on the discussion for the patch "net: stmmac:
> dwmac-rk: Add internal phy support". It is pretty much the same issue.
> Please wait for it to come to a proper conclusion. At least then we can
> agree on something so different platforms with the same problem don't
> have diverging solutions.
Yes, this is important.
Andrew
next prev parent reply other threads:[~2017-07-28 13:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 9:28 [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` [PATCH 1/3] dt-bindings: net: add compatible for internal sun8i-h3/sun8i-v3s PHYs Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` [PATCH 2/3] ARM: sunxi: h3/h5: Add sun8i-h3-ephy compatible Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:44 ` Chen-Yu Tsai
2017-07-28 9:44 ` Chen-Yu Tsai
2017-07-28 9:46 ` Icenowy Zheng
2017-07-28 9:46 ` Icenowy Zheng
2017-07-28 9:46 ` Icenowy Zheng
2017-07-28 9:28 ` [PATCH 3/3] net-next: stmmac: dwmac-sun8i: choose internal PHY via compatible Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:28 ` Corentin Labbe
2017-07-28 9:49 ` Chen-Yu Tsai
2017-07-28 9:49 ` Chen-Yu Tsai
2017-07-28 9:49 ` Chen-Yu Tsai
2017-07-28 9:54 ` Corentin Labbe
2017-07-28 9:54 ` Corentin Labbe
2017-07-28 9:54 ` Corentin Labbe
2017-07-28 9:53 ` [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode Chen-Yu Tsai
2017-07-28 9:53 ` Chen-Yu Tsai
2017-07-28 9:53 ` Chen-Yu Tsai
2017-07-28 13:47 ` Andrew Lunn [this message]
2017-07-28 13:47 ` Andrew Lunn
2017-07-28 13:47 ` Andrew Lunn
2017-07-28 13:55 ` Andrew Lunn
2017-07-28 13:55 ` Andrew Lunn
2017-07-28 13:55 ` Andrew Lunn
2017-07-28 14:25 ` Corentin Labbe
2017-07-28 14:25 ` Corentin Labbe
2017-07-28 14:25 ` Corentin Labbe
2017-07-28 14:36 ` Andrew Lunn
2017-07-28 14:36 ` Andrew Lunn
2017-07-28 14:36 ` Andrew Lunn
2017-07-28 14:44 ` Corentin Labbe
2017-07-28 14:44 ` Corentin Labbe
2017-07-28 14:44 ` Corentin Labbe
2017-07-28 14:51 ` Andrew Lunn
2017-07-28 14:51 ` Andrew Lunn
2017-07-28 14:51 ` Andrew Lunn
2017-07-28 17:54 ` Florian Fainelli
2017-07-28 17:54 ` Florian Fainelli
2017-07-28 17:54 ` Florian Fainelli
2017-07-29 6:48 ` Corentin Labbe
2017-07-29 6:48 ` Corentin Labbe
2017-07-29 6:48 ` Corentin Labbe
2017-07-31 12:19 ` Chen-Yu Tsai
2017-07-31 12:19 ` Chen-Yu Tsai
2017-07-31 12:19 ` Chen-Yu Tsai
2017-07-31 12:26 ` Corentin Labbe
2017-07-31 12:26 ` Corentin Labbe
2017-07-31 12:26 ` Corentin Labbe
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=20170728134736.GC32230@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.