diff options
| author | Ulf Hansson <ulf.hansson@linaro.org> | 2019-06-18 00:52:59 +0200 |
|---|---|---|
| committer | Ulf Hansson <ulf.hansson@linaro.org> | 2019-07-10 13:19:31 +0200 |
| commit | 6ebc581c3f9e6fd11a1c9da492a5e05bbe96885a (patch) | |
| tree | e56849d396572b47a3d18cd9b50d5b2ad7b5ca77 /Documentation | |
| parent | 7fbbe725378d62c30a076742a60a7e1812a2515a (diff) | |
| download | linux-6ebc581c3f9e6fd11a1c9da492a5e05bbe96885a.tar.bz2 | |
mmc: sdio: Don't re-initialize powered-on removable SDIO cards at resume
It looks like the original idea behind always doing a re-initialization of
a removable SDIO card during system resume in mmc_sdio_resume(), is to try
to play safe to detect whether the card has been removed.
However, this seems like a really a bad idea as it will most likely screw
things up, especially when the card is expected to remain powered on during
system suspend by the SDIO func driver.
Let's fix this, simply by trusting that the detect work checks if the card
is alive and inserted, which is being scheduled at the PM_POST_SUSPEND
notification anyway.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Tested-by: Douglas Anderson <dianders@chromium.org>
Reviewed-by: Douglas Anderson <dianders@chromium.org>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions