diff options
author | 2019-09-11 14:09:20 +0200 | |
---|---|---|
committer | 2019-09-11 16:10:18 +0200 | |
commit | 1c81d69d4c98aab56c5a7d5a810f84aefdb37e9b (patch) | |
tree | 1e1a1c6fe7211beceb57b2f72dc13a03e6534118 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | mmc: dw_mmc: Re-store SDIO IRQs mask at system resume (diff) | |
download | linux-dev-1c81d69d4c98aab56c5a7d5a810f84aefdb37e9b.tar.xz linux-dev-1c81d69d4c98aab56c5a7d5a810f84aefdb37e9b.zip |
mmc: mtk-sd: Re-store SDIO IRQs mask at system resume
In cases when SDIO IRQs have been enabled, runtime suspend is prevented by
the driver. However, this still means msdc_runtime_suspend|resume() gets
called during system suspend/resume, via pm_runtime_force_suspend|resume().
This means during system suspend/resume, the register context of the mtk-sd
device most likely loses its register context, even in cases when SDIO IRQs
have been enabled.
To re-enable the SDIO IRQs during system resume, the mtk-sd driver
currently relies on the mmc core to re-enable the SDIO IRQs when it resumes
the SDIO card, but this isn't the recommended solution. Instead, it's
better to deal with this locally in the mtk-sd driver, so let's do that.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions