| commit | e2c635999f44324d0c9db3330debd807be809507 | [log] [tgz] |
|---|---|---|
| author | Doug Anderson <dianders@chromium.org> | Sat Aug 31 00:11:21 2013 +0900 |
| committer | Chris Ball <cjb@laptop.org> | Wed Sep 25 21:31:52 2013 -0400 |
| tree | cecefa38d3a35ee3048fcf417af63ac458e198d3 | |
| 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>