From: Rob Herring <robh@kernel.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
jayachandran.nair@cavium.com, lorenzo.pieralisi@arm.com,
tnowicki@caviumnetworks.com, kvm@vger.kernel.org,
virtio-dev@lists.oasis-open.org, joro@8bytes.org, mst@redhat.com,
will.deacon@arm.com, virtualization@lists.linux-foundation.org,
marc.zyngier@arm.com, iommu@lists.linux-foundation.org,
eric.auger@redhat.com, robin.murphy@arm.com,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v2 1/5] dt-bindings: virtio: Specify #iommu-cells value for a virtio-iommu
Date: Mon, 25 Jun 2018 13:27:53 -0600 [thread overview]
Message-ID: <20180625192753.GA22351@rob-hp-laptop> (raw)
In-Reply-To: <20180621190655.56391-2-jean-philippe.brucker@arm.com>
On Thu, Jun 21, 2018 at 08:06:51PM +0100, Jean-Philippe Brucker wrote:
> A virtio-mmio node may represent a virtio-iommu device. This is discovered
> by the virtio driver at probe time, but the DMA topology isn't
> discoverable and must be described by firmware. For DT the standard IOMMU
> description is used, as specified in bindings/iommu/iommu.txt and
> bindings/pci/pci-iommu.txt. Like many other IOMMUs, virtio-iommu
> distinguishes masters by their endpoint IDs, which requires one IOMMU cell
> in the "iommus" property.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> ---
> Documentation/devicetree/bindings/virtio/mmio.txt | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/virtio/mmio.txt b/Documentation/devicetree/bindings/virtio/mmio.txt
> index 5069c1b8e193..337da0e3a87f 100644
> --- a/Documentation/devicetree/bindings/virtio/mmio.txt
> +++ b/Documentation/devicetree/bindings/virtio/mmio.txt
> @@ -8,6 +8,14 @@ Required properties:
> - reg: control registers base address and size including configuration space
> - interrupts: interrupt generated by the device
>
> +Required properties for virtio-iommu:
> +
> +- #iommu-cells: When the node describes a virtio-iommu device, it is
> + linked to DMA masters using the "iommus" property as
> + described in devicetree/bindings/iommu/iommu.txt. For
> + virtio-iommu #iommu-cells must be 1, each cell describing
> + a single endpoint ID.
The iommus property should also be documented for the client side.
Rob
next prev parent reply other threads:[~2018-06-25 19:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 19:06 [PATCH v2 0/5] Add virtio-iommu driver Jean-Philippe Brucker
2018-06-21 19:06 ` [PATCH v2 1/5] dt-bindings: virtio: Specify #iommu-cells value for a virtio-iommu Jean-Philippe Brucker
2018-06-25 19:27 ` Rob Herring [this message]
2018-06-26 17:58 ` Jean-Philippe Brucker
[not found] ` <89d31865-ee35-ef8c-f7b3-f3acf2bbd30e-5wv7dgnIgG8@public.gmane.org>
2018-06-27 17:46 ` Rob Herring
[not found] ` <CAL_JsqLdahF+2VsH9h658z9guO0XmqHM75QLaHApZLNP8twUNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-07-04 11:45 ` Robin Murphy
2018-06-21 19:06 ` [PATCH v2 2/5] iommu: Add virtio-iommu driver Jean-Philippe Brucker
[not found] ` <20180621190655.56391-3-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
2018-06-22 0:51 ` Michael S. Tsirkin
[not found] ` <20180622033720-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-06-25 17:52 ` Jean-Philippe Brucker
2018-06-21 19:06 ` [PATCH v2 3/5] iommu/virtio: Add probe request Jean-Philippe Brucker
[not found] ` <20180621190655.56391-4-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
2018-06-22 0:55 ` Michael S. Tsirkin
2018-06-25 17:52 ` Jean-Philippe Brucker
2018-06-26 17:59 ` Jean-Philippe Brucker
2018-06-21 19:06 ` [PATCH v2 4/5] iommu/virtio: Add event queue Jean-Philippe Brucker
2018-06-21 19:06 ` [PATCH v2 5/5] vfio: Allow type-1 IOMMU instantiation for ARM Jean-Philippe Brucker
[not found] ` <20180621190655.56391-1-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org>
2018-06-26 18:07 ` [PATCH v2 0/5] Add virtio-iommu driver Michael S. Tsirkin
2018-06-27 18:04 ` Jean-Philippe Brucker
2018-06-27 19:59 ` Michael S. Tsirkin
2018-06-28 9:40 ` Peter Maydell
2018-07-04 11:25 ` Jean-Philippe Brucker
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=20180625192753.GA22351@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jayachandran.nair@cavium.com \
--cc=jean-philippe.brucker@arm.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mst@redhat.com \
--cc=robin.murphy@arm.com \
--cc=tnowicki@caviumnetworks.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.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