From: Adrian Hunter <adrian.hunter@intel.com>
To: Rajeshkumar Sambandham <Rajeshkumar.Sambandham@amd.com>,
<James.Bottomley@HansenPartnership.com>,
<martin.petersen@oracle.com>, <bvanassche@acm.org>,
<archana.patni@intel.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scsi: ufs: ufs-pci: Add AMD device ID support
Date: Tue, 2 Jun 2026 13:58:42 +0300 [thread overview]
Message-ID: <8d736c51-cdf3-4007-8f47-7c1f9b606cba@intel.com> (raw)
In-Reply-To: <20260602095931.2869516-1-Rajeshkumar.Sambandham@amd.com>
On 02/06/2026 12:59, Rajeshkumar Sambandham wrote:
> Add PCI device ID 0x1022:0x1B29 for AMD UFS controllers.
>
> Signed-off-by: Rajeshkumar Sambandham <Rajeshkumar.Sambandham@amd.com>
Reviewed-by: Adrian Hunter <adrian.hunter@intel.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 */
> };
>
next prev parent reply other threads:[~2026-06-02 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 9:59 Rajeshkumar Sambandham
2026-06-02 10:58 ` Adrian Hunter [this message]
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=8d736c51-cdf3-4007-8f47-7c1f9b606cba@intel.com \
--to=adrian.hunter@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Rajeshkumar.Sambandham@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome