On 10/18/2013 08:57 AM, Rob Herring wrote:
[...]
Unflattening is definitely the right
direction to go here.
I wonder if that is really true.
The device tree in question is very short lived, and used to control the
configuration of some hardware device when loading the driver.
The use of it is completely contained within a single driver (at least
that is my understanding), it is not information that needs to be shared
system wide.
Given that it is a driver implementation issue, rather than making
things work nicely system wide, I don't think it really matters what is
done.
It may be that the overhead of unflattening the tree and then freeing
it, is much greater than just extracting a few things from the FDT.
That said, I don't really have a preference for what is done. My
original questions were targeted at understanding this particular use case.
David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
