diff options
| author | Doug Anderson <dianders@chromium.org> | 2013-08-31 00:11:21 +0900 |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2013-09-25 21:31:52 -0400 |
| commit | e2c635999f44324d0c9db3330debd807be809507 (patch) | |
| tree | cecefa38d3a35ee3048fcf417af63ac458e198d3 /block/blk-integrity.c | |
| parent | 369ac8614fcef040f96f6548acb43dcefebd21b9 (diff) | |
mmc: dw_mmc: Add exynos resume_noirq callback to clear WAKEUP_INT
If the WAKEUP_INT is asserted at wakeup and not cleared, we'll end up
looping around forever. This has been seen to happen on exynos5420
silicon despite the fact that we haven't enabled any wakeup events due
to a silicon errata. It is safe to do on all exynos variants.
Signed-off-by: Doug Anderson <dianders@chromium.org>
Acked-by: Seungwon Jeon <tgih.jun@samsung.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'block/blk-integrity.c')
0 files changed, 0 insertions, 0 deletions