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>
This commit is contained in:
parent
3d49f7426e
commit
782e2efb74
|
@ -36,8 +36,8 @@
|
|||
|
||||
/* NOP OUT retries waiting for NOP IN response */
|
||||
#define NOP_OUT_RETRIES 10
|
||||
/* Timeout after 30 msecs if NOP OUT hangs without response */
|
||||
#define NOP_OUT_TIMEOUT 30 /* msecs */
|
||||
/* Timeout after 50 msecs if NOP OUT hangs without response */
|
||||
#define NOP_OUT_TIMEOUT 50 /* msecs */
|
||||
|
||||
/* Query request retries */
|
||||
#define QUERY_REQ_RETRIES 3
|
||||
|
|
Loading…
Reference in New Issue