On Thu, Dec 8, 2011 at 2:11 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: > On Sat, Nov 19, 2011 at 12:18 AM, Omar Ramirez Luna <omar.ramirez@xxxxxx> wrote: >> Given that dm timer framework doesn't support request of clocks >> by soft | hard irqs because some recent changes, tidspbridge needs >> to request its clocks on init and enable/disable them on demand. >> >> This was first seen on 3.2-rc1. >> >> Signed-off-by: Omar Ramirez Luna <omar.ramirez@xxxxxx> > > Tested-by: Felipe Contreras <felipe.contreras@xxxxxxxxx> > Reviewed-by: Felipe Contreras <felipe.contreras@xxxxxxxxx> Thanks! > Something the commit message didn't mention is that this fixes a nasty > continuous loop that happens as soon as you load the module. Indeed. > Definitely 3.2-fix material IMO :) I believe it was pushed to staging-next... I'm rooting so it can be pushed to staging-linus :) Regards, Omar -- 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
