OMAP3: set the core dpll clk rate in its set_rate function.
Subsystems (3)
PATCH 1/1 OMAP3: set the core dpll clk rate in its set_rate function.
The debug l3_ick/rate is not displaying the actual rate of the clock in hardware. This is because, the core dpll set_rate function doesn't update the clk.rate. After fixing, the l3_ick/rate is displaying proper values.
---
* The patch is based on v2.6.39-rc6
* The patch is tested on zoom3.
* The patch is based on discussions from
http://www.mail-archive.com/linux-omap at vger.kernel.org/msg48518.html
arch/arm/mach-omap2/clkt34xx_dpll3m2.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)
arch/arm/mach-omap2/clkt34xx_dpll3m2.c +1 -0
@@ -118,6 +118,7 @@ int omap3_core_dpll_m2_set_rate(struct clk *clk, unsigned long rate) sdrc_cs0->rfr_ctrl, sdrc_cs0->actim_ctrla, sdrc_cs0->actim_ctrlb, sdrc_cs0->mr, 0, 0, 0, 0); + clk->rate = rate;return 0 ; }
Signature · 1 line
1.7.1
PATCH 1/1 OMAP3: set the core dpll clk rate in its set_rate function.
Quoted 8 lines · Avinash.H.M
The debug l3_ick/rate is not displaying the actual rate of the clock in hardware. This is because, the core dpll
set_ratefunction doesn't update the clk.rate. After fixing, the l3_ick/rate is displaying proper values.Signed-off-by Shweta Gulati <[email protected]>Signed-off-by Avinash.H.M <[email protected]>Cc Rajendra Nayak <[email protected]>Cc Paul Wamsley <[email protected]>
Thanks, let's see if we can get this into an -rc.
- Paul
Tony Lindgren
maintainerPATCH 1/1 OMAP3: set the core dpll clk rate in its set_rate function.
Quoted 6 lines · Paul Walmsley
Quoted 4 lines · Avinash.H.M
The debug l3_ick/rate is not displaying the actual rate of the clock in hardware. This is because, the core dpll
set_ratefunction doesn't update the clk.rate. After fixing, the l3_ick/rate is displaying proper values.
Quoted 8 lines
Quoted 4 lines
Signed-off-by Shweta Gulati <[email protected]>Signed-off-by Avinash.H.M <[email protected]>Cc Rajendra Nayak <[email protected]>Cc Paul Wamsley <[email protected]>Acked-by Paul Walmsley <[email protected]>Thanks, let's see if we can get this into an -rc.
Might be out of time as we still should have this sit in for-next too. Anyways, adding into devel-fixes.
Tony