sh: propagate r_clk
PATCH 1/1 sh: propagate r_clk
From: Magnus Damm <[email protected]>
Make sure the 32 KHz r_clk rate gets propagated correctly. Without this fix the clocks for RTC, CMT, KEYSC and RWDT are stuck at 0 Hz.
---
arch/sh/kernel/cpu/sh4a/clock-sh7722.c | 2 ++ 1 file changed, 2 insertions(+)
arch/sh/kernel/cpu/sh4a/clock-sh7722.c +2 -0
@@ -838,5 +838,7 @@ int __init arch_clk_init(void)clk_put (clk); } +clk_recalc_rate (&sh7722_r_clock);/* make sure rate gets propagated */ +return 0 ; }
Quoted 6 lines · Magnus Damm
From: Magnus Damm <[email protected]>
Make sure the 32 KHz
r_clkrate gets propagated correctly. Without this fix the clocks for RTC, CMT, KEYSC and RWDT are stuck at 0 Hz.Signed-off-by Magnus Damm <[email protected]>
Does this apply to 2.6.28 also, or does it depend on your rate propagation changes that are aimed at the merge window?
Quoted 10 lines · Paul Mundt
Quoted 6 lines · Magnus Damm
From: Magnus Damm <[email protected]>
Make sure the 32 KHz
r_clkrate gets propagated correctly. Without this fix the clocks for RTC, CMT, KEYSC and RWDT are stuck at 0 Hz.Signed-off-by Magnus Damm <[email protected]>Does this apply to 2.6.28 also, or does it depend on your rate propagation changes that are aimed at the merge window?
2.6.29 only, thanks.
/ magnus
Paul Mundt
AppliedQuoted 7 lines · Magnus Damm
Quoted 6 lines · Paul Mundt
Quoted 5 lines · Magnus Damm
From: Magnus Damm <[email protected]>
Make sure the 32 KHz
r_clkrate gets propagated correctly. Without this fix the clocks for RTC, CMT, KEYSC and RWDT are stuck at 0 Hz.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Signed-off-by Magnus Damm <[email protected]>Does this apply to 2.6.28 also, or does it depend on your rate propagation changes that are aimed at the merge window?
2.6.29 only, thanks.
Applied, thanks.