The driver uses the presence of iommu-ranges on a context bank node to identify it as dedicated for extended IOVA mapping. iommu-ranges lists the IOVA ranges the IOMMU allocator may use for that device; any range not listed is left unused.
Add iommu-ranges to the compute-cb subnode properties so the DT validator accepts it on context bank nodes. Relax #address-cells to enum: [1, 2] and #size-cells to enum: [0, 2] to allow platforms that require 64-bit values in iommu-ranges to pass binding validation. Signed-off-by: Vinayak Katoch <[email protected]> --- Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml index e945c8ba75e3..f4ca9a767255 100644 --- a/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml +++ b/Documentation/devicetree/bindings/misc/qcom,fastrpc.yaml @@ -73,10 +73,10 @@ properties: $ref: /schemas/types.yaml#/definitions/uint32-array "#address-cells": - const: 1 + enum: [1, 2] "#size-cells": - const: 0 + enum: [0, 2] patternProperties: "(compute-)?cb@[0-9]*$": @@ -98,6 +98,8 @@ patternProperties: minItems: 1 maxItems: 10 + iommu-ranges: true + qcom,nsessions: $ref: /schemas/types.yaml#/definitions/uint32 default: 1 -- 2.34.1
