[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <772624e4-c463-4661-f433-6d60a489f023@acm.org>
Date: Fri, 19 May 2023 15:59:25 -0700
From: Bart Van Assche <bvanassche@....org>
To: "Bao D. Nguyen" <quic_nguyenb@...cinc.com>,
quic_asutoshd@...cinc.com, quic_cang@...cinc.com, mani@...nel.org,
stanley.chu@...iatek.com, adrian.hunter@...el.com,
beanhuo@...ron.com, avri.altman@....com, martin.petersen@...cle.com
Cc: linux-scsi@...r.kernel.org, Alim Akhtar <alim.akhtar@...sung.com>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Alice Chao <alice.chao@...iatek.com>,
Arthur Simchaev <Arthur.Simchaev@....com>,
open list <linux-kernel@...r.kernel.org>,
"open list:UNIVERSAL FLASH STORAGE HOST CONTROLLER DRIVER..."
<linux-arm-msm@...r.kernel.org>
Subject: Re: [PATCH v5 6/7] ufs: mcq: Use ufshcd_mcq_poll_cqe_lock() in mcq
mode
On 5/11/23 23:28, Bao D. Nguyen wrote:
> In preparation for adding mcq error handler support, update the mcq
> code to use the ufshcd_mcq_poll_cqe_lock() in interrupt context
> instead of using ufshcd_mcq_poll_cqe_nolock(). This is to keep
> synchronization between mcq interrupt and error handler contexts
> because both need to access the mcq hardware in separate contexts.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists