From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, linux@armlinux.org.uk,
maxime.ripard@free-electrons.com, wens@csie.org,
peppe.cavallaro@st.com, alexandre.torgue@st.com, andrew@lunn.ch,
f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Corentin Labbe <clabbe.montjoie@gmail.com>
Subject: [PATCH 0/3] net: stmmac: Detect PHY location with phy-is-integrated
Date: Thu, 10 Aug 2017 10:51:26 +0200 [thread overview]
Message-ID: <20170810085129.20463-1-clabbe.montjoie@gmail.com> (raw)
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
the phy-is-integrated DT property.
The first and third patch should go via the net tree.
the second via the sunxi tree.
Thanks
Regards
Corentin Labbe (3):
Documentation: bindings: Add documentation for phy-is-integrated
ARM: sun8i: sunxi-h3-h5: add phy-is-integrated property to internal
PHY
net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated
Documentation/devicetree/bindings/net/phy.txt | 4 ++++
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 1 +
drivers/net/ethernet/stmicro/stmmac/dwmac-sun8i.c | 16 ++++++++--------
3 files changed, 13 insertions(+), 8 deletions(-)
--
2.13.0
next reply other threads:[~2017-08-10 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 8:51 Corentin Labbe [this message]
2017-08-10 8:51 ` [PATCH 1/3] Documentation: bindings: Add documentation for phy-is-integrated Corentin Labbe
2017-08-10 8:51 ` [PATCH 2/3] ARM: sun8i: sunxi-h3-h5: add phy-is-integrated property to internal PHY Corentin Labbe
[not found] ` <20170810085129.20463-3-clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-11 2:42 ` Chen-Yu Tsai
[not found] ` <CAGb2v64dBZgN6-8kHnnN1qiEXHnbXw_FM9WxGHPU0h-tZDbspA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 8:05 ` Corentin Labbe
2017-08-11 8:11 ` Chen-Yu Tsai
[not found] ` <CAGb2v66wCRe8nFucJa5nAT1GhO75LmCyfNWQQbwxzh085Zwk+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 8:19 ` Corentin Labbe
2017-08-11 8:22 ` Chen-Yu Tsai
[not found] ` <CAGb2v66SGAKnFoHNqWR+DqS-mY3KA853NmKpdHqf8huOkisLKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-11 8:39 ` Corentin Labbe
2017-08-11 13:25 ` Corentin Labbe
2017-08-11 15:03 ` Florian Fainelli
[not found] ` <302496B2-46F1-456D-A9A0-8257B5582695-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-16 9:12 ` Corentin Labbe
2017-08-17 15:10 ` Rob Herring
2017-08-10 8:51 ` [PATCH 3/3] net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated 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=20170810085129.20463-1-clabbe.montjoie@gmail.com \
--to=clabbe.montjoie@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).