[U-Boot] [PATCH v2 2/3] dts: move device tree sources to arch/$(ARCH)/dts/

Scott Wood scottwood at freescale.com
Fri Feb 7 19:26:51 CET 2014


On Wed, 2014-02-05 at 14:47 -0700, Simon Glass wrote:
> Hi Masahiro,
> 
> On 4 February 2014 02:38, Masahiro Yamada <yamada.m at 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. 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 have strong feelings, just questing this...

Having all the device trees in one place (I don't even see why it should
be split by arch; some common dtsi files may be shared by multiple
arches) is nice for grepping and maintenance.  If it gets too large it
can grow an internal hierarchy.

Just like net drivers go under drivers/net regardless of arch, etc.

-Scott




More information about the U-Boot mailing list