From: Philipp Zabel <p.zabel@pengutronix.de> To: linux-kernel@vger.kernel.org, kernel@pengutronix.de Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>, Russell King - ARM Linux <linux@arm.linux.org.uk>, Greg KH <gregkh@linuxfoundation.org>, Mauro Carvalho Chehab <m.chehab@samsung.com>, Tomi Valkeinen <tomi.valkeinen@ti.com>, Guennadi Liakhovetski <g.liakhovetski@gmx.de>, Rob Herring <robh+dt@kernel.org>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Kyungmin Park <kyungmin.park@samsung.com>, devicetree@vger.kernel.org, Philipp Zabel <p.zabel@pengutronix.de> Subject: [RFC PATCH 0/3] Parse OF graph and create backlinks internally Date: Wed, 19 Mar 2014 16:12:01 +0100 [thread overview] Message-ID: <1395241924-9675-1-git-send-email-p.zabel@pengutronix.de> (raw) 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. 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
WARNING: multiple messages have this Message-ID (diff)
From: Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org Cc: Sylwester Nawrocki <s.nawrocki-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>, Russell King - ARM Linux <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>, Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>, Mauro Carvalho Chehab <m.chehab-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>, Tomi Valkeinen <tomi.valkeinen-l0cyMroinI0@public.gmane.org>, Guennadi Liakhovetski <g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>, Kyungmin Park <kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Philipp Zabel <p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Subject: [RFC PATCH 0/3] Parse OF graph and create backlinks internally Date: Wed, 19 Mar 2014 16:12:01 +0100 [thread overview] Message-ID: <1395241924-9675-1-git-send-email-p.zabel@pengutronix.de> (raw) 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. 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 devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-03-19 15:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-19 15:12 Philipp Zabel [this message] 2014-03-19 15:12 ` [RFC PATCH 0/3] Parse OF graph and create backlinks internally Philipp Zabel 2014-03-19 15:12 ` [RFC PATCH 1/3] of: Parse OF graph into graph structure Philipp Zabel 2014-03-20 13:22 ` Laurent Pinchart 2014-03-20 13:22 ` Laurent Pinchart 2014-03-19 15:12 ` [RFC PATCH 2/3] of: Add OF graph helper to get a specific port by id Philipp Zabel 2014-03-19 15:12 ` [RFC PATCH 3/3] of: Add OF graph helpers to iterate over ports Philipp Zabel 2014-03-20 22:09 ` [RFC PATCH 0/3] Parse OF graph and create backlinks internally Grant Likely 2014-03-20 22:09 ` Grant Likely
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1395241924-9675-1-git-send-email-p.zabel@pengutronix.de \ --to=p.zabel@pengutronix.de \ --cc=devicetree@vger.kernel.org \ --cc=g.liakhovetski@gmx.de \ --cc=gregkh@linuxfoundation.org \ --cc=kernel@pengutronix.de \ --cc=kyungmin.park@samsung.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=m.chehab@samsung.com \ --cc=robh+dt@kernel.org \ --cc=s.nawrocki@samsung.com \ --cc=tomi.valkeinen@ti.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.