Re: [PATCH] UFS: Make TM command timeout configurable from host side

[Bart Van Assche <bvanassche@acm.org>]

On 11/17/25 9:55 PM, Peter Wang (王信友) wrote:
> However, in extreme cases, it’s possible that after a 30-second
> timeout, the device just send a response, and at the same time,
> when the host receives the response, the IRQ is pending by system.
> (other irq is executing or spin_lock_irq, etc)

It is not clear to me how this could happen? If a response is not
received in time from the UFS device, an abort TMF is sent. If the
device does not respond to the abort TMF, the UFS device is reset
(ufshcd_device_reset() is called if ufshcd_abort_all() fails). This
prevents that a response can be received after the error handler has
finished, isn't it?

Thanks,

Bart.