summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorAsutosh Das <asutoshd@codeaurora.org>2015-05-29 15:39:37 +0530
committerSubhash Jadavani <subhashj@codeaurora.org>2016-05-31 15:27:08 -0700
commitf052410b0bd6f04effc8d2c9c9323dda55d9c7da (patch)
treecdea594d02008ec07e287c7d7e484c8ee3b33535 /include/linux
parented1bdbadff70bc32ae279b9fa967094c2d784b56 (diff)
mmc: cmdq: trigger get queue status after dcmd
CMDQ spec defines periodic SEND_STATUS mechanism to poll on READY tasks in the device. When DAT lines are in IDLE the counter counts from its reset value to '0' and then triggers SEND_STATUS command. When CMD13 is completed and also the syncing of the device status to HCLK domain is done there is a 1 cycle pulse to reload the counter with timer reset value so that the counting can start over. In rare cases, when the 'done' pulse for reloading the counter happens in parallel to a BUSY state of direct command - the IDLE counter is not reloaded and can't trigger another CMD13. If this scenario happens when there are pending tasks which are not 'READY' yet - it can lead to a deadlock, since there is no other mechainsm to send CMD13, and CQE will never get READY on the pending tasks. Hence, trigger a send status command after DCMD is completed as a work-around to the above issue. Change-Id: I4e8530e72c8bf581ffaeed7d35d8b8c61d282ffa Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions