From: b.brezillon@overkiz.com (Boris BREZILLON)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: add strict of_clk_init dependency check
Date: Wed, 05 Feb 2014 16:07:19 +0100 [thread overview]
Message-ID: <52F253A7.9030805@overkiz.com> (raw)
In-Reply-To: <52F25324.90108@free-electrons.com>
On 05/02/2014 16:05, Gregory CLEMENT wrote:
> On 05/02/2014 15:48, Gregory CLEMENT wrote:
>> Hi Boris,
>>
>> On 05/02/2014 10:48, Boris BREZILLON wrote:
>>> The parent dependency check is only available on the first parent of a given
>>> clk.
>>>
>>> Add support for strict dependency check: all parents of a given clk must be
>>> initialized.
>>>
>>> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
>>> ---
>>>
>>> Hello Gregory,
>>>
>>> This patch adds support for strict check on clk dependencies (check if all
>>> parents specified by an DT clk node are initialized).
>>>
>>> I'm not sure this is what you were expecting (maybe testing the first parent
>>> is what you really want), so please feel free to tell me if I'm wrong.
>>>
>>> Best Regards,
>>>
>>> Boris
>>>
>>> drivers/clk/clk.c | 27 +++++++++++++++++++++------
>>> 1 file changed, 21 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>>> index beb0f8b..6849769 100644
>>> --- a/drivers/clk/clk.c
>>> +++ b/drivers/clk/clk.c
>>> @@ -2543,22 +2543,37 @@ static int parent_ready(struct device_node *np)
>>> {
>>> struct of_phandle_args clkspec;
>>> struct of_clk_provider *provider;
>>> + int num_parents;
>>> + bool found;
>>> + int i;
>>>
>>> /*
>>> * If there is no clock parent, no need to wait for them, then
>>> * we can consider their absence as being ready
>>> */
>>> - if (of_parse_phandle_with_args(np, "clocks", "#clock-cells", 0,
>>> - &clkspec))
>>> + num_parents = of_count_phandle_with_args(np, "clocks", "#clock-cells");
>>> + if (num_parents <= 0)
>>> return 1;
>>>
>>> - /* Check if we have such a provider in our array */
>>> - list_for_each_entry(provider, &of_clk_providers, link) {
>>> - if (provider->node == clkspec.np)
>>> + for (i = 0; i < num_parents; i++) {
>>> + if (of_parse_phandle_with_args(np, "clocks", "#clock-cells", i,
>>> + &clkspec))
>>> return 1;
>>> +
>>> + /* Check if we have such a provider in our array */
>>> + found = false;
>>> + list_for_each_entry(provider, &of_clk_providers, link) {
>>> + if (provider->node == clkspec.np) {
>>> + found = true;
>>> + break;
>> Hum this means that as soon as you have one parent then you consider it
>> as ready. It is better of what I have done because I only test the 1st
>> parent. However I wondered if we should go further by ensuring all the
>> parents are ready.
> My bad, I read the code too fast. Your code already checks that all the
> parents are ready.
>
> So if you agree I will merge your code with mine and send a new patch.
That's fine by me.
>
>> If I am right, there is more than one parent only for the muxer. In this
>> case is it really expected that all the parent are ready?
>>
>> Thanks,
>>
>> Gregory
>>
>>> + }
>>> + }
>>> +
>>> + if (!found)
>>> + return 0;
>>> }
>>>
>>> - return 0;
>>> + return 1;
>>> }
>>>
>>> /**
>>>
>>
>
WARNING: multiple messages have this Message-ID (diff)
From: Boris BREZILLON <b.brezillon@overkiz.com>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] clk: add strict of_clk_init dependency check
Date: Wed, 05 Feb 2014 16:07:19 +0100 [thread overview]
Message-ID: <52F253A7.9030805@overkiz.com> (raw)
In-Reply-To: <52F25324.90108@free-electrons.com>
On 05/02/2014 16:05, Gregory CLEMENT wrote:
> On 05/02/2014 15:48, Gregory CLEMENT wrote:
>> Hi Boris,
>>
>> On 05/02/2014 10:48, Boris BREZILLON wrote:
>>> The parent dependency check is only available on the first parent of a given
>>> clk.
>>>
>>> Add support for strict dependency check: all parents of a given clk must be
>>> initialized.
>>>
>>> Signed-off-by: Boris BREZILLON <b.brezillon@overkiz.com>
>>> ---
>>>
>>> Hello Gregory,
>>>
>>> This patch adds support for strict check on clk dependencies (check if all
>>> parents specified by an DT clk node are initialized).
>>>
>>> I'm not sure this is what you were expecting (maybe testing the first parent
>>> is what you really want), so please feel free to tell me if I'm wrong.
>>>
>>> Best Regards,
>>>
>>> Boris
>>>
>>> drivers/clk/clk.c | 27 +++++++++++++++++++++------
>>> 1 file changed, 21 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>>> index beb0f8b..6849769 100644
>>> --- a/drivers/clk/clk.c
>>> +++ b/drivers/clk/clk.c
>>> @@ -2543,22 +2543,37 @@ static int parent_ready(struct device_node *np)
>>> {
>>> struct of_phandle_args clkspec;
>>> struct of_clk_provider *provider;
>>> + int num_parents;
>>> + bool found;
>>> + int i;
>>>
>>> /*
>>> * If there is no clock parent, no need to wait for them, then
>>> * we can consider their absence as being ready
>>> */
>>> - if (of_parse_phandle_with_args(np, "clocks", "#clock-cells", 0,
>>> - &clkspec))
>>> + num_parents = of_count_phandle_with_args(np, "clocks", "#clock-cells");
>>> + if (num_parents <= 0)
>>> return 1;
>>>
>>> - /* Check if we have such a provider in our array */
>>> - list_for_each_entry(provider, &of_clk_providers, link) {
>>> - if (provider->node == clkspec.np)
>>> + for (i = 0; i < num_parents; i++) {
>>> + if (of_parse_phandle_with_args(np, "clocks", "#clock-cells", i,
>>> + &clkspec))
>>> return 1;
>>> +
>>> + /* Check if we have such a provider in our array */
>>> + found = false;
>>> + list_for_each_entry(provider, &of_clk_providers, link) {
>>> + if (provider->node == clkspec.np) {
>>> + found = true;
>>> + break;
>> Hum this means that as soon as you have one parent then you consider it
>> as ready. It is better of what I have done because I only test the 1st
>> parent. However I wondered if we should go further by ensuring all the
>> parents are ready.
> My bad, I read the code too fast. Your code already checks that all the
> parents are ready.
>
> So if you agree I will merge your code with mine and send a new patch.
That's fine by me.
>
>> If I am right, there is more than one parent only for the muxer. In this
>> case is it really expected that all the parent are ready?
>>
>> Thanks,
>>
>> Gregory
>>
>>> + }
>>> + }
>>> +
>>> + if (!found)
>>> + return 0;
>>> }
>>>
>>> - return 0;
>>> + return 1;
>>> }
>>>
>>> /**
>>>
>>
>
next prev parent reply other threads:[~2014-02-05 15:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:59 [PATCH] clk: respect the clock dependencies in of_clk_init Gregory CLEMENT
2014-02-04 22:59 ` Gregory CLEMENT
2014-02-05 5:09 ` Jason Cooper
2014-02-05 5:09 ` Jason Cooper
2014-02-05 8:45 ` Boris BREZILLON
2014-02-05 8:45 ` Boris BREZILLON
2014-02-05 9:48 ` [PATCH] clk: add strict of_clk_init dependency check Boris BREZILLON
2014-02-05 9:48 ` Boris BREZILLON
2014-02-05 14:48 ` Gregory CLEMENT
2014-02-05 14:48 ` Gregory CLEMENT
2014-02-05 15:05 ` Gregory CLEMENT
2014-02-05 15:05 ` Gregory CLEMENT
2014-02-05 15:07 ` Boris BREZILLON [this message]
2014-02-05 15:07 ` Boris BREZILLON
2014-02-05 23:11 ` [PATCH] clk: respect the clock dependencies in of_clk_init Sebastian Hesselbarth
2014-02-05 23:11 ` Sebastian Hesselbarth
2014-02-07 13:06 ` Emilio López
2014-02-07 13:06 ` Emilio López
2014-02-07 14:24 ` Jason Cooper
2014-02-07 14:24 ` Jason Cooper
2014-02-07 14:43 ` Ezequiel Garcia
2014-02-07 14:43 ` Ezequiel Garcia
2014-02-07 14:49 ` Gregory CLEMENT
2014-02-07 14:49 ` Gregory CLEMENT
2014-02-07 15:00 ` Emilio López
2014-02-07 15:00 ` Emilio López
2014-02-07 15:12 ` Gregory CLEMENT
2014-02-07 15:12 ` Gregory CLEMENT
2014-02-07 16:16 ` Emilio López
2014-02-07 16:16 ` Emilio López
2014-02-07 18:10 ` Gregory CLEMENT
2014-02-07 18:10 ` Gregory CLEMENT
2014-02-07 18:17 ` Emilio López
2014-02-07 18:17 ` Emilio López
2014-02-07 23:15 ` Sebastian Hesselbarth
2014-02-07 23:15 ` Sebastian Hesselbarth
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=52F253A7.9030805@overkiz.com \
--to=b.brezillon@overkiz.com \
--cc=linux-arm-kernel@lists.infradead.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.