summaryrefslogtreecommitdiff
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorSubhash Jadavani <subhashj@codeaurora.org>2015-10-19 12:04:46 -0700
committerSubhash Jadavani <subhashj@codeaurora.org>2016-05-31 15:27:43 -0700
commit4463dc76685b8e2702501502b0c4a4f03ac82e95 (patch)
tree0682b7954f2ca346dc85a389c97c16aa626444d1 /scripts/objdiff
parent6aa3b33671feb9dbd6ae3af93c71f8cb631dba96 (diff)
mmc: card: kick command queue thread on completion of RPMB operation
During RPMB operation, command queue mode would be disabled and we don't exlicitly move back to command queue once the RPMB operation is completed. We expect the command queue thread to switch operating mode (or partition) to command queue before issuing the new transfers in command queue but command queue thread isn't getting scheduled if we don't wake it up explicitly or if some other new transfer get submitted to the queue. Fix this issue by explicitly waking up the command queue thread after the completion of RPMB operation. Change-Id: I68b2f7989d68b51b4810346458e1966d45aee5a2 Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions