summaryrefslogtreecommitdiffstats
path: root/block/blk-mq-cpumap.c
diff options
context:
space:
mode:
authorSubhash Jadavani <subhashj@codeaurora.org>2016-10-27 17:26:24 -0700
committerMartin K. Petersen <martin.petersen@oracle.com>2016-11-08 17:30:00 -0500
commit69d72ac8369a503926b5c494182dd209484de67e (patch)
treeaa1401245c4894a0745575be2a66c18ed476504f /block/blk-mq-cpumap.c
parentd6fcf81a0d97a9e9f5035973c3a4dc219c9488b0 (diff)
downloadlinux-69d72ac8369a503926b5c494182dd209484de67e.tar.bz2
scsi: ufs: change device rails hpm mode ramp up sequence
When we are resuming the UFS device rails in HPM mode, we are first powering on the VCC rail while VCCQ and VCCQ2 rails still being in LPM mode. Some UFS devices may take VCC on event as hint that host wants UFS device to be resumed and may start drawing more power from the VCCQ/VCCQ2 rails (while they are still in LPM mode) causing voltage drop on these rails. This change fixes this issue by bringing VCCQ & VCCQ2 rails out of LPM before powering on VCC rail. Reviewed-by: Venkat Gopalakrishnan <venkatg@codeaurora.org> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'block/blk-mq-cpumap.c')
0 files changed, 0 insertions, 0 deletions