From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 3/5] ARM: BCM63XX: add BCM63138 minimal Device Tree
Date: Tue, 22 Apr 2014 12:52:16 +0200 [thread overview]
Message-ID: <4701106.5EnjdVQgVO@wuerfel> (raw)
In-Reply-To: <1398130758-19456-4-git-send-email-f.fainelli@gmail.com>
On Monday 21 April 2014 18:39:16 Florian Fainelli wrote:
>
> +#include "skeleton.dtsi"
> +
> +/ {
> + compatible = "brcm,bcm63138";
> + model = "Broadcom BCM63138 DSL SoC";
> + interrupt-parent = <&gic>;
> +
> + cpus {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu at 0 {
> + device_type = "cpu";
> + compatible = "arm,cortex-a9";
> + next-level-cache = <&L2>;
> + reg = <0>;
> + };
> + };
Even if you don't support SMP yet, I can see no reason not
to list both CPUs here. The binding is known and the code
should ignore the extra cores if it doesn't know how to
turn them on.
> +
> + /* ARM bus */
> + axi at 80000000 {
> + compatible = "simple-bus";
> + ranges = <0 0x80000000 0x783003>;
> + reg = <0x80000000 0x783003>;
The length seems odd, I would expect that the bus actually
translates all addresses in the 0x80000000 range to downstream
devices even if there is nothing connected. Just round it up
to your best knowledge.
I would also drop the 'reg' property. Since you don't have a
specific "compatible" value, there is no way to use the registers
in this node.
> + #address-cells = <1>;
> + #size-cells = <1>;
> +
> + L2: cache-controller at 1d000 {
> + compatible = "arm,pl310-cache";
> + reg = <0x1d000 0x1000>;
> + cache-unified;
> + cache-level = <2>;
> + interrupts = <GIC_PPI 0 IRQ_TYPE_LEVEL_HIGH>;
> + };
> +
> + mpcore at 1e000 {
> + compatible = "simple-bus";
> + reg = <0x1e000 0x20000>;
> + ranges = <0 0x1e000 0x20000>;
> + #address-cells = <1>;
> + #size-cells = <1>;
Same thing here.
Also, can you explain why there is a separate 'mpcore' bus, and why the
cache controller is not part of that?
Do you have reason to believe that this is how the hardware actually
looks?
> +
> + /* Legacy UBUS base */
> + ubus at fffe8000 {
> + compatible = "simple-bus";
> + reg = <0xfffe8000 0x8053>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0 0xfffe8000 0x8053>;
> + };
> +};
Again, use a proper 'length' here and remove the 'reg' property.
Arnd
next prev parent reply other threads:[~2014-04-22 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 1:39 [PATCH RESEND 0/5] ARM: BCM63XX: add support for BCM63138 SoC Florian Fainelli
2014-04-22 1:39 ` [PATCH RESEND 1/5] ARM: BCM63XX: add basic support for the Broadcom BCM63138 DSL SoC Florian Fainelli
2014-04-22 10:45 ` Arnd Bergmann
2014-05-02 5:32 ` Florian Fainelli
2014-05-02 7:55 ` Arnd Bergmann
2014-05-05 22:41 ` Florian Fainelli
2014-05-06 9:32 ` Arnd Bergmann
2014-04-22 1:39 ` [PATCH RESEND 2/5] ARM: BCM63XX: add low-level UART debug support Florian Fainelli
2014-04-22 1:39 ` [PATCH RESEND 3/5] ARM: BCM63XX: add BCM63138 minimal Device Tree Florian Fainelli
2014-04-22 10:52 ` Arnd Bergmann [this message]
2014-05-02 5:37 ` Florian Fainelli
2014-04-22 1:39 ` [PATCH RESEND 4/5] ARM: BCM63XX: add BCM963138DVT Reference platform DTS Florian Fainelli
2014-04-22 13:49 ` Jonas Gorski
2014-04-22 15:41 ` Matt Porter
2014-04-22 1:39 ` [PATCH RESEND 5/5] MAINTAINERS: add entry for the Broadcom BCM63xx ARM SoCs Florian Fainelli
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=4701106.5EnjdVQgVO@wuerfel \
--to=arnd@arndb.de \
--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