Re: [RFC] MIPS: BCM63XX: add simple Device Tree includes for allSoCs

[David Daney]

On 11/12/2012 08:54 PM, Stephen Warren wrote:
> On 11/11/2012 05:50 AM, Jonas Gorski wrote:
> > Add simple Device Tree include files for all currently supported SoCs.
> > These will be populated with device definitions as driver support
> > gets added.
>
> >   arch/mips/bcm63xx/dts/bcm6328.dtsi |   30 ++++++++++++++++++++++++++++++
> >   arch/mips/bcm63xx/dts/bcm6338.dtsi |   30 ++++++++++++++++++++++++++++++
> >   arch/mips/bcm63xx/dts/bcm6345.dtsi |   30 ++++++++++++++++++++++++++++++
> >   arch/mips/bcm63xx/dts/bcm6348.dtsi |   30 ++++++++++++++++++++++++++++++
> >   arch/mips/bcm63xx/dts/bcm6358.dtsi |   33 +++++++++++++++++++++++++++++++++
> >   arch/mips/bcm63xx/dts/bcm6368.dtsi |   33 +++++++++++++++++++++++++++++++++
>
> All of ARM, c6x, microblaze, openrisc, powerpc put device tree files
> into arch/${arch}/boot/dts/ - should MIPS follow the same layout?

At this point, I don't see what the benefit of centralizing all of these 
would be.  Currently there is no concept of a single kernel image that 
would work across multiple MIPS system implementations.  So keeping the 
DTS files with their users makes some organizational sense.

Similar arguments could be made for moving all the files in `find . 
-name \*.dts\*` to a top level dts/ directory.

David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/