On Sat, Nov 19, 2011 at 12:18 AM, Omar Ramirez Luna <[email protected]> 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 <[email protected]>
Tested-by: Felipe Contreras <[email protected]> Reviewed-by: Felipe Contreras <[email protected]> Something the commit message didn't mention is that this fixes a nasty continuous loop that happens as soon as you load the module. Definitely 3.2-fix material IMO :) Cheers. -- Felipe Contreras -- 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
