On 10/21/24 1:58 AM, Peter Wang (王信友) wrote:
As the DBR clear event occurs before !ufshcd_cmd_inflight, this could potentially cause an additional usleep_range wait. If an additional wait of 100~200 us is not a concern, then I think it should be fine.
Hi Peter, ufshcd_try_to_abort_task() is typically called if no completion will be received from the UFS device. I think that the potential additional loop iteration is acceptable since it is rare that a UFS device reports a completion while ufshcd_try_to_abort_task() is in progress and since this is an error path and not the hot path. Thanks, Bart.
