On Wed, 19 Mar 2014 16:12:01 +0100, Philipp Zabel <p.zabel@xxxxxxxxxxxxxx> wrote: > Hi, > > while I'm eagerly awaiting the outcome of the current situation regarding the > "Move device tree graph parsing helpers to drivers/of" series, here is a draft > implementation that parses the whole device tree into a separate graph > structure, creating the backlinks internally. This way it doesn't matter to > the code in which direction the phandle links in the device tree are pointing. > The current code assumes a static device tree and doesn't handle runtime > changes at all. Hi Philipp, Nak on this approach. I still think each node has to be explicitly processed by a driver that understands its parents compatible property. Scanning the whole tree, hoping that it finds nodes that look like the graph binding makes too many assumptions about what it will find in the tree. I think your other patch that has each driver register its own endpoints is a better solution, and I think it is better suited for handling runtime changes. g. > > I've also added two helpers to iterate over all ports of a device, and to > obtain a specific port by its id (as contained in the 'reg' property). > > These patches are based directly on top of the previous series, which still > can be found at: > git://git.pengutronix.de/git/pza/linux.git topic/of-graph > > Philipp Zabel (3): > of: Parse OF graph into graph structure > of: Add OF graph helper to get a specific port by id > of: Add OF graph helpers to iterate over ports > > drivers/of/base.c | 476 +++++++++++++++++++++++++++++++++++++++-------- > include/linux/of_graph.h | 31 +++ > 2 files changed, 430 insertions(+), 77 deletions(-) > > -- > 1.9.0 > > -- > 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/ -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
