From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] dts: move device tree sources to arch/$(ARCH)/dts/
Date: Thu, 06 Feb 2014 14:50:50 +0900 [thread overview]
Message-ID: <20140206145049.4323.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <CAPnjgZ3WAXresEJ_es=wMKsaiTWU4c3PFot8GzL1sKu182jT_Q@mail.gmail.com>
Hello Simon,
> Hi Masahiro,
>
> On 4 February 2014 02:38, Masahiro Yamada <yamada.m@jp.panasonic.com> wrote:
> > Unlike Linux Kernel, U-Boot historically had *.dts files under
> > board/$(VENDOR)/dts/ and *.dtsi files under arch/$(ARCH)/dts/.
> >
> > I think arch/$(ARCH)/dts dicretory is a better location
> > to store both *.dts and *.dtsi files.
> >
> > For example, before this commit, board/xilinx/dts directory
> > had both MicroBlaze dts (microblaze-generic.dts) and
> > ARM dts (zynq-*.dts), which are totally unrelated.
> >
> > This commit moves *.dts to arch/$(ARCH)/dts/ directories,
> > allowing us to describe nicely mutiple DTBs generation in the next commit.
>
> What is the motivation for this? I worry that we might end up with a
> lot of files in one directory.
We have only 35 .dtsi and .dts for ARM.
I think it will be OK at least until we have 500.
Linux v3.13 has 500 .dtsi and .dts files in arch/arm/boot/dts/
and they are still adding device trees to that directory.
I have no idea if they will keep going, or someone will scream and turn
around.
Anyway, when Linux guys someday invents a nice idea to work arond
increasing device trees, we can import it to U-Boot.
It should be easy for us because we already have a similar build system.
> One benefit of the current approach is
> that .dts files are split up by vendor. Even if we put the SoC .dtsi
> files in arch/arm, perhaps there is a benefit in leaving the board
> .dts files in board/<vendor>?
I don't like the idea to split up by vendor.
Now Xilinx has device trees both for ARM and Microblaze,
resulting in totally unrelated device trees in one directory.
What if Freescale decided to adopt device tree?
They support various boards on ARM, PowerPC, M68K.
Renesus is the same. They have ARM and SuperH boards.
On the other hand, different vendors can produce similar boards.
For example avionic design, which develops Tegra boards,
are using nVidia's sources.
When I saw board/nvidia/common/common.mk
and board/avionic-design/*/Makefile, etc., I think we're screwed up
with <vendor> directory.
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2014-02-06 5:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 9:38 [U-Boot] [PATCH v2 0/3] Simplify dts/Makefile and support multiple DTBs generation Masahiro Yamada
2014-02-04 9:38 ` [U-Boot] [PATCH v2 1/3] dts: re-write dts/Makefile more simply with Kbuild Masahiro Yamada
2014-02-15 23:38 ` Simon Glass
2014-02-18 9:27 ` Masahiro Yamada
2014-02-19 5:45 ` Simon Glass
2014-02-19 6:06 ` Masahiro Yamada
2014-02-19 6:12 ` Simon Glass
2014-02-04 9:38 ` [U-Boot] [PATCH v2 2/3] dts: move device tree sources to arch/$(ARCH)/dts/ Masahiro Yamada
2014-02-05 21:47 ` Simon Glass
2014-02-06 5:50 ` Masahiro Yamada [this message]
2014-02-15 23:46 ` Simon Glass
2014-02-18 9:43 ` Masahiro Yamada
2014-02-19 6:06 ` Simon Glass
2014-02-18 14:32 ` Tom Rini
2014-02-18 14:59 ` Michal Simek
2014-02-07 18:26 ` Scott Wood
2014-02-04 9:38 ` [U-Boot] [PATCH v2 3/3] dts: generate multiple device tree blobs Masahiro Yamada
2014-02-15 23:39 ` Simon Glass
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=20140206145049.4323.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.