From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Shweta Gulati <shweta.gulati@ti.com>
Cc: linux-omap@vger.kernel.org, Rajendra Nayak <rnayak@ti.com>,
Paul Wamsley <paul@pwsan.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate'
Date: Wed, 20 Apr 2011 19:42:21 +0400 [thread overview]
Message-ID: <4DAEFEDD.1040106@ru.mvista.com> (raw)
In-Reply-To: <1303291509-2305-1-git-send-email-shweta.gulati@ti.com>
Hello.
On 20-04-2011 13:25, Shweta Gulati wrote:
> From: Gulati, Shweta<shweta.gulati@ti.com>
> Core Clk Tree shows incorrect Clk rates at OPP50, as
> in commit e07f469d284ca3d1f5dcf5438c22982be98bc071
Please also specify that commit's summary -- for human readers.
> 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.
> 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>
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate'
Date: Wed, 20 Apr 2011 19:42:21 +0400 [thread overview]
Message-ID: <4DAEFEDD.1040106@ru.mvista.com> (raw)
In-Reply-To: <1303291509-2305-1-git-send-email-shweta.gulati@ti.com>
Hello.
On 20-04-2011 13:25, Shweta Gulati wrote:
> From: Gulati, Shweta<shweta.gulati@ti.com>
> Core Clk Tree shows incorrect Clk rates at OPP50, as
> in commit e07f469d284ca3d1f5dcf5438c22982be98bc071
Please also specify that commit's summary -- for human readers.
> 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.
> 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>
WBR, Sergei
next prev parent reply other threads:[~2011-04-20 15:43 UTC|newest]
Thread overview: 24+ 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 9:25 ` Shweta Gulati
2011-04-20 13:35 ` Janorkar, Mayuresh
2011-04-20 13:35 ` Janorkar, Mayuresh
2011-04-21 13:27 ` Gulati, Shweta
2011-04-21 13:27 ` Gulati, Shweta
2011-04-20 15:42 ` Sergei Shtylyov [this message]
2011-04-20 15:42 ` Sergei Shtylyov
2011-04-21 13:27 ` Gulati, Shweta
2011-04-21 13:27 ` Gulati, Shweta
2011-04-20 19:55 ` Paul Walmsley
2011-04-20 19:55 ` Paul Walmsley
2011-04-21 13:32 ` Gulati, Shweta
2011-04-21 13:32 ` Gulati, Shweta
2011-04-23 17:00 ` Paul Walmsley
2011-04-23 17:00 ` Paul Walmsley
2011-05-06 21:49 ` Paul Walmsley
2011-05-06 21:49 ` Paul Walmsley
2011-05-10 10:55 ` Gulati, Shweta
2011-05-10 10:55 ` Gulati, Shweta
2011-05-10 13:42 ` Avinash.H.M.
2011-05-10 13:42 ` Avinash.H.M.
2011-05-11 4:19 ` Gulati, Shweta
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=4DAEFEDD.1040106@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=shweta.gulati@ti.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.