From: "Martin K. Petersen (Oracle)" <mkp@kernel.org>
To: sangram kumar yerra <sangram.k.y@intel.com>
Cc: Martin K Petersen <martin.petersen@oracle.com>,
James EJ Bottomley <James.Bottomley@HansenPartnership.com>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
adrian.hunter@intel.com
Subject: Re: [PATCH 0/2] scsi: ufs: ufs-pci: Intel UFS 4.0 HS-Gear5 and MCQ support
Date: Fri, 28 Aug 2026 22:13:14 -0400 [thread overview]
Message-ID: <yq1v78tisi9.fsf@mail.kernel.org> (raw)
In-Reply-To: <20260818112830.453402-1-sangram.k.y@intel.com> (sangram kumar yerra's message of "Tue, 18 Aug 2026 16:58:28 +0530")
sangram,
> 096cd6b7adf2 ("scsi: ufs: ufs-pci: Add support for Intel Nova Lake")
> added the PCI ID for Intel's UFS 4.0 controller (8086:D335), reusing
> the existing Meteor Lake variant operations table. That table is
> missing two things this controller needs to work correctly at UFS 4.0
> capability: a PA_INITIAL_ADAPT sequence for reliable HS-Gear5 link
> training, and the MCQ resource/runtime-config hooks required for
> ufshcd_alloc_mcq() to succeed. Without either, the controller still
> works, but silently falls back to Gear5 link instability or legacy
> single-doorbell mode respectively.
Applied to 7.3/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-08-29 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 11:28 [PATCH 0/2] scsi: ufs: ufs-pci: Intel UFS 4.0 HS-Gear5 and MCQ support sangram kumar yerra
2026-08-18 11:28 ` [PATCH 1/2] scsi: ufs: ufs-pci: Add support for Intel UFS 4.0 HS-Gear5 sangram kumar yerra
2026-08-18 11:28 ` [PATCH 2/2] scsi: ufs: ufs-pci: Add MCQ support for Intel UFS 4.0 controllers sangram kumar yerra
2026-08-18 15:39 ` [PATCH 0/2] scsi: ufs: ufs-pci: Intel UFS 4.0 HS-Gear5 and MCQ support Bart Van Assche
2026-08-29 2:13 ` Martin K. Petersen (Oracle) [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=yq1v78tisi9.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sangram.k.y@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.