From: "Peter Wang (王信友)" <peter.wang@mediatek.com>
To: "huobean@gmail.com" <huobean@gmail.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"quic_nitirawa@quicinc.com" <quic_nitirawa@quicinc.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"andre.draszik@linaro.org" <andre.draszik@linaro.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"mani@kernel.org" <mani@kernel.org>,
"James.Bottomley@HansenPartnership.com"
<James.Bottomley@HansenPartnership.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"quic_pkambar@quicinc.com" <quic_pkambar@quicinc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1] ufs: core: Fix interrupt handling for MCQ Mode in ufshcd_intr
Date: Wed, 30 Jul 2025 06:41:28 +0000 [thread overview]
Message-ID: <b005d94288a4c4d29a9361b043354bbc8d85e0e8.camel@mediatek.com> (raw)
In-Reply-To: <0fd86741-f72e-4a52-9d2c-2388c4a26115@acm.org>
On Tue, 2025-07-29 at 09:24 -0700, Bart Van Assche wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> On 7/29/25 7:37 AM, Nitin Rawat wrote:
> > I reviewed your patch and test it locally—it resolves the issue.
>
> Thanks!
>
> > The patch looks good. Since this path handles only UIC, TM, and
> > error
> > conditions with no IO for MCQ, we still check for outstanding_reqs
> > and
> > UTP_TRANSFER_REQ_COMPL for the error case within
> > ufshcd_threaded_intr in
> > the patch. In my opinion, we can skip these additional checks.
>
> We can only skip the outstanding_reqs check if MCQ is enabled. André
> Draszik is working on a patch that will cause ufshcd_intr() to be
> called
> again for legacy mode so I prefer to keep the outstanding_reqs check.
>
> Bart.
Hi Bart,
The threaded ISR was separated out specifically to address
the issues of the traditional ISR, because a traditional ISR
must be very fast and short, as it blocks other interrupts.
But your patch letting the traditional ISR call the threaded
ISR, doesn’t this bring back the problem where the threaded
ISR might block other interrupts?
So, I prefer this patch clear the interrupt status register
(IS) directly.
Thanks.
Peter
next prev parent reply other threads:[~2025-07-30 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 22:57 Nitin Rawat
2025-07-28 23:41 ` Bart Van Assche
2025-07-29 14:37 ` Nitin Rawat
2025-07-29 16:24 ` Bart Van Assche
2025-07-30 6:41 ` Peter Wang (王信友) [this message]
2025-07-30 16:04 ` Bart Van Assche
2025-07-31 9:22 ` Peter Wang (王信友)
2025-07-31 8:27 ` neil.armstrong
2025-08-06 1:54 ` Martin K. Petersen
2025-07-31 16:52 ` Bart Van Assche
2025-08-01 7:31 ` Peter Wang (王信友)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b005d94288a4c4d29a9361b043354bbc8d85e0e8.camel@mediatek.com \
--to=peter.wang@mediatek.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alim.akhtar@samsung.com \
--cc=andre.draszik@linaro.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=huobean@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_nitirawa@quicinc.com \
--cc=quic_pkambar@quicinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®