From: Sergei Shtylyov <sshtylyov@mvista.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 2/6] of: Make of_find_node_by_path() traverse /aliases for relative paths.
Date: Fri, 06 May 2011 14:17:13 +0400 [thread overview]
Message-ID: <4DC3CAA9.5040203@mvista.com> (raw)
In-Reply-To: <1304614949-30460-3-git-send-email-ddaney@caviumnetworks.com>
Hello.
On 05-05-2011 21:02, David Daney wrote:
> Currently all paths passed to of_find_node_by_path() must begin with a
> '/', indicating a full path to the desired node.
> Augment the look-up code so that if a path does *not* begin with '/',
> the path is used as the name of an /aliases property. The value of
> this alias is then used as the full node path to be found.
> Signed-off-by: David Daney<ddaney@caviumnetworks.com>
> ---
> drivers/of/base.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 40 insertions(+), 1 deletions(-)
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 632ebae..1a0a83e 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
[...]
> @@ -348,14 +351,50 @@ EXPORT_SYMBOL(of_get_next_child);
> struct device_node *of_find_node_by_path(const char *path)
> {
> struct device_node *np = allnodes;
> + struct device_node *aliases = NULL;
> + char *alias = NULL;
> + char *new_path = NULL;
>
> read_lock(&devtree_lock);
> +
> + if (path[0] != '/') {
> + const char *ps;
> + aliases = of_find_node_by_path("/aliases");
> + if (!aliases)
> + goto out;
> +
> + ps = strchr(path, '/');
> + if (ps) {
> + size_t len = ps - path;
> + alias = kmalloc(len + 1, GFP_KERNEL);
> + strncpy(alias, path, len);
> + alias[len] = 0;
BTW, you could use kstrndup() (from mm/util.c) instead of the above 3 lines.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov-Igf4POYTYCDQT0dZR+AlfA@public.gmane.org>
To: David Daney <ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
Cc: linux-mips-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ralf-6z/3iImG2C8G8FEW9MqTrA@public.gmane.org
Subject: Re: [RFC PATCH v3 2/6] of: Make of_find_node_by_path() traverse /aliases for relative paths.
Date: Fri, 06 May 2011 14:17:13 +0400 [thread overview]
Message-ID: <4DC3CAA9.5040203@mvista.com> (raw)
In-Reply-To: <1304614949-30460-3-git-send-email-ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
Hello.
On 05-05-2011 21:02, David Daney wrote:
> Currently all paths passed to of_find_node_by_path() must begin with a
> '/', indicating a full path to the desired node.
> Augment the look-up code so that if a path does *not* begin with '/',
> the path is used as the name of an /aliases property. The value of
> this alias is then used as the full node path to be found.
> Signed-off-by: David Daney<ddaney-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>
> ---
> drivers/of/base.c | 41 ++++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 40 insertions(+), 1 deletions(-)
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 632ebae..1a0a83e 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
[...]
> @@ -348,14 +351,50 @@ EXPORT_SYMBOL(of_get_next_child);
> struct device_node *of_find_node_by_path(const char *path)
> {
> struct device_node *np = allnodes;
> + struct device_node *aliases = NULL;
> + char *alias = NULL;
> + char *new_path = NULL;
>
> read_lock(&devtree_lock);
> +
> + if (path[0] != '/') {
> + const char *ps;
> + aliases = of_find_node_by_path("/aliases");
> + if (!aliases)
> + goto out;
> +
> + ps = strchr(path, '/');
> + if (ps) {
> + size_t len = ps - path;
> + alias = kmalloc(len + 1, GFP_KERNEL);
> + strncpy(alias, path, len);
> + alias[len] = 0;
BTW, you could use kstrndup() (from mm/util.c) instead of the above 3 lines.
WBR, Sergei
next prev parent reply other threads:[~2011-05-06 10:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 17:02 [RFC PATCH v3 0/6] MIPS: Octeon: Use Device Tree David Daney
2011-05-05 17:02 ` David Daney
2011-05-05 17:02 ` [RFC PATCH v3 1/6] of: Allow scripts/dtc/libfdt to be used from kernel code David Daney
2011-05-05 17:02 ` David Daney
2011-05-06 10:56 ` Michal Marek
2011-05-06 10:56 ` Michal Marek
2011-05-06 17:14 ` David Daney
2011-05-05 17:02 ` [RFC PATCH v3 2/6] of: Make of_find_node_by_path() traverse /aliases for relative paths David Daney
2011-05-06 10:05 ` Sergei Shtylyov
2011-05-19 18:54 ` Grant Likely
2011-05-06 10:17 ` Sergei Shtylyov [this message]
2011-05-06 10:17 ` Sergei Shtylyov
2011-05-05 17:02 ` [RFC PATCH v3 3/6] MIPS: Octeon: Add device tree source files David Daney
2011-05-05 17:02 ` David Daney
2011-05-05 17:02 ` [RFC PATCH v3 4/6] MIPS: Prune some target specific code out of prom.c David Daney
2011-05-05 17:02 ` David Daney
2011-05-05 17:02 ` [RFC PATCH v3 5/6] MIPS: Octeon: Add irq_create_of_mapping() and GPIO interrupts David Daney
2011-05-05 17:02 ` [RFC PATCH v3 6/6] MIPS: Octeon: Initialize and fixup device tree David Daney
2011-05-05 17:02 ` David Daney
2011-05-05 17:40 ` [RFC PATCH v3 0/6] MIPS: Octeon: Use Device Tree Grant Likely
2011-05-05 17:48 ` David Daney
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=4DC3CAA9.5040203@mvista.com \
--to=sshtylyov@mvista.com \
--cc=ddaney@caviumnetworks.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 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.