Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Fang Hongjie(方洪杰)" <hongjiefang@asrmicro.com>,
	"avri.altman@wdc.com" <avri.altman@wdc.com>,
	"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
	"beanhuo@micron.com" <beanhuo@micron.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: ufs: core: Add a vop to handle vendor specific ops
Date: Mon, 23 Mar 2026 10:29:21 -0700	[thread overview]
Message-ID: <29da71fc-b371-4869-9635-3b8d9b88fcfc@acm.org> (raw)
In-Reply-To: <dc22d720deba4ce1b1c7aa229a685911@exch02.asrmicro.com>

On 3/20/26 8:34 PM, Fang Hongjie(方洪杰) wrote:
>> On 3/19/26 2:38 AM, Hongjie Fang wrote:
>>> add a vop to allow some vendors to do some additional ops
>>> for some interrupts if necessary.
>>
>> UFS patches should be sent to Martin K. Petersen and should be Cc-ed to
>> the linux-scsi mailing list. Additionally, a patch description should
>> not only explain what has been changed but also why a change is being
>> mode. "to do some additional ops for some interrupts if necessary" is
>> too vague.
> 
> Given that some UFS controllers have private or extended interrupt status
> registers, the purpose of this patch is to facilitate the handling of
> proprietary registers within the host driver during the interrupt handling.

The above makes it clear that this patch is intended for a UFS host
controller that does not comply to the JEDEC UFSHCI standard. The Linux
kernel is standards based and the upstream Linux kernel UFS
driver is for UFS host controllers that comply to the JEDEC UFSHCI
standard.

Thanks,

Bart.

      reply	other threads:[~2026-03-23 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260319093839.1854051-1-hongjiefang@asrmicro.com>
     [not found] ` <64cc22ec-4d43-45c0-b63f-0401776f79a7@acm.org>
2026-03-21  3:34   ` [PATCH] scsi: ufs: core: Add a vop to handle vendor specific ops Fang Hongjie(方洪杰)
2026-03-23 17:29     ` Bart Van Assche [this message]

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=29da71fc-b371-4869-9635-3b8d9b88fcfc@acm.org \
    --to=bvanassche@acm.org \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=hongjiefang@asrmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=peter.wang@mediatek.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