On Fri, Sep 09, 2016 at 07:17:48PM +0100, Robin Murphy wrote: > Now that we've ratified SMMUv3's use of the generic binding, document it. > > CC: Rob Herring <robh+dt@xxxxxxxxxx> > CC: Mark Rutland <mark.rutland@xxxxxxx> > Signed-off-by: Robin Murphy <robin.murphy@xxxxxxx> > --- > Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt > index 7b94c88cf2ee..69a694f70bea 100644 > --- a/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt > +++ b/Documentation/devicetree/bindings/iommu/arm,smmu-v3.txt > @@ -27,6 +27,12 @@ the PCIe specification. > * "cmdq-sync" - CMD_SYNC complete > * "gerror" - Global Error activated > > +- #iommu-cells : See the generic IOMMU binding described in > + devicetree/bindings/iommu/iommu.txt That file has a weird "Notes:" section describing the application of "iommus" to a PCI host bridge. We should probably rip that out, because it seems to be going directly against the approach we've ended up taking. In fact, replacing that with a cross reference to devicetree/bindings/pci/pci-iommu.txt would make much more sense to me. > + for details. For SMMUv3, must be 1, with each cell > + describing a single stream ID. All possible stream > + ID which a device may emit must be described. IDs Will -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
