[RFC PATCH 1/6] dt-bindings: document stall and PASID properties for IOMMU masters
Yisheng Xie
xieyisheng1 at huawei.com
Thu Aug 31 01:20:37 PDT 2017
From: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
Document the bindings for stall and PASID capable platform devices.
Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>
---
Documentation/devicetree/bindings/iommu/iommu.txt | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/iommu/iommu.txt b/Documentation/devicetree/bindings/iommu/iommu.txt
index 5a8b462..7355d7f 100644
--- a/Documentation/devicetree/bindings/iommu/iommu.txt
+++ b/Documentation/devicetree/bindings/iommu/iommu.txt
@@ -86,6 +86,19 @@ have a means to turn off translation. But it is invalid in such cases to
disable the IOMMU's device tree node in the first place because it would
prevent any driver from properly setting up the translations.
+Optional properties:
+--------------------
+- dma-can-stall: When present, the master can wait for a DMA transaction
+ to be handled by the IOMMU and can recover from a fault. For example, if
+ the page accessed by the DMA transaction isn't mapped, some IOMMUs are
+ able to stall the transaction and let the OS populate the page tables.
+ The IOMMU then performs the transaction if the fault was successfully
+ handled, or aborts the transaction otherwise.
+
+- pasid-bits: Some masters support multiple address spaces for DMA. By
+ tagging DMA transactions with an address space identifier. By default,
+ this is 0, which means that the device only has one address space.
+
Notes:
======
--
1.7.12.4
More information about the linux-arm-kernel
mailing list