[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1598517445.10649.20.camel@mtkswgap22>
Date: Thu, 27 Aug 2020 16:37:25 +0800
From: Stanley Chu <stanley.chu@...iatek.com>
To: Can Guo <cang@...eaurora.org>
CC: <asutoshd@...eaurora.org>, <nguyenb@...eaurora.org>,
<hongwus@...eaurora.org>, <rnayak@...eaurora.org>,
<linux-scsi@...r.kernel.org>, <kernel-team@...roid.com>,
<saravanak@...gle.com>, <salyzyn@...gle.com>,
"Alim Akhtar" <alim.akhtar@...sung.com>,
Avri Altman <avri.altman@....com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Bean Huo <beanhuo@...ron.com>,
"Bart Van Assche" <bvanassche@....org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 1/2] scsi: ufs: Abort tasks before clear them from
doorbell
On Mon, 2020-08-24 at 19:07 -0700, Can Guo wrote:
> To recovery non-fatal errors, no full reset is required, err_handler only
> clears those pending TRs/TMRs so that scsi layer can re-issue them. In
> current err_handler, TRs are directly cleared from UFS host's doorbell but
> not aborted from device side. However, according to the UFSHCI JEDEC spec,
> the host software shall use UTP Transfer Request List CLear Register to
> clear a task from UFS host's doorbell only when a UTP Transfer Request is
> expected to not be completed, e.g. when the host software receives a
> “FUNCTION COMPLETE” Task Management response which means a Transfer Request
> was aborted. To follow the UFSHCI JEDEC spec, in err_handler, aborts one TR
> before clearing it from doorbell.
>
> Signed-off-by: Can Guo <cang@...eaurora.org>
Acked-by: Stanley Chu <stanley.chu@...iatek.com>
Powered by blists - more mailing lists