OMAP3: PM: fix UART handling when using no_console_suspend
authorKevin Hilman <khilman@ti.com>
Tue, 13 Sep 2011 18:18:44 +0000 (11:18 -0700)
committerKevin Hilman <khilman@ti.com>
Fri, 16 Sep 2011 16:44:50 +0000 (09:44 -0700)
commitdca2d0eb5917ff132d9be13f0afa9ae5d4e80580
treef81db8f8db8f45ff4a71c7b2208f5c66173c0446
parente9a5190aa30d9d9eeead10a978609f46869bfe50
OMAP3: PM: fix UART handling when using no_console_suspend

During the idle/suspend path, we expect the console lock to be held so
that no console output is done during/after the UARTs are idled.

However, when using the no_console_suspend argument on the
command-line, the console driver does not take the console lock.  This
allows the possibility of console activity after UARTs have been
disabled.

To fix, update the current is_suspending() to also check the
console_suspend_enabled flag.

Reported-by: Abhilash Koyamangalath <abhilash.kv@ti.com>
Tested-by: Abhilash Koyamangalath <abhilash.kv@ti.com>
Signed-off-by: Kevin Hilman <khilman@ti.com>
arch/arm/mach-omap2/pm34xx.c