bindings/virtio/pci-iommu.yaml

1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/virtio/pci-iommu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: virtio-iommu device using the virtio-pci transport
10   - Jean-Philippe Brucker <jean-philippe@linaro.org>
13   When virtio-iommu uses the PCI transport, its programming interface is
15   device tree statically describes the relation between IOMMU and DMA
16   masters. Therefore, the PCI root complex that hosts the virtio-iommu
17   contains a child node representing the IOMMU device explicitly.
19   DMA from the IOMMU device isn't managed by another IOMMU. Therefore the
20   virtio-iommu node doesn't have an "iommus" property, and is omitted from
21   the iommu-map property of the root complex.
26   # built-in identification methods, compatible is not actually required.
29       - items:
30           - const: virtio,pci-iommu
31           - const: pci1af4,1057
32       - items:
33           - const: pci1af4,1057
37       PCI address of the IOMMU. As defined in the PCI Bus Binding
38       reference, the reg property is a five-cell address encoded as (phys.hi
43   '#iommu-cells':
47   - compatible
48   - reg
49   - '#iommu-cells'
54   - |
56         #address-cells = <2>;
57         #size-cells = <2>;
61             #address-cells = <3>;
62             #size-cells = <2>;
67              * The IOMMU manages all functions in this PCI domain except
70             iommu-map = <0x0 &iommu0 0x0 0x8
73             /* The IOMMU programming interface uses slot 00:01.0 */
74             iommu0: iommu@1,0 {
77                 #iommu-cells = <1>;
83             #address-cells = <3>;
84             #size-cells = <2>;
89              * The IOMMU also manages all functions from this domain,
90              * with endpoint IDs 0x10000 - 0x1ffff
92             iommu-map = <0x0 &iommu0 0x10000 0x10000>;
96             /* The IOMMU manages this platform device with endpoint ID 0x20000 */