From: Stephen Boyd <sboyd@codeaurora.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: Re: [PATCH 2/3] clk: let of_clk_get_parent_name() fail for invalid clock-indices
Date: Fri, 20 Nov 2015 09:45:09 -0800 [thread overview]
Message-ID: <20151120174509.GQ32672@codeaurora.org> (raw)
In-Reply-To: <1448004981-11133-2-git-send-email-yamada.masahiro@socionext.com>
On 11/20, Masahiro Yamada wrote:
> Currently, of_clk_get_parent_name() returns a wrong parent clock name
> when "clock-indices" property exists and the given index is not found
> in the property. In this case, NULL should be returned.
>
> For example,
>
> oscillator {
> compatible = "myclocktype";
> #clock-cells = <1>;
> clock-indices = <1>, <3>;
> clock-output-names = "clka", "clkb";
> };
>
> Currently, of_clk_get_parent_name(np, 0) returns "clka", but should
> return NULL because "clock-indices" does not contain <0>.
What is np pointing at? Something like:
consumer {
clocks = <&oscillator 0>;
};
Which would be invalid DT because oscillator doesn't have an
output for index 0?
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> @@ -3068,17 +3065,20 @@ const char *of_clk_get_parent_name(struct device_node *np, int index)
> return NULL;
>
> index = clkspec.args_count ? clkspec.args[0] : 0;
> - count = 0;
>
> /* if there is an indices property, use it to transfer the index
> * specified into an array offset for the clock-output-names property.
> */
> - of_property_for_each_u32(clkspec.np, "clock-indices", prop, vp, pv) {
> - if (index == pv) {
> - index = count;
> - break;
> - }
> - count++;
> + list = of_get_property(clkspec.np, "clock-indices", &len);
> + if (list) {
> + len /= sizeof(*list);
> + for (i = 0; i < len; i++)
> + if (index == be32_to_cpup(list++)) {
> + index = i;
> + break;
> + }
> + if (i == len)
> + return NULL;
> }
Why can't we leave everything in place and check count == len at
the end? i.e.
of_property_for_each_u32(clkspec.np, "clock-indices", prop, vp, pv) {
if (index == pv) {
index = count;
break;
}
count++;
}
if (count == of_property_count_u32_elems(clkspec.np, "clock-indices"))
return NULL
?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-20 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 7:36 [PATCH 1/3] clk: remove redundant negative index check in of_clk_get_parent_name() Masahiro Yamada
2015-11-20 7:36 ` [PATCH 2/3] clk: let of_clk_get_parent_name() fail for invalid clock-indices Masahiro Yamada
2015-11-20 17:45 ` Stephen Boyd [this message]
2015-11-22 6:03 ` Masahiro Yamada
2015-11-24 0:53 ` Stephen Boyd
2015-11-30 8:34 ` Masahiro Yamada
2015-12-01 0:44 ` Stephen Boyd
2015-11-20 7:36 ` [PATCH 3/3] clk: split of_clk_get_parent_name() into two functions Masahiro Yamada
2015-11-21 0:37 ` Stephen Boyd
2015-11-22 5:44 ` Masahiro Yamada
2015-11-24 4:25 ` Masahiro Yamada
2015-12-01 0:49 ` Stephen Boyd
2015-12-01 1:51 ` Masahiro Yamada
2015-11-20 17:18 ` [PATCH 1/3] clk: remove redundant negative index check in of_clk_get_parent_name() Stephen Boyd
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=20151120174509.GQ32672@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=yamada.masahiro@socionext.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