[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a1a0c85-e2f1-4a7c-ad0d-86ad8a84e624@acm.org>
Date: Mon, 21 Oct 2024 13:26:58 -0700
From: Bart Van Assche <bvanassche@....org>
To: Avri Altman <avri.altman@....com>,
"Martin K . Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] scsi: ufs: core: Use reg_lock to protect UTRLCLR
On 10/21/24 5:03 AM, Avri Altman wrote:
> @@ -3100,9 +3100,9 @@ static int ufshcd_clear_cmd(struct ufs_hba *hba, u32 task_tag)
> mask = 1U << task_tag;
>
> /* clear outstanding transaction before retry */
> - spin_lock_irqsave(hba->host->host_lock, flags);
> + spin_lock_irqsave(&hba->reg_lock, flags);
> ufshcd_utrl_clear(hba, mask);
> - spin_unlock_irqrestore(hba->host->host_lock, flags);
> + spin_unlock_irqrestore(&hba->reg_lock, flags);
>
> /*
> * wait for h/w to clear corresponding bit in door-bell.
Hi Avri,
A similar comment as for the previous patch applies to this patch:
ufshcd_utrl_clear() performs a single MMIO write so I don't think that
calls of this function have to be serialized.
Thanks,
Bart.
Powered by blists - more mailing lists