From: Rob Herring <robh@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Aymeric Aillet <aymeric.aillet@iot.bzh>,
Yusuke Goda <yusuke.goda.sx@renesas.com>
Subject: Re: [PATCH v2 2/4] of: add __of_get_next_status_child() and makes more generic of_get_next
Date: Tue, 28 Nov 2023 09:23:00 -0600 [thread overview]
Message-ID: <20231128152300.GA3275878-robh@kernel.org> (raw)
In-Reply-To: <87cyw3c13p.wl-kuninori.morimoto.gx@renesas.com>
On Tue, Nov 21, 2023 at 02:05:30AM +0000, Kuninori Morimoto wrote:
> Linux Kernel has of_get_next_available_child().
> Add more generic __of_get_next_status_child() to enable to use same
> logic for other status.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> Tested-by: Yusuke Goda <yusuke.goda.sx@renesas.com>
> ---
> drivers/of/base.c | 29 ++++++++++++++++++-----------
> 1 file changed, 18 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/of/base.c b/drivers/of/base.c
> index 3cb467a7e747..d0f7e7c890f1 100644
> --- a/drivers/of/base.c
> +++ b/drivers/of/base.c
> @@ -612,16 +612,9 @@ struct device_node *of_get_next_child(const struct device_node *node,
> }
> EXPORT_SYMBOL(of_get_next_child);
>
> -/**
> - * of_get_next_available_child - Find the next available child node
> - * @node: parent node
> - * @prev: previous child of the parent node, or NULL to get first
> - *
> - * This function is like of_get_next_child(), except that it
> - * automatically skips any disabled nodes (i.e. status = "disabled").
> - */
> -struct device_node *of_get_next_available_child(const struct device_node *node,
> - struct device_node *prev)
> +static struct device_node *__of_get_next_status_child(const struct device_node *node,
'__' means the lock should already be held, not that it is an internal
function.
With that dropped,
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-11-28 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 2:05 [PATCH v2 0/4] drivers: clk: renesas: ignore all clocks which is assinged to non Linux system Kuninori Morimoto
2023-11-21 2:05 ` [PATCH v2 1/4] of: add __of_device_is_status() and makes more generic status check Kuninori Morimoto
2023-11-28 15:23 ` Rob Herring
2023-11-21 2:05 ` [PATCH v2 2/4] of: add __of_get_next_status_child() and makes more generic of_get_next Kuninori Morimoto
2023-11-28 15:23 ` Rob Herring [this message]
2023-11-21 2:05 ` [PATCH v2 3/4] of: add for_each_reserved_child_of_node() Kuninori Morimoto
2023-11-21 2:05 ` [PATCH v2 4/4] drivers: clk: renesas: enable all clocks which is assinged to non Linux system Kuninori Morimoto
2023-11-28 15:34 ` Rob Herring
2023-11-28 23:13 ` Kuninori Morimoto
2023-11-30 16:07 ` Geert Uytterhoeven
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=20231128152300.GA3275878-robh@kernel.org \
--to=robh@kernel.org \
--cc=aymeric.aillet@iot.bzh \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=yusuke.goda.sx@renesas.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: 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).