Re: [RFC] Device Tree Overlays Proposal (Was Re: capebus moving omap_devices to mach-omap2)

[Grant Likely <grant.likely@secretlab.ca>]

On Sat, 17 Nov 2012 23:27:18 +0100, Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
> On 16:23 Fri 09 Nov     , Stephen Warren wrote:
> > On 11/09/2012 09:28 AM, Grant Likely wrote:
> > However, I think the process for an end-user needs to be as simple as
> > "drop this .dts/.dtb file into some standard directory", and I imagine
> > it'll be much easier for distros/... to make that process work if
> > they're dealing with a .dtb that they can just blast into the kernel's
> > firmware loader interface, rather than having to also locate the
> > base-board .dts/.dtb file, and run dtc and/or other tools on both .dts
> > files together.
> I've exactly the same issue on Calao or the new atmel boards
> 
> We have lego boards
> 
> with different cpu-modues running on differetn mother boards with
> diferrentdaugther boards
> 
> on atmel we are lucky enough we can identity via 1-wire all of them but
> on Calao no
> 
> On Somfy platform we can detect hardware version and need different pinctrl
> 
> So personally I'll prefer to be able to request dtb from the kernel or push
> them from the userspace as it will depends where you will detect the hardware
> present
> 
> The main concern will which part of the kenel will now handle hw detection?

Along the lines of what you said above, it will depend on the board. If
the board /can/ be detected, then the kernel should do so and request
the appropriate configuration. If it cannot, then it simply must be left
up to either userspace or something explicit in the boot devicetree.

g.