From: Frank Chang <frank.chang@sifive.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liwei1518@gmail.com, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, ajones@ventanamicro.com, kraxel@redhat.com
Subject: Re: [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU
Date: Tue, 7 May 2024 23:37:05 +0800 [thread overview]
Message-ID: <CANzO1D0g=AoPkyFS_5d5mJwmwDX8hpaj0fjeFy9xt4xi70fh1A@mail.gmail.com> (raw)
In-Reply-To: <20240503124244.8804-1-dbarboza@ventanamicro.com>
Hi Daniel,
Daniel Henrique Barboza <dbarboza@ventanamicro.com> 於 2024年5月3日 週五 下午8:43寫道：
>
> Hi,
>
> In this RFC I want to check with Gerd and others if it's ok to add a PCI
> id for the RISC-V IOMMU device. It's currently under review in [1]. The
Is the link [1] missing?
Regards,
Frank Chang
> idea is to fold this patch into the RISC-V IOMMU series if we're all ok
> with this change.
>
> Gerd, we picked the ID right after the PCI UFS device. Let me know if
> you want another ID instead.
>
>
> Daniel Henrique Barboza (1):
> pci-ids.rst: add Red Hat pci-id for generic IOMMU device
>
> docs/specs/pci-ids.rst | 2 ++
> include/hw/pci/pci.h | 1 +
> 2 files changed, 3 insertions(+)
>
> --
> 2.44.0
>
>
next prev parent reply other threads:[~2024-05-07 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 12:42 [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU Daniel Henrique Barboza
2024-05-03 12:42 ` [RFC PATCH 1/1] pci-ids.rst: add Red Hat pci-id for generic IOMMU device Daniel Henrique Barboza
2024-05-07 15:35 ` Frank Chang
2024-05-07 15:37 ` Frank Chang [this message]
2024-05-07 15:53 ` [RFC PATCH 0/1] pci: allocate a PCI ID for RISC-V IOMMU Gerd Hoffmann
2024-05-08 11:19 ` Daniel Henrique Barboza
2024-05-08 11:17 ` Daniel Henrique Barboza
2024-05-07 15:44 ` Peter Maydell
2024-05-08 12:41 ` Daniel Henrique Barboza
2024-05-10 10:47 ` Frank Chang
2024-05-20 17:40 ` Daniel Henrique Barboza
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='CANzO1D0g=AoPkyFS_5d5mJwmwDX8hpaj0fjeFy9xt4xi70fh1A@mail.gmail.com' \
--to=frank.chang@sifive.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=kraxel@redhat.com \
--cc=liwei1518@gmail.com \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).