summaryrefslogtreecommitdiff
path: root/drivers/target/target_core_user.c
diff options
context:
space:
mode:
authorDaejun Park <daejun7.park@samsung.com>2020-09-02 05:58:52 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2020-09-16 03:14:01 +0300
commit782e2efb749f617209363b1ec1dd5cfc41a427e9 (patch)
tree6bb0c7a662b68739881dee056fef358e0644ffbc /drivers/target/target_core_user.c
parent3d49f7426e6c4e9c41d0aa88f0a76616912a383e (diff)
downloadlinux-782e2efb749f617209363b1ec1dd5cfc41a427e9.tar.xz
scsi: ufs: Fix NOP OUT timeout value
Boot occasionally fails with some Samsung low-power UFS devices. The reason is that these devices have a little bit higher latency for NOP OUT responses. This causes boot to fail because the NOP OUT command is issued during initialization to check whether the device transport protocol is ready or not. Increase NOP_OUT_TIMEOUT value from 30 to 50ms. Link: https://lore.kernel.org/r/231786897.01599016081767.JavaMail.epsvc@epcpadp2 Acked-by: Avri Altman <avri.altman@wdc.com> Signed-off-by: Daejun Park <daejun7.park@samsung.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/target/target_core_user.c')
0 files changed, 0 insertions, 0 deletions