summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorsubhashj@codeaurora.org <subhashj@codeaurora.org>2016-12-22 18:41:33 -0800
committerMartin K. Petersen <martin.petersen@oracle.com>2017-01-05 18:10:04 -0500
commitd2aebb9b269b3e094b2d2d03121c3863b683a25b (patch)
tree0f13cb671064e524d1d6709f87eae829c5724f9e /include
parent4e768e7645ec4ffa92ee163643777b261ae97142 (diff)
downloadlinux-d2aebb9b269b3e094b2d2d03121c3863b683a25b.tar.gz
linux-d2aebb9b269b3e094b2d2d03121c3863b683a25b.tar.bz2
linux-d2aebb9b269b3e094b2d2d03121c3863b683a25b.zip
scsi: ufs: fix setting init power mode
Immediately after successful UFS link startup, UFS link power mode would be in PWM-G1, 1-lane, SLOW-AUTO mode. But currently we are doing few of the DME local/peer attributes access before setting the "hba->pwr_info" to default power mode. If we are doing link startup as part of error recovery then old power mode might be set to FAST mode and doing DME peer access (after link startup but before updating "hba->pwr_info" to default power mode) unintentionally tries to switch from FAST to FAST_AUTO mode (if UFSHCD_QUIRK_DME_PEER_ACCESS_AUTO_MODE quirk is enabled). Above issue is fixed by setting the default power mode immediately after successful link startup. Reviewed-by: Sahitya Tummala <stummala@codeaurora.org> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions