From: Jiada Wang <jiada_wang@mentor.com>
To: Michael Turquette <mturquette@baylibre.com>,
<sboyd@codeaurora.org>, <linux-clk@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <joshua_frkuska@mentor.com>,
<vladimir_zapolskiy@mentor.com>
Subject: Re: [RFC PATCH v2] clk: move check of CLK_SET_RATE_GATE flag to clk_propagate_rate_change()
Date: Thu, 14 Jul 2016 14:15:31 +0900 [thread overview]
Message-ID: <57871FF3.2030306@mentor.com> (raw)
In-Reply-To: <146836257017.73491.10485892804134671614@resonance>
Hello Michael
On 07/13/2016 07:29 AM, Michael Turquette wrote:
> Quoting jiada_wang@mentor.com (2016-07-10 22:33:28)
>> From: Jiada Wang <jiada_wang@mentor.com>
>>
>> Previously CLK_SET_RATE_GATE flag is only checked in clk_set_rate()
>> which only ensures the clock being called by clk_set_rate() won't
>> change rate when it has been prepared if CLK_SET_RATE_GATE flag is set.
>> But a clk_set_rate() request may propagate rate change to these clocks
>> from the requested clock's topmost parent clock to all its offsprings,
>> when any one of these clocks has CLK_SET_RATE_GATE flag set
>> and it has been prepared, the clk_set_rate() request should fail.
>>
>> This patch moves check of CLK_SET_RATE_GATE flag to
>> clk_propagate_rate_change() to ensure all affected clocks will
>> be checked if their rate will be changed after clk_set_rate().
>>
>> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
>> ---
>
> What's different in version 2? It's tradition to put a little version
> changelog here, below the "---" line and above the "diff --git a/..."
> line.
>
version 2 resolves the following kernel warning
"
drivers/clk/clk.c: In function 'clk_propagate_rate_change':
>> drivers/clk/clk.c:1441:3: warning: return makes pointer from integer
without a cast
return -EBUSY;
^
"
I forgot to add a changelog in v2 patch, sorry for the confusion caused.
Thanks,
Jiada
> Regards,
> Mike
>
>> drivers/clk/clk.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
>> index 820a939..2f930c8 100644
>> --- a/drivers/clk/clk.c
>> +++ b/drivers/clk/clk.c
>> @@ -1437,6 +1437,9 @@ static struct clk_core *clk_propagate_rate_change(struct clk_core *core,
>> if (core->rate == core->new_rate)
>> return NULL;
>>
>> + if ((core->flags & CLK_SET_RATE_GATE) && core->prepare_count)
>> + return core;
>> +
>> if (core->notifier_count) {
>> ret = __clk_notify(core, event, core->rate, core->new_rate);
>> if (ret & NOTIFY_STOP_MASK)
>> @@ -1571,9 +1574,6 @@ static int clk_core_set_rate_nolock(struct clk_core *core,
>> if (rate == clk_core_get_rate_nolock(core))
>> return 0;
>>
>> - if ((core->flags & CLK_SET_RATE_GATE) && core->prepare_count)
>> - return -EBUSY;
>> -
>> /* calculate new rates and get the topmost changed clock */
>> top = clk_calc_new_rates(core, rate);
>> if (!top)
>> --
>> 1.7.9.5
>>
>>
next prev parent reply other threads:[~2016-07-14 5:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 5:33 [RFC PATCH v2] clk: move check of CLK_SET_RATE_GATE flag to clk_propagate_rate_change() jiada_wang
2016-07-12 22:29 ` Michael Turquette
2016-07-12 22:29 ` Michael Turquette
2016-07-14 5:15 ` Jiada Wang [this message]
2016-08-10 22:19 ` Stephen Boyd
2016-08-23 7:16 ` Jiada Wang
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=57871FF3.2030306@mentor.com \
--to=jiada_wang@mentor.com \
--cc=joshua_frkuska@mentor.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=vladimir_zapolskiy@mentor.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 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.