[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F5A44E5.6090300@cavium.com>
Date: Fri, 09 Mar 2012 09:59:01 -0800
From: David Daney <david.daney@...ium.com>
To: Grant Likely <grant.likely@...retlab.ca>
CC: David Daney <ddaney.cavm@...il.com>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>,
"ralf@...ux-mips.org" <ralf@...ux-mips.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
Rob Herring <rob.herring@...xeda.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 2/2] of: Make of_find_node_by_path() traverse /aliases
for relative paths.
On 03/08/2012 05:33 PM, Grant Likely wrote:
> On Wed, 29 Feb 2012 11:21:04 -0800, David Daney<ddaney.cavm@...il.com> wrote:
>> From: David Daney<david.daney@...ium.com>
>>
>> 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<david.daney@...ium.com>
[...]
>
> All the aliases are already decoded at boot time now. See
> of_alias_scan(). Instead of open-coding this, you can add an
> of_alias_lookup() function something like this (untested):
>
After objections from davem, and a bit of thought, I already indicated
on a different branch of this thread that we should drop this patch.
I have improved my code so that it is no longer needed.
Thanks,
David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists