From: Rob Herring <robherring2@gmail.com> To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "David S. Miller" <davem@davemloft.net>, Lennert Buytenhek <kernel@wantstofly.org>, Lior Amsalem <alior@marvell.com>, Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>, Rami Rosen <rosenr@marvell.com>, netdev@vger.kernel.org, Maen Suleiman <maen@marvell.com>, Gregory Clement <gregory.clement@free-electrons.com>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Date: Thu, 11 Oct 2012 10:46:57 -0500 [thread overview] Message-ID: <5076E9F1.60200@gmail.com> (raw) In-Reply-To: <1349969282-12676-2-git-send-email-thomas.petazzoni@free-electrons.com> On 10/11/2012 10:27 AM, Thomas Petazzoni wrote: > This patch contains a new network driver for the network unit of the > ARM Marvell Armada 370 and the Armada XP. Both SoCs use the PJ4B > processor, a Marvell-developed ARM core that implements the ARMv7 > instruction set. > diff --git a/Documentation/devicetree/bindings/net/marvell-neta.txt b/Documentation/devicetree/bindings/net/marvell-neta.txt > new file mode 100644 > index 0000000..a031978 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/marvell-neta.txt > @@ -0,0 +1,24 @@ > +* Marvell Armada 370 / Armada XP Ethernet Controller (NETA) > + > +Required properties: > +- compatible: should be "marvell,neta". This should be more specific such as "marvell,armada-xp-neta". Or use 370 instead of xp. It should be which ever chip came first. > +- reg: address and length of the register set for the device. > +- interrupts: interrupt for the device > +- phy-mode: String, operation mode of the PHY interface. Supported > + values are "sgmii" and "rmii". > +- phy-addr: Integer, address of the PHY. > +- device_type: should be "network". Drop this. device_type is not used for FDT. > +- clock-frequency: frequency of the peripheral clock of the SoC. > + > +Example: > + > +eth@d0070000 { Should be ethernet@... Rob
WARNING: multiple messages have this Message-ID (diff)
From: robherring2@gmail.com (Rob Herring) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Date: Thu, 11 Oct 2012 10:46:57 -0500 [thread overview] Message-ID: <5076E9F1.60200@gmail.com> (raw) In-Reply-To: <1349969282-12676-2-git-send-email-thomas.petazzoni@free-electrons.com> On 10/11/2012 10:27 AM, Thomas Petazzoni wrote: > This patch contains a new network driver for the network unit of the > ARM Marvell Armada 370 and the Armada XP. Both SoCs use the PJ4B > processor, a Marvell-developed ARM core that implements the ARMv7 > instruction set. > diff --git a/Documentation/devicetree/bindings/net/marvell-neta.txt b/Documentation/devicetree/bindings/net/marvell-neta.txt > new file mode 100644 > index 0000000..a031978 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/marvell-neta.txt > @@ -0,0 +1,24 @@ > +* Marvell Armada 370 / Armada XP Ethernet Controller (NETA) > + > +Required properties: > +- compatible: should be "marvell,neta". This should be more specific such as "marvell,armada-xp-neta". Or use 370 instead of xp. It should be which ever chip came first. > +- reg: address and length of the register set for the device. > +- interrupts: interrupt for the device > +- phy-mode: String, operation mode of the PHY interface. Supported > + values are "sgmii" and "rmii". > +- phy-addr: Integer, address of the PHY. > +- device_type: should be "network". Drop this. device_type is not used for FDT. > +- clock-frequency: frequency of the peripheral clock of the SoC. > + > +Example: > + > +eth at d0070000 { Should be ethernet at ... Rob
next prev parent reply other threads:[~2012-10-11 15:47 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-11 15:27 [PATCH v2] Network driver for the Armada 370 and Armada XP ARM Marvell SoCs Thomas Petazzoni 2012-10-11 15:27 ` Thomas Petazzoni 2012-10-11 15:27 ` [PATCH v2 1/4] net: mvneta: driver for Marvell Armada 370/XP network unit Thomas Petazzoni 2012-10-11 15:27 ` Thomas Petazzoni 2012-10-11 15:46 ` Rob Herring [this message] 2012-10-11 15:46 ` Rob Herring 2012-10-11 16:38 ` Thomas Petazzoni 2012-10-11 16:38 ` Thomas Petazzoni 2012-10-12 14:16 ` Thomas Petazzoni 2012-10-12 14:16 ` Thomas Petazzoni 2012-10-11 18:13 ` Baruch Siach 2012-10-11 18:13 ` Baruch Siach 2012-10-11 21:26 ` Francois Romieu 2012-10-11 21:26 ` Francois Romieu 2012-10-12 14:31 ` Jason Cooper 2012-10-12 14:31 ` Jason Cooper 2012-10-12 14:59 ` Thomas Petazzoni 2012-10-12 14:59 ` Thomas Petazzoni 2012-10-12 16:03 ` Jason Cooper 2012-10-12 16:03 ` Jason Cooper 2012-10-11 15:28 ` [PATCH v2 2/4] net: mvneta: update MAINTAINERS file for the mvneta maintainers Thomas Petazzoni 2012-10-11 15:28 ` Thomas Petazzoni 2012-10-11 15:28 ` [PATCH v2 3/4] arm: mvebu: add Ethernet controllers using mvneta driver for Armada 370/XP Thomas Petazzoni 2012-10-11 15:28 ` Thomas Petazzoni 2012-10-11 15:28 ` [PATCH v2 4/4] arm: mvebu: enable Ethernet controllers on Armada 370/XP eval boards Thomas Petazzoni 2012-10-11 15:28 ` Thomas Petazzoni
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=5076E9F1.60200@gmail.com \ --to=robherring2@gmail.com \ --cc=alior@marvell.com \ --cc=andrew@lunn.ch \ --cc=davem@davemloft.net \ --cc=gregory.clement@free-electrons.com \ --cc=jason@lakedaemon.net \ --cc=kernel@wantstofly.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=maen@marvell.com \ --cc=netdev@vger.kernel.org \ --cc=rosenr@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.