From: Mark Rutland <mark.rutland@arm.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Jason Cooper <jason@lakedaemon.net>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org list"
<linux-kernel@vger.kernel.org>
Subject: Re: common location for devicetree files
Date: Mon, 11 Nov 2013 17:35:00 +0000 [thread overview]
Message-ID: <20131111173500.GM21201@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <528104AD.9030102@wwwdotorg.org>
On Mon, Nov 11, 2013 at 04:24:13PM +0000, Stephen Warren wrote:
> On 11/08/2013 11:32 AM, Jason Cooper wrote:
> > On Fri, Nov 08, 2013 at 12:17:30PM -0600, Kumar Gala wrote:
> > ...
> >> I get the point, just not sure how else to sort the 800+ .dts{i} files
> >> that we have in the kernel tree right now.
> >
> > Well, to start with, all #include'd files could go into a
> > arch/dts/include directory. That would clean things up a bit.
> >
> > We could also consider separating the dts files by ISA. All armv7 in
> > one directory, armv8, armv5te, powerpc, mips, etc.
>
> It's quite likely people will want to share some significant *.dtsi
> across multiple architectures.
At the moment we have some duplication of Versatile Express dtsi files
across the arm{,64}/boot/dts/ folders that could be shared. We already
share similar dtsi files between dts for ARMv7 and ARMv8 boards in
Pawel's external arm-dts repo [1].
Sharing across ISAs is important to me at least.
Mark.
[1] http://linux-arm.org/git?p=arm-dts.git;a=tree;f=versatile_express;h=7559c30fa94c471ff2a08c7936c5c01139d16f33;hb=18db2060268ae5b2b8616ba87376d73e338d4ca2
> --
> To unsubscribe from this list: send the line "unsubscribe devicetree" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-11-11 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 23:21 common location for devicetree files Kumar Gala
2013-11-08 16:52 ` Jason Cooper
[not found] ` <20131108165255.GA32668-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-11-08 17:59 ` Kumar Gala
2013-11-08 18:13 ` Jason Cooper
2013-11-08 18:17 ` Kumar Gala
2013-11-08 18:32 ` Jason Cooper
[not found] ` <20131108183240.GH10335-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-11-11 16:24 ` Stephen Warren
[not found] ` <528104AD.9030102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-11-11 16:34 ` Jason Cooper
2013-11-11 17:35 ` Mark Rutland [this message]
[not found] ` <1438803E-C904-428B-B042-891978BC15DF-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-11-08 19:33 ` Olof Johansson
2013-11-08 19:37 ` Jason Cooper
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=20131111173500.GM21201@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.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).