| Message ID | a4f3d4e2feef008d1236ebc3f5f0c46360f20c60.1645119806.git.robin.murphy@arm.com |
|---|---|
| State | Accepted |
| Commit | 10d7e312497f13419e1f99d903961c7ec0739da3 |
| Headers | show |
| Series | [v2] dt-bindings: reserved-memory: Add restricted-dma-pool constraints | expand |
On Thu, 17 Feb 2022 17:47:14 +0000, Robin Murphy wrote: > The "restricted-dma-pool" definition prohibits combination with either > of the "no-map" and "reusable" properties, but this is only stated in > the description text. Add those constraints to the schema so we can > properly validate them. > > Signed-off-by: Robin Murphy <robin.murphy@arm.com> > --- > > v2: Simplify with "properties:...:false" vs. "not:required:..." > > .../bindings/reserved-memory/shared-dma-pool.yaml | 10 ++++++++++ > 1 file changed, 10 insertions(+) > Applied, thanks!
diff --git a/Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml b/Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml index a4bf757d6881..618105f079be 100644 --- a/Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml +++ b/Documentation/devicetree/bindings/reserved-memory/shared-dma-pool.yaml @@ -56,6 +56,16 @@ properties: If this property is present, then Linux will use the region for the default pool of the consistent DMA allocator. +if: + properties: + compatible: + contains: + const: restricted-dma-pool +then: + properties: + no-map: false + reusable: false + unevaluatedProperties: false examples:
The "restricted-dma-pool" definition prohibits combination with either of the "no-map" and "reusable" properties, but this is only stated in the description text. Add those constraints to the schema so we can properly validate them. Signed-off-by: Robin Murphy <robin.murphy@arm.com> --- v2: Simplify with "properties:...:false" vs. "not:required:..." .../bindings/reserved-memory/shared-dma-pool.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+)