From: Srinivas KANDAGATLA <srinivas.kandagatla-qxv4g6HH51o@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@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 16:51:08 +0100 [thread overview]
Message-ID: <505200EC.2090707@st.com> (raw)
In-Reply-To: <5051FF1A.7060507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 13/09/12 16:43, Rob Herring wrote:
> On 09/13/2012 10:25 AM, Srinivas KANDAGATLA wrote:
>> On 13/09/12 16:14, Stephen Warren wrote:
>>> On 09/13/2012 05: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>
>>> You forgot to Cc the drivers/of maintainers, Grant and Rob. I have here.
>> Oops...
>>
>>> I can certainly see a use for this in many places; the "runtime
>>> interpreted power sequences" patch, and the regulator DT parsing code at
>>> least both could benefit from this.
> I would think the power sequences code would always iterate over the nodes.
>
>> There are at-least 7-8 places in the current kernel which could use this
>> function directly.
> Care to point them out and preferably fix them then. That would be more
> convincing that this is needed.
I did plan on sending all the 7 patches with this one, But I wanted to
know overall opinion on introduction of this new function.
Here are the instances of the drivers... which can benefit from this
function..
drivers/tty/hvc/hvc_opal.c
drivers/spi/spi-s3c64xx.c
drivers/net/ethernet/freescale/fsl_pq_mdio.c
arch/powerpc/sysdev/qe_lib/qe.c
arch/powerpc/platforms/powernv/opal.c
arch/powerpc/kernel/prom.c
>
> Rob
>
>
>
next prev parent reply other threads:[~2012-09-13 15:51 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 [this message]
2012-09-13 20:32 ` Rob Herring
[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=505200EC.2090707@st.com \
--to=srinivas.kandagatla-qxv4g6hh51o@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=robherring2-Re5JQEeQqe8AvxtiuMwx3w@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).