linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: mvebu: Add required ethernet muxing for the Armada 370 SoC
Date: Sun, 10 Aug 2014 14:21:49 +0200	[thread overview]
Message-ID: <53E763DD.4000305@gmail.com> (raw)
In-Reply-To: <1407511136-26477-2-git-send-email-ezequiel.garcia@free-electrons.com>

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 {
> +					marvell,pins = "mpp17", "mpp18";
> +					marvell,function = "ge";
> +				};
> +
> +				ge0_pins: ge0_pins {

More nitpicking,

as stated by others it should be "ge{0,1]_rgmii_pins" not only because
it is rgmii, but because a370 also supports gmii for ge0.

Sebastian

> +					marvell,pins = "mpp5", "mpp6", "mpp7", "mpp8",
> +						       "mpp9", "mpp10", "mpp11", "mpp12",
> +						       "mpp13", "mpp14", "mpp15", "mpp16";
> +					marvell,function = "ge0";
> +				};
> +
> +				ge1_pins: ge1_pins {
> +					marvell,pins = "mpp19", "mpp20", "mpp21", "mpp22",
> +						       "mpp23", "mpp24", "mpp25", "mpp26",
> +						       "mpp27", "mpp28", "mpp29", "mpp30";
> +					marvell,function = "ge1";
> +				};
>  			};
>  
>  			gpio0: gpio at 18100 {
> 

  parent reply	other threads:[~2014-08-10 12:21 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
2014-08-10 12:21   ` Sebastian Hesselbarth [this message]
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=53E763DD.4000305@gmail.com \
    --to=sebastian.hesselbarth@gmail.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;
as well as URLs for NNTP newsgroup(s).