From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v3 2/2] ARC: DTS: Add device-tree for Anarion-based development board
Date: Thu, 17 Aug 2017 13:17:43 +0000 [thread overview]
Message-ID: <1502975863.3268.25.camel@synopsys.com> (raw)
In-Reply-To: <20170816221516.13609-3-alex.g@adaptrum.com>
Hi Alexandru,
On Wed, 2017-08-16@15:15 -0700, Alexandru Gagniuc wrote:
> +#include "skeleton.dtsi"
Eugeniy already commented on that - most probably you'll end up
overriding most if not all entries from "skeleton.dtsi" so why
bother with it at all?
And I don't see any mention of your own memory node so I assume you rely on
the one from our skeleton.dtsi? The first question is if it really matches your setup?
I.e. 256 Mb mapped to 0x8000_0000. And even if that's the case what if we change
this to something else later?
IMHO having your own "memory" node makes some sens :)
> +
> + gmac0: ethernet at f2010000 {
> + compatible = "adaptrum,anarion-gmac", "snps,dwmac";
> + reg = <0xf2010000 0x4000>;
> +
> + interrupt-parent = <&core_intc>;
You already specified default INTC above, so you may just drop "interrupt-parent"
property from this node.
> +
> + gmac1: ethernet at f2014000 {
> + compatible = "adaptrum,anarion-gmac", "snps,dwmac";
> + reg = <0xf2014000 0x4000>, <0xf2018100 8>;
> +
> + interrupt-parent = <&core_intc>;
Ditto.
-Alexey
next prev parent reply other threads:[~2017-08-17 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 22:15 [PATCH v3 0/2] Add platform support for Adaptrum Anarion SOC Alexandru Gagniuc
2017-08-16 22:15 ` [PATCH v3 1/2] ARC: [plat-sim] Add .compatible property " Alexandru Gagniuc
2017-08-16 22:15 ` [PATCH v3 2/2] ARC: DTS: Add device-tree for Anarion-based development board Alexandru Gagniuc
2017-08-17 11:11 ` Eugeniy Paltsev
2017-08-17 11:35 ` Eugeniy Paltsev
2017-08-17 13:17 ` Alexey Brodkin [this message]
2017-08-25 21:18 ` [PATCH v3 0/2] Add platform support for Adaptrum Anarion SOC Vineet Gupta
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=1502975863.3268.25.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@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