Hi Mike, On Thu, 8 Aug 2013, Mike Turquette wrote: > Quoting Rajendra Nayak (2013-08-08 03:14:11) > > On OMAP4 we have clk_set_rate()s being done for a few > > DPLL clock nodes, as part of the clock init code, since > > the bootloaders no longer locks these DPLLs. > ... > > Signed-off-by: Rajendra Nayak <rnayak@xxxxxx> > > Taken into clk-next. Thanks for the fix. Besides the annoying prints is > there a functional regression fixed by this? If so I can take into > clk-fixes as needed. It's best if I take this patch upstream. That way, potential merge conflicts are avoided, since I might have other changes to arch/arm/mach-omap2/cclock44xx_data.c to send upstream at the same time. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html