Lines Matching full:iommu

2 relationship between PCI(e) devices and IOMMU(s).
17 Requester ID. While a given PCI device can only master through one IOMMU, a
18 root complex may split masters across a set of IOMMUs (e.g. with one IOMMU per
22 and a mechanism is required to map from a PCI device to its IOMMU and sideband
25 For generic IOMMU bindings, see
26 Documentation/devicetree/bindings/iommu/iommu.txt.
35 - iommu-map: Maps a Requester ID to an IOMMU and associated IOMMU specifier
39   (rid-base,iommu,iommu-base,length).
42   the listed IOMMU, with the IOMMU specifier (r - rid-base + iommu-base).
44 - iommu-map-mask: A mask to be applied to each Requester ID prior to being
45   mapped to an IOMMU specifier per the iommu-map property.
55 	iommu: iommu@a {
57 		compatible = "vendor,some-iommu";
58 		#iommu-cells = <1>;
67 		 * The sideband data provided to the IOMMU is the RID,
70 		iommu-map = <0x0 &iommu 0x0 0x10000>;
82 	iommu: iommu@a {
84 		compatible = "vendor,some-iommu";
85 		#iommu-cells = <1>;
94 		 * The sideband data provided to the IOMMU is the RID with the
97 		iommu-map = <0x0 &iommu 0x0 0x10000>;
98 		iommu-map-mask = <0xfff8>;
110 	iommu: iommu@a {
112 		compatible = "vendor,some-iommu";
113 		#iommu-cells = <1>;
122 		 * The sideband data provided to the IOMMU is the RID,
125 		iommu-map = <0x0000 &iommu 0x8000 0x8000>,
126 			    <0x8000 &iommu 0x0000 0x8000>;
138 	iommu_a: iommu@a {
140 		compatible = "vendor,some-iommu";
141 		#iommu-cells = <1>;
144 	iommu_b: iommu@b {
146 		compatible = "vendor,some-iommu";
147 		#iommu-cells = <1>;
150 	iommu_c: iommu@c {
152 		compatible = "vendor,some-iommu";
153 		#iommu-cells = <1>;
162 		 * Devices with bus number 0-127 are mastered via IOMMU
165 		 * IOMMU b, with sideband data being RID[14:0].
166 		 * No devices master via IOMMU c.
168 		iommu-map = <0x0000 &iommu_a 0x0000 0x8000>,