diff options
author | Ulf Hansson <ulf.hansson@linaro.org> | 2013-06-10 17:03:45 +0200 |
---|---|---|
committer | Chris Ball <cjb@laptop.org> | 2013-06-27 12:39:21 -0400 |
commit | 43235679341510f58a86eb75ab23cbae4bdc59b8 (patch) | |
tree | 769bffa7f730d317dc4690c0ba15c244e3de3cbd /include/linux/mmc | |
parent | 486fdbbc1483504cde0314e33e47bc32e9d38186 (diff) | |
download | linux-stable-43235679341510f58a86eb75ab23cbae4bdc59b8.tar.gz linux-stable-43235679341510f58a86eb75ab23cbae4bdc59b8.tar.bz2 linux-stable-43235679341510f58a86eb75ab23cbae4bdc59b8.zip |
mmc: core: Enable power_off_notify for eMMC shutdown sequence
In suspend mode it is important to save power. If the host is able to
cut buth vcc and vccq, the MMC_CAP2_POWEROFF_NOTIFY shall be set. It
will mean the card will be completely powered down at suspend and the
power off notification cmd will be sent prior power down.
It seems common not being able to cut both vcc and vccq for a host. In
this situation we issue the sleep cmd in favor of the power off
notification cmd, to save more power.
While maintainng the above policy, we also want to make use of the
power off notification in the shutdown sequence, even in the case were
the host has not set MMC_CAP2_POWEROFF_NOTIFY, since we know vcc and
vccq will regardless be cut.
We accomplish this by always enabling the power off notification byte
in the EXT_CSD and issue the power off notification when either
MMC_CAP2_POWEROFF_NOTIFY is set or we are executing a shutdown.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'include/linux/mmc')
0 files changed, 0 insertions, 0 deletions