From: Jerome Brunet <jbrunet@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH 2/5] arm64: dts: meson: g12a: add ethernet pinctrl definitions
Date: Sat, 11 May 2019 19:27:49 +0200 [thread overview]
Message-ID: <7244c6d3e81e7bbb84ac508399ab64e236051673.camel@baylibre.com> (raw)
In-Reply-To: <CAFBinCAmGRHDU5QX2VEsV8vLBXD6fJtcRHbjdW8=p9Yti0V4qA@mail.gmail.com>
On Sat, 2019-05-11 at 19:06 +0200, Martin Blumenstingl wrote:
> Hi Jerome,
>
> On Fri, May 10, 2019 at 6:49 PM Jerome Brunet <jbrunet@baylibre.com> wrote:
> > Add the ethernet pinctrl settings for RMII, RGMII and internal phy leds
> >
> > Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> > ---
> > arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 37 +++++++++++++++++++++
> > 1 file changed, 37 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi b/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
> > index a32db09809f7..fe0f73730525 100644
> > --- a/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
> > +++ b/arch/arm64/boot/dts/amlogic/meson-g12a.dtsi
> > @@ -206,6 +206,43 @@
> > };
> > };
> >
> > + eth_leds_pins: eth-leds {
> > + mux {
> > + groups = "eth_link_led",
> > + "eth_act_led";
> > + function = "eth";
> > + bias-disable;
> > + };
> > + };
> > +
> > + eth_rmii_pins: eth-rmii {
> > + mux {
> > + groups = "eth_mdio",
> > + "eth_mdc",
> > + "eth_rgmii_rx_clk",
> > + "eth_rx_dv",
> > + "eth_rxd0",
> > + "eth_rxd1",
> > + "eth_txen",
> > + "eth_txd0",
> > + "eth_txd1";
> > + function = "eth";
> > + bias-disable;
> > + };
> > + };
> > +
> > + eth_rgmii_pins: eth-rgmii {
> > + mux {
> > + groups = "eth_rxd2_rgmii",
> > + "eth_rxd3_rgmii",
> > + "eth_rgmii_tx_clk",
> > + "eth_txd2_rgmii",
> > + "eth_txd3_rgmii";
> > + function = "eth";
> > + bias-disable;
> > + };
> > + };
> it seems that the group definition is incomplete (missing things like
> eth_mdc, eth_rx_dv, ...)
>
> we could also mix the eth_rmii_pins and eth_rgmii_pins in a board.dts
> (maybe that was your idea in the first place?):
yes that's the idea
> phy-mode = "rgmii";
> pinctrl-0 = <ð_rmii_pins>, <ð_rgmii_pins>;
> pinctrl-names = "default";
> however, in this case I would prefer if "eth_rmii_pins" was named only
> "eth_pins" (following mostly what Amlogic does with the pin group
> naming: eth_* for pins that are valid in both, rmii and rgmii mode and
> eth*rgmii* for pins that are only valid in rgmii mode)
I can't say I share your preference. I let Kevin decide what he wants.
>
>
> Regards
> Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-05-11 17:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:49 [PATCH 0/5] arm64: dts: meson: g12a: add network support Jerome Brunet
2019-05-10 16:49 ` [PATCH 1/5] arm64: dts: meson: g12a: add ethernet mac controller Jerome Brunet
2019-05-10 16:49 ` [PATCH 2/5] arm64: dts: meson: g12a: add ethernet pinctrl definitions Jerome Brunet
2019-05-11 17:06 ` Martin Blumenstingl
2019-05-11 17:27 ` Jerome Brunet [this message]
2019-05-15 0:10 ` Kevin Hilman
2019-05-10 16:49 ` [PATCH 3/5] arm64: dts: meson: g12a: add mdio multiplexer Jerome Brunet
2019-05-11 16:59 ` Martin Blumenstingl
2019-05-11 17:30 ` Jerome Brunet
2019-05-10 16:49 ` [PATCH 4/5] arm64: dts: meson: u200: add internal network Jerome Brunet
2019-05-10 16:49 ` [PATCH 5/5] arm64: dts: meson: sei510: add network support Jerome Brunet
2019-05-10 22:45 ` Kevin Hilman
2019-05-11 15:46 ` Jerome Brunet
2019-05-13 16:31 ` Kevin Hilman
2019-05-11 17:16 ` Martin Blumenstingl
2019-05-11 17:25 ` Jerome Brunet
2019-05-10 16:52 ` [PATCH 0/5] arm64: dts: meson: g12a: " Jerome Brunet
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=7244c6d3e81e7bbb84ac508399ab64e236051673.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
/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).