diff options
author | Ulf Hansson <ulf.hansson@linaro.org> | 2017-05-08 23:52:04 +0200 |
---|---|---|
committer | Ulf Hansson <ulf.hansson@linaro.org> | 2017-06-20 10:30:10 +0200 |
commit | 52c8212d80b69d2197bb8506384b6e6a0aef7fb7 (patch) | |
tree | 386ccbf33e6ea6cf72719dda6e1914f074bf860d /drivers/Makefile | |
parent | 773a9ef85f02f6a82f58244f33cb628ad1ecac21 (diff) | |
download | linux-52c8212d80b69d2197bb8506384b6e6a0aef7fb7.tar.bz2 |
mmc: core: Don't do eMMC HW reset when resuming the eMMC card
In case if a pwrseq-emmc has been bound to the host, a call to
mmc_power_up() triggers an eMMC HW reset via the pwrseq_emmc's
->post_power_on() callback. This isn't really what we want, as
mmc_power_up() is called each time when resuming the card.
As a matter of fact, the current approach may also violate the eMMC spec,
as the involved delays managed in pwrseq_emmc assumes both VCC and VCCQ has
been turned on, which isn't the case for VCCQ, unless the regulator is
always on.
Fix this behaviour by aligning to the same procedure used when the mmc host
implements the ->hw_reset() callback and has the MMC_CAP_HW_RESET flag set.
In this way the eMMC HW reset is issued at card detection scan, to cope
with bogus bootloaders and in the error recovery path via the mmc specific
bus_ops->reset() callback.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
Diffstat (limited to 'drivers/Makefile')
0 files changed, 0 insertions, 0 deletions