From: Scott Branden <scott.branden@broadcom.com>
To: Jon Mason <jon.mason@broadcom.com>,
davem@davemloft.net, f.fainelli@gmail.com
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Scott Branden <sbranden@broadcom.com>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
hauke@hauke-m.de, zajec5@gmail.com, linux-kernel@vger.kernel.org,
Ray Jui <rjui@broadcom.com>, Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Kumar Gala <galak@codeaurora.org>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/7] ARM: dts: NSP: Add bgmac entries
Date: Fri, 8 Jul 2016 09:14:17 -0700 [thread overview]
Message-ID: <577FD159.7000905@broadcom.com> (raw)
In-Reply-To: <1467993362-13229-1-git-send-email-jon.mason@broadcom.com>
Hi Jon,
In Subject line, you mean add amac entries.
On 16-07-08 08:56 AM, Jon Mason wrote:
> Add device tree entries for the ethernet devices present on the
> Broadcom Northstar Plus SoCs
>
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
> ---
> arch/arm/boot/dts/bcm-nsp.dtsi | 18 ++++++++++++++++++
> arch/arm/boot/dts/bcm958625k.dts | 8 ++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/arch/arm/boot/dts/bcm-nsp.dtsi b/arch/arm/boot/dts/bcm-nsp.dtsi
> index def9e78..f6d5abe 100644
> --- a/arch/arm/boot/dts/bcm-nsp.dtsi
> +++ b/arch/arm/boot/dts/bcm-nsp.dtsi
> @@ -192,6 +192,24 @@
> status = "disabled";
> };
>
> + amac0: ethernet@22000 {
> + compatible = "brcm,nsp-amac";
> + reg = <0x022000 0x1000>,
> + <0x110000 0x1000>;
> + reg-names = "amac_base", "idm_base";
> + interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
> + status = "disabled";
> + };
> +
> + amac1: ethernet@23000 {
> + compatible = "brcm,nsp-amac";
> + reg = <0x023000 0x1000>,
> + <0x111000 0x1000>;
> + reg-names = "amac_base", "idm_base";
> + interrupts = <GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>;
> + status = "disabled";
> + };
> +
> nand: nand@26000 {
> compatible = "brcm,nand-iproc", "brcm,brcmnand-v6.1";
> reg = <0x026000 0x600>,
> diff --git a/arch/arm/boot/dts/bcm958625k.dts b/arch/arm/boot/dts/bcm958625k.dts
> index e298450..f41a13b 100644
> --- a/arch/arm/boot/dts/bcm958625k.dts
> +++ b/arch/arm/boot/dts/bcm958625k.dts
> @@ -56,6 +56,14 @@
> status = "okay";
> };
>
> +&amac0 {
> + status = "okay";
> +};
> +
> +&amac1 {
> + status = "okay";
> +};
> +
> &pcie0 {
> status = "okay";
> };
>
Regards,
Scott
next prev parent reply other threads:[~2016-07-08 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 15:56 [PATCH 7/7] ARM: dts: NSP: Add bgmac entries Jon Mason
2016-07-08 16:14 ` Scott Branden [this message]
2016-07-11 16:50 ` Florian Fainelli
-- strict thread matches above, loose matches on Subject: below --
2016-06-30 22:59 [PATCH 0/7] net: ethernet: bgmac: Add platform device support Jon Mason
2016-06-30 22:59 ` [PATCH 7/7] ARM: dts: NSP: Add bgmac entries Jon Mason
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=577FD159.7000905@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=galak@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jon.mason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=zajec5@gmail.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).