summaryrefslogtreecommitdiff
path: root/net/rds/iw.h
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@linaro.org>2013-05-02 12:02:39 (GMT)
committerChris Ball <cjb@laptop.org>2013-05-26 18:23:17 (GMT)
commitc4d770d72492df510077b277f21ac5f0dad9e5eb (patch)
tree60412abaad7c69267483d368afeff4d0a769a82b /net/rds/iw.h
parente94cfef698aae6b209d8918dd319312e4b02118d (diff)
downloadlinux-fsl-qoriq-c4d770d72492df510077b277f21ac5f0dad9e5eb.tar.xz
mmc: core: Support aggressive power management for (e)MMC/SD
Aggressive power management is suitable when saving power is essential. At request inactivity timeout, aka pm runtime autosuspend timeout, the card will be suspended. Once a new request arrives, the card will be re-initalized and thus the first request will suffer from a latency. This latency is card-specific, experiments has shown in general that SD-cards has quite poor initialization time, around 300ms-1100ms. eMMC is not surprisingly far better but still a couple of hundreds of ms has been observed. Except for the request latency, it is important to know that suspending the card will also prevent the card from executing internal house-keeping operations in idle mode. This could mean degradation in performance. To use this feature make sure the request inactivity timeout is chosen carefully. This has not been done as a part of this patch. Enable this feature by using host cap MMC_CAP_AGGRESSIVE_PM and by setting CONFIG_MMC_UNSAFE_RESUME. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'net/rds/iw.h')
0 files changed, 0 insertions, 0 deletions