From: Jeuk Kim <jeuk20.kim@samsung.com>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"dlunev@chromium.org" <dlunev@chromium.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: ufs: ufs-pci: Add support for QEMU
Date: Tue, 01 Aug 2023 18:20:00 +0900 [thread overview]
Message-ID: <20230801092000epcms2p44c99d2c15bc6169e38693cb64cf946db@epcms2p4> (raw)
In-Reply-To: <48f05875-5255-70d2-0737-36fa95470037@intel.com>
On 1/08/23, Adrian Hunter wrote:
> On 1/08/23 10:37, Jeuk Kim wrote:
> > Add PCI ID to support QEMU ufs.
> >
> > The new qemu ufs device can be found at
> > https://lore.kernel.org/qemu-devel/20230727155239.GA979354@fedora
>
> Please say something about why a UFS device is being virtualized
> and what features it is expected to support.
Hi Adrian!
UFS device emulation feature has been newly added to QEMU recently.
Currently, QEMU UFS supports basic io and query request features,
and plans to add more features in the future.
With the addition of the QEMU ufs device emulation feature,
QEMU UFS decided to use the pci device id of 0x0013 in the REDHAT vendor id (0x1b36).
However, this information is not registered in the linux ufs driver,
so the current linux kernel does not recognize the QEMU UFS device.
Therefore, I want to register the QEMU ufs pci id through this patch.
Do I need to add the above content to the commit message?
Thanks,
Jeuk
> >
> > Signed-off-by: Jeuk Kim <jeuk20.kim@samsung.com>
> > ---
> > 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 cf3987773051..29d322931427 100644
> > --- a/drivers/ufs/host/ufshcd-pci.c
> > +++ b/drivers/ufs/host/ufshcd-pci.c
> > @@ -590,6 +590,7 @@ static const struct dev_pm_ops ufshcd_pci_pm_ops = {
> > };
> >
> > static const struct pci_device_id ufshcd_pci_tbl[] = {
> > + { PCI_VENDOR_ID_REDHAT, 0x0013, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
> > { PCI_VENDOR_ID_SAMSUNG, 0xC00C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 },
> > { PCI_VDEVICE(INTEL, 0x9DFA), (kernel_ulong_t)&ufs_intel_cnl_hba_vops },
> > { PCI_VDEVICE(INTEL, 0x4B41), (kernel_ulong_t)&ufs_intel_ehl_hba_vops },
next prev parent reply other threads:[~2023-08-01 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230801073750epcms2p121c08e452aaafdda301c5562f4ccff5b@epcms2p1>
2023-08-01 7:37 ` [PATCH] scsi: ufs: ufs-pci: Add support for QEMU Jeuk Kim
2023-08-01 8:25 ` Adrian Hunter
2023-08-01 9:20 ` Jeuk Kim [this message]
2023-08-01 11:12 ` Adrian Hunter
2023-08-01 18:20 ` Bart Van Assche
2023-08-02 1:20 ` Jeuk Kim
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=20230801092000epcms2p44c99d2c15bc6169e38693cb64cf946db@epcms2p4 \
--to=jeuk20.kim@samsung.com \
--cc=adrian.hunter@intel.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=dlunev@chromium.org \
--cc=jejb@linux.ibm.com \
--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