public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: mvebu: Add required ethernet muxing for the Armada 370 SoC
Date: Mon, 11 Aug 2014 08:38:56 -0300	[thread overview]
Message-ID: <20140811113856.GA1665@arch.cereza> (raw)
In-Reply-To: <53E762A0.5070900@gmail.com>

On 10 Aug 02:16 PM, Sebastian Hesselbarth wrote:
> On 08/08/2014 05:18 PM, Ezequiel Garcia wrote:
> > This commit adds the required pin muxing for the two network interfaces
> > and the MDIO interface, to the Armada 370 SoC.
> > 
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > ---
> >  arch/arm/boot/dts/armada-370.dtsi | 19 +++++++++++++++++++
> >  1 file changed, 19 insertions(+)
> > 
> > diff --git a/arch/arm/boot/dts/armada-370.dtsi b/arch/arm/boot/dts/armada-370.dtsi
> > index 21b588b..b0700bf6 100644
> > --- a/arch/arm/boot/dts/armada-370.dtsi
> > +++ b/arch/arm/boot/dts/armada-370.dtsi
> > @@ -151,6 +151,25 @@
> >  						       "mpp62", "mpp60", "mpp58";
> >  					marvell,function = "audio";
> >  				};
> > +
> > +				mdio_pins: mdio_pins {
> 
> Ezequiel,
> 
> please keep me posted next time ;)
> 

Ouch...

> Above should be: mdio_pins: mdio-pins {
> same for the ones below.
> 

OK.

> > +					marvell,pins = "mpp17", "mpp18";
> > +					marvell,function = "ge";
> 
> As we haven't used it before, we could still rename "ge" function to
> more approprate "mdio"... but it is ok.
>

FWIW, I'd rather leave it as it is. If we change the function name, we would
make backporting a PITA, just because of a nitpick.
 
> Besides the comments,
> 
> Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
>

Thanks,
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-08-11 11:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 15:18 [PATCH 0/6] mvebu: Network devicetree pin muxing Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 1/6] ARM: mvebu: Add required ethernet muxing for the Armada 370 SoC Ezequiel Garcia
2014-08-09 15:19   ` Thomas Petazzoni
2014-08-09 16:31     ` Ezequiel Garcia
2014-08-10 12:16   ` Sebastian Hesselbarth
2014-08-11 11:38     ` Ezequiel Garcia [this message]
2014-08-10 12:21   ` Sebastian Hesselbarth
2014-08-08 15:18 ` [PATCH 2/6] ARM: mvebu: Add proper pin muxing on Globalscale Mirabox board Ezequiel Garcia
2014-08-08 17:12   ` Andrew Lunn
2014-08-08 18:21     ` Ezequiel Garcia
2014-08-08 19:21       ` Andrew Lunn
2014-08-08 19:47         ` Ezequiel Garcia
2014-08-09 15:21         ` Thomas Petazzoni
2014-08-09 15:52           ` Ezequiel Garcia
2014-08-09 15:57           ` Jason Cooper
2014-08-10 17:38             ` Thomas Petazzoni
2014-08-10 21:23               ` Andrew Lunn
2014-08-08 15:18 ` [PATCH 3/6] ARM: mvebu: Add proper pin muxing on the Armada 370 DB board Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 4/6] ARM: mvebu: Add proper pin muxing on Netgear ReadyNAS 102 Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 5/6] ARM: mvebu: Add proper pin muxing on Netgear ReadyNAS 104 Ezequiel Garcia
2014-08-08 15:18 ` [PATCH 6/6] ARM: mvebu: Add proper pin muxing on Armada 370 RD board Ezequiel Garcia

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=20140811113856.GA1665@arch.cereza \
    --to=ezequiel.garcia@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox