summaryrefslogtreecommitdiffstats
path: root/drivers/thermal
diff options
context:
space:
mode:
authorSujit Reddy Thumma2014-09-25 14:32:26 +0200
committerChristoph Hellwig2014-10-01 13:11:21 +0200
commit1d337ec2f35e69a046dab0cc77e64e68d1cdcd8b (patch)
tree88d672dad6fa282cd02e242d606a3340e42f209f /drivers/thermal
parentufs: refactor query descriptor API support (diff)
downloadkernel-qcow2-linux-1d337ec2f35e69a046dab0cc77e64e68d1cdcd8b.tar.gz
kernel-qcow2-linux-1d337ec2f35e69a046dab0cc77e64e68d1cdcd8b.tar.xz
kernel-qcow2-linux-1d337ec2f35e69a046dab0cc77e64e68d1cdcd8b.zip
ufs: improve init sequence
In ->hce_enable_notify() callback the vendor specific initialization may carry out additional DME configuration using UIC commands and hence the UIC command completion interrupt enable bit should be set before the post reset notification. Add retries if the link-startup fails. This is required since due to hardware timing issues, the Uni-Pro link-startup might fail. The UFS HCI recovery procedure contradicts the Uni-Pro sequence. The UFS HCI specifies to resend DME_LINKSTARTUP command after IS.ULLS (link-lost interrupt) is received. The Uni-Pro specifies that if link-startup fails the link is in "down" state. The link-lost is indicated to the DME user only when the link is up. Hence, the UFS HCI recovery procedure of waiting for IS.ULLS and retrying link-startup may not work properly. At the end, if detection fails, power off (disable clocks, regulators, phy) if the UFS device detection fails. This saves power while UFS device is not embedded into the system. Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org> Signed-off-by: Dolev Raviv <draviv@codeaurora.org> Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/thermal')
0 files changed, 0 insertions, 0 deletions