diff options
author | Kevin Hilman <khilman@deeprootsystems.com> | 2010-06-09 13:53:09 +0300 |
---|---|---|
committer | Tony Lindgren <tony@atomide.com> | 2010-06-10 15:37:41 +0300 |
commit | 0b96a3a3c5c5e6e1b79a05c23d110d59518f4fc8 (patch) | |
tree | cd4b60e4ce289a4baeaf53f7955d56df43ffe6ee /arch/arm/mach-omap2/clock44xx_data.c | |
parent | f7ec0b0b16c97a75a1b6aa8bc8b32548003f3339 (diff) | |
download | linux-0b96a3a3c5c5e6e1b79a05c23d110d59518f4fc8.tar.gz linux-0b96a3a3c5c5e6e1b79a05c23d110d59518f4fc8.tar.bz2 linux-0b96a3a3c5c5e6e1b79a05c23d110d59518f4fc8.zip |
OMAP3: PM: fix IO daisy chain enable to use PM_WKEN reg
Checking to se if the IO daisy chain is enabled should be checking the
PM_WKEN register, not the PM_WKST register. Reading PM_WKST tells us
if an event occurred, not whether or not it is enabled.
Apparently, we've been lucky until now in that a pending event has not
been there during enable. However, on 3630/Zoom3, I noticed because
of the WARN that this timeout was always happening.
Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/mach-omap2/clock44xx_data.c')
0 files changed, 0 insertions, 0 deletions