[EXT] [PATCH v1 1/3] scsi: ufs: fix empty check of error history
Bean Huo (beanhuo)
beanhuo at micron.com
Mon Jan 13 01:28:48 PST 2020
> Currently checking if an error history element is empty or not is by its "value". In
> most cases, value is error code.
> However this checking is not correct because some errors or events do not
> specify any values in error history so values remain as 0, and this will lead to
> incorrect empty checking.
Do you think this is a bug of UFS host controller? According to the UFS host Spec,
If there had error detected in each layer, at least bit31 in its error code register
Should be set to 1.
Why there was an error happening, but host didn't set this bit31?
More information about the linux-arm-kernel