Hi,
On Tue, May 10, 2011 at 7:12 PM, Avinash.H.M. avinas...@ti.com wrote:
On Tue, May 10, 2011 at 04:25:19PM +0530, Gulati, Shweta wrote:
Hi,
On Sat, May 7, 2011 at 3:19 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code
Hi,
On Sat, May 7, 2011 at 3:19 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update clk.rate, I will submit patch fixing that bug and will
make sure that
set_rate
On Tue, May 10, 2011 at 04:25:19PM +0530, Gulati, Shweta wrote:
Hi,
On Sat, May 7, 2011 at 3:19 AM, Paul Walmsley p...@pwsan.com wrote:
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate'
doesn't update clk.rate, I will submit patch fixing that bug and will
make sure that
set_rate of all clocks should update clk.rate
Ping. Do you plan to post this
On Thu, 21 Apr 2011, Gulati, Shweta wrote:
Yes, but in current code clk_set_rate of dpll3_m2 -
'omap3_core_dpll_m2_set_rate' doesn't update clk.rate, I will submit
patch fixing that bug and will make sure that set_rate of all clocks
should update clk.rate
Yes, that's the right thing to
: linux-arm-ker...@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.gul...@ti.com
Core Clk Tree shows incorrect Clk rates at OPP50, as
in commit
Hi,
On Wed, Apr 20, 2011 at 9:12 PM, Sergei Shtylyov sshtyl...@mvista.com wrote:
Hello.
On 20-04-2011 13:25, Shweta Gulati wrote:
From: Gulati, Shwetashweta.gul...@ti.com
Core Clk Tree shows incorrect Clk rates at OPP50, as
in commit e07f469d284ca3d1f5dcf5438c22982be98bc071
Please
Hi,
On Thu, Apr 21, 2011 at 1:25 AM, Paul Walmsley p...@pwsan.com wrote:
Hi
On Wed, 20 Apr 2011, Shweta Gulati wrote:
From: Gulati, Shweta shweta.gul...@ti.com
Core Clk Tree shows incorrect Clk rates at OPP50, as
in commit e07f469d284ca3d1f5dcf5438c22982be98bc071
calling of 'recalc' in
From: Gulati, Shweta shweta.gul...@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
Wamsley
Subject: [PATCH] OMAP: Added recalculation of clock rate in 'clk_set_rate'
From: Gulati, Shweta shweta.gul...@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
Hello.
On 20-04-2011 13:25, Shweta Gulati wrote:
From: Gulati, Shwetashweta.gul...@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
Hi
On Wed, 20 Apr 2011, Shweta Gulati wrote:
From: Gulati, Shweta shweta.gul...@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,
That's intentional. struct
12 matches
Mail list logo
