From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Srinivas KANDAGATLA <srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
Cc: bergner-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Subject: Re: [PATCH 3.6.0-rc5] dt: introduce of_get_child to get child node by name.
Date: Thu, 13 Sep 2012 15:32:03 -0500 [thread overview]
Message-ID: <505242C3.7090006@gmail.com> (raw)
In-Reply-To: <1347534640-787-1-git-send-email-srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
On 09/13/2012 06:10 AM, Srinivas KANDAGATLA wrote:
> From: Srinivas Kandagatla <srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
>
> This patch introduces of_get_child function to get a child node by its
> name in a given parent node.
>
> Without this patch each driver code has to iterate the parent and do
> a string compare, However having of_get_child libary function would
> avoid code duplication, errors and is more convenient.
>
> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
> ---
> drivers/of/base.c | 27 +++++++++++++++++++++++++++
> include/linux/of.h | 2 ++
> 2 files changed, 29 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index d4a1c9a..d4b6840 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -391,6 +391,33 @@ struct device_node *of_get_next_available_child(const struct device_node *node,
> EXPORT_SYMBOL(of_get_next_available_child);
>
> /**
> + * of_get_child - Find the child node by name for given parent
> + * @node: parent node
> + * @name: child name to look for.
> + *
> + * This function looks for child node for given matching name
> + *
> + * Returns a node pointer if found, with refcount incremented, use
> + * of_node_put() on it when done.
> + * else returns NULL.
> + */
> +
> +struct device_node *of_get_child(const struct device_node *node,
of_get_child_by_name would be more consistent naming with other apis.
> + const char *name)
> +{
> + struct device_node *child;
> +
> + read_lock(&devtree_lock);
I don't think you need the lock here. The for_each takes the lock while
finding the node.
> + for_each_child_of_node(node, child)
> + if (child->name && (of_node_cmp(child->name, name) == 0)
> + && of_node_get(child))
> + break;
> + read_unlock(&devtree_lock);
> + return child;
> +}
> +EXPORT_SYMBOL(of_get_child);
> +
> +/**
> * of_find_node_by_path - Find a node matching a full OF path
> * @path: The full path to match
> *
> diff --git a/include/linux/of.h b/include/linux/of.h
> index 1b11632..510e1fe 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -192,6 +192,8 @@ extern struct device_node *of_get_next_child(const struct device_node *node,
> struct device_node *prev);
> extern struct device_node *of_get_next_available_child(
> const struct device_node *node, struct device_node *prev);
> +extern struct device_node *of_get_child(const struct device_node *node,
> + const char *name);
>
> #define for_each_child_of_node(parent, child) \
> for (child = of_get_next_child(parent, NULL); child != NULL; \
>
next prev parent reply other threads:[~2012-09-13 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 11:10 [PATCH 3.6.0-rc5] dt: introduce of_get_child to get child node by name Srinivas KANDAGATLA
[not found] ` <1347534640-787-1-git-send-email-srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
2012-09-13 15:14 ` Stephen Warren
[not found] ` <5051F838.5080002-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-09-13 15:25 ` Srinivas KANDAGATLA
[not found] ` <5051FAFA.4040507-qxv4g6HH51o@public.gmane.org>
2012-09-13 15:43 ` Rob Herring
[not found] ` <5051FF1A.7060507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-13 15:48 ` Stephen Warren
2012-09-13 15:51 ` Srinivas KANDAGATLA
2012-09-13 20:32 ` Rob Herring [this message]
[not found] ` <505242C3.7090006-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-09-14 6:55 ` Srinivas KANDAGATLA
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=505242C3.7090006@gmail.com \
--to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bergner-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=srinivas.kandagatla-qxv4g6HH51o@public.gmane.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).