From: shweta.gulati@ti.com (Gulati, Shweta)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate'
Date: Thu, 21 Apr 2011 18:57:26 +0530 [thread overview]
Message-ID: <BANLkTin4jETyDMDAE70M7rook=D4cW_mqQ@mail.gmail.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB033D7EB768@dbde02.ent.ti.com>
Hi,
On Wed, Apr 20, 2011 at 7:05 PM, Janorkar, Mayuresh <mayur@ti.com> wrote:
>
>
>> -----Original Message-----
>> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
>> owner at vger.kernel.org] On Behalf Of Gulati, Shweta
>> Sent: Wednesday, April 20, 2011 2:55 PM
>> To: linux-omap at vger.kernel.org
>> Cc: linux-arm-kernel at lists.infradead.org; Gulati, Shweta; Nayak, Rajendra;
>> Paul Wamsley
>> Subject: [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate'
>>
>> From: Gulati, Shweta <shweta.gulati@ti.com>
>>
>> Core Clk Tree shows incorrect Clk rates at OPP50, as
>> in commit e07f469d284ca3d1f5dcf5438c22982be98bc071
>> calling of 'recalc' in API clk_set_rate is unintentionally
>> removed, because of which clock's tree rates get goofed
>> up when DVFS happens. This Patch adds recalc API back.
>
> I see that the patch is not adding API back.
> It is adding a call to the API.
Will Modify Commit message.
>>
>> Tested on OMAP3630 SDP Board.
>>
>> Signed-off-by: Shweta Gulati <shweta.gulati@ti.com>
>> Cc: Rajendra Nayak <rnayak@ti.com>
>> Cc: Paul Wamsley <paul@pwsan.com>
>> ---
>> ?arch/arm/plat-omap/clock.c | ? ?5 ++++-
>> ?1 files changed, 4 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
>> index c9122dd..5a0d06b 100644
>> --- a/arch/arm/plat-omap/clock.c
>> +++ b/arch/arm/plat-omap/clock.c
>> @@ -130,8 +130,11 @@ int clk_set_rate(struct clk *clk, unsigned long rate)
>>
>> ? ? ? spin_lock_irqsave(&clockfw_lock, flags);
>> ? ? ? ret = arch_clock->clk_set_rate(clk, rate);
>> - ? ? if (ret == 0)
>> + ? ? if (ret == 0) {
>
> checking if (!ret) is an intelligent way.
> But it is an individual's choice.
It doesn't make much difference.
>> + ? ? ? ? ? ? if (clk->recalc)
>> + ? ? ? ? ? ? ? ? ? ? clk->rate = clk->recalc(clk);
>> ? ? ? ? ? ? ? propagate_rate(clk);
>> + ? ? }
>> ? ? ? spin_unlock_irqrestore(&clockfw_lock, flags);
>>
>> ? ? ? return ret;
>> --
>> 1.7.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo at vger.kernel.org
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
--
Thanks,
Regards,
Shweta
next prev parent reply other threads:[~2011-04-21 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 9:25 [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate' Shweta Gulati
2011-04-20 13:35 ` Janorkar, Mayuresh
2011-04-21 13:27 ` Gulati, Shweta [this message]
2011-04-20 15:42 ` Sergei Shtylyov
2011-04-21 13:27 ` Gulati, Shweta
2011-04-20 19:55 ` Paul Walmsley
2011-04-21 13:32 ` Gulati, Shweta
2011-04-23 17:00 ` Paul Walmsley
2011-05-06 21:49 ` Paul Walmsley
2011-05-10 10:55 ` Gulati, Shweta
2011-05-10 13:42 ` Avinash.H.M.
2011-05-11 4:19 ` Gulati, Shweta
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='BANLkTin4jETyDMDAE70M7rook=D4cW_mqQ@mail.gmail.com' \
--to=shweta.gulati@ti.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 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).