All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajeshkumar Sambandham <Rajeshkumar.Sambandham@amd.com>
To: <James.Bottomley@HansenPartnership.com>,
	<martin.petersen@oracle.com>, <bvanassche@acm.org>,
	<adrian.hunter@intel.com>, <archana.patni@intel.com>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Rajeshkumar Sambandham <Rajeshkumar.Sambandham@amd.com>
Subject: [PATCH v2] scsi: ufs: ufs-pci: Add AMD device ID support
Date: Tue, 2 Jun 2026 15:29:31 +0530	[thread overview]
Message-ID: <20260602095931.2869516-1-Rajeshkumar.Sambandham@amd.com> (raw)

Add PCI device ID 0x1022:0x1B29 for AMD UFS controllers.

Signed-off-by: Rajeshkumar Sambandham <Rajeshkumar.Sambandham@amd.com>
---

v2:
 - Use PCI_VDEVICE to match other entries in the ufshcd_pci_tbl array.

 drivers/ufs/host/ufshcd-pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/ufs/host/ufshcd-pci.c b/drivers/ufs/host/ufshcd-pci.c
index 13293e83064c..f2433879b0eb 100644
--- a/drivers/ufs/host/ufshcd-pci.c
+++ b/drivers/ufs/host/ufshcd-pci.c
@@ -694,6 +694,7 @@ static const struct pci_device_id ufshcd_pci_tbl[] = {
 	{ PCI_VDEVICE(INTEL, 0xE447), .driver_data = (kernel_ulong_t)&ufs_intel_mtl_hba_vops },
 	{ PCI_VDEVICE(INTEL, 0x4D47), .driver_data = (kernel_ulong_t)&ufs_intel_mtl_hba_vops },
 	{ PCI_VDEVICE(INTEL, 0xD335), .driver_data = (kernel_ulong_t)&ufs_intel_mtl_hba_vops },
+	{ PCI_VDEVICE(AMD, 0x1B29), .driver_data = 0 },
 	{ }	/* terminate list */
 };
 
-- 
2.34.1


             reply	other threads:[~2026-06-02 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  9:59 Rajeshkumar Sambandham [this message]
2026-06-02 10:58 ` [PATCH v2] scsi: ufs: ufs-pci: Add AMD device ID support Adrian Hunter
2026-06-08 21:45 ` Martin K. Petersen
2026-06-16  2:26 ` Martin K. Petersen

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=20260602095931.2869516-1-Rajeshkumar.Sambandham@amd.com \
    --to=rajeshkumar.sambandham@amd.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=adrian.hunter@intel.com \
    --cc=archana.patni@intel.com \
    --cc=bvanassche@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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.