From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: Sharing *.dtsi between Linux architectures?
Date: Fri, 12 Jul 2013 13:58:35 -0600 [thread overview]
Message-ID: <51E05FEB.1090308@wwwdotorg.org> (raw)
Is there a (possibly just proposed) mechanism in place to allow *.dts
from multiple Linux architectures to share common *.dtsi files?
As an example, consider two SoCs that are identical except for the CPU
complex. One uses an ARMv7 CPU (DTs in arch/arm/boot/dts/) and the other
uses some ARMv8 CPU (DTs in arch/am64/boot/dts/). It'd be useful to
define all the SoC components in some common .dtsi file to avoid
duplication, and have both arch/arm/boot/dts/tegraXXX.dtsi and
arch/arm64/boot/dts/tegraYYY.dtsi include that and add the relevant
CPU-related nodes.
I could imagine creating one of the following paths for this purpose:
arch/common/dts/
include/dt-common/
include/dtsi/
... or perhaps re-using the existing:
include/dt-bindings/
... although my original intent for that last location was just to house
header files that define constants that are part of binding definitions,
rather than actual structural content.
next reply other threads:[~2013-07-12 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 19:58 Stephen Warren [this message]
2013-07-12 20:17 ` Sharing *.dtsi between Linux architectures? Rob Herring
2013-07-12 20:23 ` Jean-Christophe PLAGNIOL-VILLARD
2013-07-12 22:26 ` Russell King - ARM Linux
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=51E05FEB.1090308@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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