Hi Peter, On 01/03/2013 07:46 AM, Peter Ujfalusi wrote: > We need to lock ABE DPPL on al OMAP4 revisions, not only for OMAP446x > > Signed-off-by: Peter Ujfalusi <[email protected]> > --- > arch/arm/mach-omap2/cclock44xx_data.c | 14 ++++++-------- > 1 file changed, 6 insertions(+), 8 deletions(-) > > diff --git a/arch/arm/mach-omap2/cclock44xx_data.c > b/arch/arm/mach-omap2/cclock44xx_data.c > index 5789a5e..79c32ce 100644 > --- a/arch/arm/mach-omap2/cclock44xx_data.c > +++ b/arch/arm/mach-omap2/cclock44xx_data.c > @@ -2023,17 +2023,15 @@ int __init omap4xxx_clk_init(void) > ARRAY_SIZE(enable_init_clks)); > > /* > - * On OMAP4460 the ABE DPLL fails to turn on if in idle low-power > + * On OMAP4 the ABE DPLL fails to turn on if in idle low-power > * state when turning the ABE clock domain. Workaround this by > * locking the ABE DPLL on boot.
I am not sure that this change to the comment is completely accurate. On OMAP4430 I did not see any issues with the DPLL failing to turn on if the DPLL was not locked. I only saw this particular problem on the 4460. Therefore, it may be better to leave the comment as-is and add an additional sentence to state that the DPLL should be locked for all OMAP4 devices for audio to work correctly. Cheers Jon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
