From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>,
Jason Cooper <jason@lakedaemon.net>,
Marcin Wojtas <mw@semihalf.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Lior Amsalem <alior@marvell.com>
Subject: Re: [PATCH 2/3] ARM: mvebu: Add support for the network controller in Armada 375 SoC
Date: Fri, 04 Jul 2014 22:51:02 +0400 [thread overview]
Message-ID: <53B6F796.3090004@cogentembedded.com> (raw)
In-Reply-To: <1404498697-21978-3-git-send-email-ezequiel.garcia@free-electrons.com>
Hello.
On 07/04/2014 10:31 PM, Ezequiel Garcia wrote:
> This commit adds the support for the network controller in Marvell
> Armada 375 SoC devicetree.
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---
> arch/arm/boot/dts/armada-375.dtsi | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> diff --git a/arch/arm/boot/dts/armada-375.dtsi b/arch/arm/boot/dts/armada-375.dtsi
> index fb92551..5e897d2 100644
> --- a/arch/arm/boot/dts/armada-375.dtsi
> +++ b/arch/arm/boot/dts/armada-375.dtsi
> @@ -151,6 +151,37 @@
> <0xc100 0x100>;
> };
>
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "marvell,orion-mdio";
> + reg = <0xc0054 0x4>;
> + };
> +
> + /* Network controller */
> + pp2@f0000 {
> + compatible = "marvell,armada-375-pp2";
> + reg = <0xf0000 0xa000>, /* Packet Processor regs */
> + <0xc0000 0x3060>, /* LMS regs */
> + <0xc4000 0x100>, /* eth0 regs */
> + <0xc5000 0x100>; /* eth1 regs */
Hm, why are the above two ranges not listed under the "ethernet" subnodes?
> + clocks = <&gateclk 3>, <&gateclk 19>;
> + clock-names = "pp_clk", "gop_clk";
> + status = "disabled";
> +
> + eth0: ethernet@c4000 {
> + interrupts = <GIC_SPI 37 IRQ_TYPE_LEVEL_HIGH>;
> + port-id = <0>;
> + status = "disabled";
> + };
> +
> + eth1: ethernet@c5000 {
> + interrupts = <GIC_SPI 41 IRQ_TYPE_LEVEL_HIGH>;
> + port-id = <1>;
> + status = "disabled";
> + };
> + };
> +
WBR, Sergei
next prev parent reply other threads:[~2014-07-04 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 18:31 [PATCH net-next 0/3] Network driver for Armada 375 SoC Ezequiel Garcia
2014-07-04 18:31 ` [PATCH 1/3] ethernet: Add new driver for Marvell Armada 375 network unit Ezequiel Garcia
2014-07-05 21:03 ` Francois Romieu
2014-07-05 21:14 ` Joe Perches
2014-07-07 14:26 ` Ezequiel Garcia
2014-07-07 21:22 ` Francois Romieu
2014-07-04 18:31 ` [PATCH 2/3] ARM: mvebu: Add support for the network controller in Armada 375 SoC Ezequiel Garcia
2014-07-04 18:51 ` Sergei Shtylyov [this message]
2014-07-04 19:06 ` Ezequiel Garcia
2014-07-04 18:31 ` [PATCH 3/3] ARM: mvebu: Enable the network controller in Armada 375 DB 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=53B6F796.3090004@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=alior@marvell.com \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.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).