diff options
| author | Lokesh Vutla <lokeshvutla@ti.com> | 2012-06-18 07:23:16 +0200 |
|---|---|---|
| committer | Wim Van Sebroeck <wim@iguana.be> | 2012-07-23 12:50:11 +0200 |
| commit | 41814eed414ab3cef3d2b857ae3690a2b4888291 (patch) | |
| tree | f027af4b049e2bcc366be42916b98c425fbce483 /kernel/printk.c | |
| parent | watchdog: ie6xx_wdt: section mismatch in ie6xx_wdt_probe() (diff) | |
| download | linux-41814eed414ab3cef3d2b857ae3690a2b4888291.tar.xz linux-41814eed414ab3cef3d2b857ae3690a2b4888291.zip | |
Watchdog: OMAP: Fix the runtime pm code to avoid module getting stuck intransition state.
OMAP watchdog driver is adapted to runtime PM like a general device
driver but it is not appropriate. It is causing couple of functional
issues.
1. On OMAP4 SYSCLK can't be gated, because of issue with WDTIMER2 module,
which constantly stays in "in transition" state. Value of register
CM_WKUP_WDTIMER2_CLKCTRL is always 0x00010000 in this case.
Issue occurs immediately after first idle, when hwmod framework tries
to disable WDTIMER2 functional clock - "wd_timer2_fck". After this
module falls to "in transition" state, and SYSCLK gating is blocked.
2. Due to runtime PM, watchdog timer may be completely disabled.
In current code base watchdog timer is not disabled only because of
issue 1. Otherwise state of WDTIMER2 module will be "Disabled", and there
will be no interrupts from omap_wdt. In other words watchdog will not
work at all.
Watchdong is a special IP and it should not be disabled otherwise
purpose of it itself is defeated. Watchdog functional clock should
never be disabled. This patch updates the runtime PM handling in
driver so that runtime PM is limited only during probe/shutdown
and suspend/resume.
The patch fixes issue 1 and 2
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
Diffstat (limited to 'kernel/printk.c')
0 files changed, 0 insertions, 0 deletions