[PATCH v4 19/21] drivers/of: Support adding sub-tree
panto at antoniou-consulting.com
Tue May 5 02:41:59 AEST 2015
> On May 2, 2015, at 01:57 , Benjamin Herrenschmidt <benh at kernel.crashing.org> wrote:
> On Fri, 2015-05-01 at 13:46 -0500, Rob Herring wrote:
>> On Fri, May 1, 2015 at 10:22 AM, Benjamin Herrenschmidt
>> <benh at kernel.crashing.org> wrote:
>>> On Fri, 2015-05-01 at 07:54 -0500, Rob Herring wrote:
>>>> The difference seems to be whether you allocate space or just point to
>>>> the FDT for various strings/data. Is that right?
>>>>> * of_fdt_add_subtree() is the introduced API to do the work.
>>>> Have you looked at overlays and if so why do they not work for your purposes?
>>>> Why do you need to do this with the flattened tree?
>>> The basic idea I asked Gavin to implement is that since the FW needs to
>>> provide a bunch of DT updates to Linux at runtime in the form of new
>>> nodes below an existing one, rather than doing it via some new/custom
>>> format, instead, have it send a bit of FDT blob to expand under an
>>> existing node.
>> Overlay = an FDT blob to graft into a live running system. Sounds like
>> the same thing.
>>> As for the details of Gavin implementation, I haven't looked at it in
>>> details yet so there might be issues there, however I don't know what
>>> you mean by "overlays", any pointer ?
> Well, that looks horrendously complicated, poorly documented and totally
> unused in-tree outside of the unittest stuff, yay ! It has all sort of
> "features" that I don't really care about.
If it was easy to get stuff in, it would get more of the real-use drivers
> I still don't see what it buys me other than making my FW a lot more
> complex having to generate all that additional fixup etc... crap that I
> don't totally get yet.
You don’t generate any additional fixups. You just compile with the option
that generates all the fixups for you.
> What's wrong with just unflattening the nodes in place ? The DT comes
> from the FW in the first place so all the phandles are already good in
> the new added blob. Internally, the FW created new nodes in its internal
> representation and flattened the subtree and sends that subtree to
> I don't plan to play "revert" either, if you unplug, I do need to remove
> what's under the slot but that's true of boot time devices, not just
> "new" ones, so the overlay stuff won't do the trick and I certainly
> don't want to keep track…
You get all of the corner cases handled for free. Perhaps it works for your
Perhaps you can educate me on what you need supported and we can make sure
More information about the Linuxppc-dev