From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 7/7] ARM: BCM5301X: register bcma bus
Date: Wed, 27 Aug 2014 11:22:01 -0700 [thread overview]
Message-ID: <53FE21C9.7060909@gmail.com> (raw)
In-Reply-To: <1408915485-8078-9-git-send-email-hauke@hauke-m.de>
On 08/24/2014 02:24 PM, Hauke Mehrtens wrote:
> ---
> arch/arm/boot/dts/bcm4708.dtsi | 58 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 58 insertions(+)
We probably want a compatible string for each of these aix subnodes you
are adding, so we can match them.
>
> diff --git a/arch/arm/boot/dts/bcm4708.dtsi b/arch/arm/boot/dts/bcm4708.dtsi
> index 31141e8..7c240ab 100644
> --- a/arch/arm/boot/dts/bcm4708.dtsi
> +++ b/arch/arm/boot/dts/bcm4708.dtsi
> @@ -31,4 +31,62 @@
> };
> };
>
> + nvram0: nvram at 0 {
> + compatible = "brcm,bcm47xx-nvram";
> + reg = <0x1c000000 0x01000000>;
> + };
> +
> + sprom0: sprom at 0 {
> + compatible = "brcm,bcm47xx-sprom";
> + nvram = <&nvram0>;
> + };
> +
> + aix at 18000000 {
> + compatible = "brcm,bus-aix";
> + reg = <0x18000000 0x1000>;
> + ranges = <0x00000000 0x18000000 0x00100000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + sprom = <&sprom0>;
> +
> + usb2 at 0 {
> + reg = <0x18021000 0x1000>;
> + interrupts = <GIC_SPI 79 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + usb3 at 0 {
> + reg = <0x18023000 0x1000>;
> + interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + gmac at 0 {
> + reg = <0x18024000 0x1000>;
> + interrupts = <GIC_SPI 147 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + gmac at 1 {
> + reg = <0x18025000 0x1000>;
> + interrupts = <GIC_SPI 148 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + gmac at 2 {
> + reg = <0x18026000 0x1000>;
> + interrupts = <GIC_SPI 149 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + gmac at 3 {
> + reg = <0x18027000 0x1000>;
> + interrupts = <GIC_SPI 150 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + pcie at 0 {
> + reg = <0x18012000 0x1000>;
> + interrupts = <GIC_SPI 131 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + pcie at 1 {
> + reg = <0x18013000 0x1000>;
> + interrupts = <GIC_SPI 137 IRQ_TYPE_LEVEL_HIGH>;
> + };
> + };
> };
>
prev parent reply other threads:[~2014-08-27 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 21:24 [RFC 0/7] bcma: add device tree support Hauke Mehrtens
2014-08-24 21:24 ` Hauke Mehrtens
2014-08-24 21:24 ` [RFC 1/7] MIPS: BCM47XX: move the nvram header file into common space Hauke Mehrtens
2014-08-24 21:24 ` [RFC 2/7] bcm47xx-nvram: add new broadcom nvram driver with dt support Hauke Mehrtens
2014-08-24 21:45 ` Rafał Miłecki
2014-08-27 5:54 ` Rafał Miłecki
2014-08-27 18:20 ` Florian Fainelli
2014-08-27 18:43 ` Rafał Miłecki
2014-08-24 21:24 ` [RFC 3/7] bcm47xx-sprom: add Broadcom sprom parser driver Hauke Mehrtens
2014-08-25 7:52 ` Arnd Bergmann
2014-08-25 15:01 ` Jonas Gorski
2014-08-26 21:32 ` Hauke Mehrtens
2014-09-01 9:24 ` Rafał Miłecki
2014-08-24 21:24 ` [RFC 4/7] bcma: register bcma as device tree driver Hauke Mehrtens
2014-08-25 7:57 ` Arnd Bergmann
2014-08-26 21:25 ` Hauke Mehrtens
2014-08-24 21:24 ` [RFC 5/7] bcma: get IRQ numbers from dt Hauke Mehrtens
2014-08-25 8:00 ` Arnd Bergmann
2014-08-24 21:24 ` [RFC 6/7] bcma: get sprom from devicetree Hauke Mehrtens
2014-08-25 8:04 ` Arnd Bergmann
2014-08-24 21:24 ` [RFC 7/7] ARM: BCM5301X: register bcma bus Hauke Mehrtens
2014-08-27 18:22 ` Florian Fainelli [this message]
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=53FE21C9.7060909@gmail.com \
--to=f.fainelli@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).