]> pilppa.com Git - linux-2.6-omap-h63xx.git/commit
OMAP2/3 clock: don't tinker with hardirqs when they are supposed to be disabled
authorPaul Walmsley <paul@pwsan.com>
Wed, 7 Jan 2009 15:23:46 +0000 (17:23 +0200)
committerTony Lindgren <tony@atomide.com>
Wed, 7 Jan 2009 15:23:46 +0000 (17:23 +0200)
commitb9b6208dadb5e0d8b290900a3ffa911673ca97ed
tree1afb2a36b96e25e1dbe11e66dc7f5b96a041d6a4
parent8f0680aff352906b81c49b0450172ffa690b03bb
OMAP2/3 clock: don't tinker with hardirqs when they are supposed to be disabled

Clock rate change code executes inside a spinlock with hardirqs
disabled.  The only code that should be messing around with the
hardirq state should be the plat-omap/clock.c code.  In the
omap2_reprogram_dpllcore() case, this probably just wastes cycles, but
in the omap3_core_dpll_m2_set_rate() case, this is a nasty bug.

Signed-off-by: Paul Walmsley <paul@pwsan.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
arch/arm/mach-omap2/clock24xx.c
arch/arm/mach-omap2/clock34xx.c