From: Arnd Bergmann <arnd@arndb.de>
To: "Linas Vepstas (Code Aurora)" <linas@codeaurora.org>
Cc: linux-arch@vger.kernel.org, linux-hexagon@vger.kernel.org
Subject: Re: Device trees and systems-on-a-chip
Date: Fri, 23 Sep 2011 22:56:18 +0200 [thread overview]
Message-ID: <1420112.d5BXaqWxOG@wuerfel> (raw)
In-Reply-To: <20110923171300.GA15815@codeaurora.org>
On Friday 23 September 2011 12:13:00 Linas Vepstas wrote:
> Here: http://lwn.net/Articles/457635/ you say: "If the device tree
> vision comes true, a single board will actually be able to use the
> same device tree binary on either one, independent of which CPU
> actually runs the kernel."
>
> In my case, the hexagon and the arm cores will perceive the same
> devices at different addresses; there are also devices attached to one
> core that aren't attached to the other. So either we have two DT's,
> one for each core, or we have one DT with subsections for each core.
>
> I haven't yet looked to see how the DT's are being designed, but I have
> this sneaking suspicion that the second alternative is not being
> pursued ...
Hi Linas,
You can have .dtsi include files that describe the common parts and
just put the child buses at different addresses or leave them out
from a main .dts source file.
I think it should all work out. If not, there is still the option
of adding features to dtc to allow what you need.
Arnd
prev parent reply other threads:[~2011-09-23 20:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 17:13 Device trees and systems-on-a-chip Linas Vepstas (Code Aurora)
2011-09-23 20:56 ` Arnd Bergmann [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=1420112.d5BXaqWxOG@wuerfel \
--to=arnd@arndb.de \
--cc=linas@codeaurora.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hexagon@vger.kernel.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