mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Draszik" <andre.draszik@linaro.org>
To: Kui Sun <kui.sun@unisoc.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	 Avri Altman <avri.altman@sandisk.com>,
	Bart Van Assche <bvanassche@acm.org>,
	"James E . J . Bottomley"	
	<James.Bottomley@HansenPartnership.com>,
	"Martin K . Petersen"	 <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	 rain.zhang@unisoc.com, yuelin.tang@unisoc.com,
	wenchao.chen@unisoc.com,  cixi.geng@linux.dev
Subject: Re: [PATCH] scsi: ufs: Allows the driver to choose the interrupt handler type
Date: Fri, 10 Jul 2026 12:29:48 +0100	[thread overview]
Message-ID: <1727f508a0b094420b124a1f5c9d4b29ec2cae31.camel@linaro.org> (raw)
In-Reply-To: <20260710065948.467514-1-kui.sun@unisoc.com>

Hi,

On Fri, 2026-07-10 at 14:59 +0800, Kui Sun wrote:
> This capability allows the host controller driver to choose whether
> To register interrupts in a threaded manner or in a
> Standard (non-threaded) manner

I believe it should at the least default to the original behaviour to
avoid the regression on pre-existing platforms out of the box without
taking additional steps, and make the threaded handling an opt-in until
a better solution is found for platforms that benefit from it without
adversely affecting other platforms.

Alternatively, I suggest to drop the threaded handler altogether (making it a
full revert).

For context:

https://lore.kernel.org/all/4enen7mopxtx4ijl5qyrd2gnxvv3kygtlnhxpr64egckpvkja4@hjli25ndhxwc/#t
and
https://lore.kernel.org/all/a4003ac352f382fa4ff329acdfa561eb06e77289.camel@linaro.org/
and related.

Cheers,
Andre'

  reply	other threads:[~2026-07-10 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  6:59 Kui Sun
2026-07-10 11:29 ` André Draszik [this message]
2026-07-10 12:45   ` André Draszik
2026-07-10 13:40 ` Bart Van Assche

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=1727f508a0b094420b124a1f5c9d4b29ec2cae31.camel@linaro.org \
    --to=andre.draszik@linaro.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@sandisk.com \
    --cc=bvanassche@acm.org \
    --cc=cixi.geng@linux.dev \
    --cc=kui.sun@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=rain.zhang@unisoc.com \
    --cc=wenchao.chen@unisoc.com \
    --cc=yuelin.tang@unisoc.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®