diff options
| author | Jaehoon Chung <jh80.chung@samsung.com> | 2012-09-17 08:42:02 +0000 |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2012-10-03 10:05:12 -0400 |
| commit | 950d56acce5d401f477b91d0177605b543d63d07 (patch) | |
| tree | 205505f3976d02c6ef2fa9d6c911407f0e0f6c80 /include/linux/mmc/dw_mmc.h | |
| parent | bec9d4e5939987053169a9bb48fc58b6a2d3e237 (diff) | |
| download | talos-obmc-linux-950d56acce5d401f477b91d0177605b543d63d07.tar.gz talos-obmc-linux-950d56acce5d401f477b91d0177605b543d63d07.zip | |
mmc: support BKOPS feature for eMMC
Enable eMMC background operations (BKOPS) feature.
If URGENT_BKOPS is set after a response, note that BKOPS are required.
Immediately run BKOPS if required. Read/write operations should be
requested during BKOPS(LEVEL-1), then issue HPI to interrupt the
ongoing BKOPS and service the foreground operation.
(This patch only controls the LEVEL2/3.)
When repeating the writing 1GB data, at a certain time, performance is
decreased. At that time, card triggers the Level-3 or Level-2. After
running bkops, performance is recovered.
Future considerations:
* Check BKOPS_LEVEL=1 and start BKOPS in a preventive manner.
* Interrupt ongoing BKOPS before powering off the card.
* How do we get BKOPS_STATUS value (periodically send ext_csd command)?
* If using periodic bkops, also consider runtime_pm control.
Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: Konstantin Dorfman <kdorfman@codeaurora.org>
Reviewed-by: Maya Erez <merez@codeaurora.org>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'include/linux/mmc/dw_mmc.h')
0 files changed, 0 insertions, 0 deletions
