From: Bart Van Assche <bvanassche@acm.org>
To: Can Guo <quic_cang@quicinc.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 0/3] Reduce interrupt latency
Date: Mon, 30 Mar 2026 11:36:12 -0700 [thread overview]
Message-ID: <6e4ce34a-23e6-4dca-837a-b89feb504e41@acm.org> (raw)
In-Reply-To: <20260330183311.1941942-1-bvanassche@acm.org>
On 3/30/26 11:33 AM, Bart Van Assche wrote:
> On Android systems it is important to keep the time spent in interrupts short.
> This keeps the user interface responsive and prevents audio stuttering. Hence
> this patch series to reduce the time spent in the UFS interrupt handler. Please
> consider this patch series for the next merge window.
(replying to my own email)
Hi,
Can anyone help me to test this patch series on an MCQ Qualcomm system?
I do not have access to such a setup.
Thanks,
Bart.
next prev parent reply other threads:[~2026-03-30 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 18:33 [PATCH 0/3] Reduce interrupt latency Bart Van Assche
2026-03-30 18:33 ` [PATCH 1/3] ufs: core: Fix ufshcd_mcq_force_compl_one() Bart Van Assche
2026-03-31 9:41 ` Peter Wang (王信友)
2026-03-31 19:29 ` Bart Van Assche
2026-04-01 13:10 ` Peter Wang (王信友)
2026-04-01 15:51 ` Bart Van Assche
2026-04-02 7:19 ` Peter Wang (王信友)
2026-03-30 18:33 ` [PATCH 2/3] ufs: core: Introduce ufshcd_mcq_poll_cqe_lock_n() Bart Van Assche
2026-03-31 9:43 ` Peter Wang (王信友)
2026-03-31 19:31 ` Bart Van Assche
2026-04-01 13:11 ` Peter Wang (王信友)
2026-04-01 15:51 ` Bart Van Assche
2026-04-02 7:20 ` Peter Wang (王信友)
2026-03-30 18:33 ` [PATCH 3/3] ufs: qcom: Reduce interrupt latency Bart Van Assche
2026-03-31 7:09 ` Manivannan Sadhasivam
2026-03-31 19:44 ` Bart Van Assche
2026-04-04 3:11 ` Manivannan Sadhasivam
2026-04-06 16:02 ` Bart Van Assche
2026-03-30 18:36 ` Bart Van Assche [this message]
2026-03-31 2:01 ` [PATCH 0/3] " Can Guo
2026-04-07 8:20 ` Xiaosen
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=6e4ce34a-23e6-4dca-837a-b89feb504e41@acm.org \
--to=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@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