.../bindings/display/mediatek/mediatek,ovl-2l.yaml | 5 ++--- .../devicetree/bindings/display/mediatek/mediatek,ovl.yaml | 5 ++--- .../devicetree/bindings/display/mediatek/mediatek,rdma.yaml | 4 +--- .../devicetree/bindings/display/mediatek/mediatek,wdma.yaml | 4 +--- 4 files changed, 6 insertions(+), 12 deletions(-)
Lists should have fixed constraints, because binding must be specific in
respect to hardware. Add missing constraints to number of iommus in
Mediatek media devices.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
.../bindings/display/mediatek/mediatek,ovl-2l.yaml | 5 ++---
.../devicetree/bindings/display/mediatek/mediatek,ovl.yaml | 5 ++---
.../devicetree/bindings/display/mediatek/mediatek,rdma.yaml | 4 +---
.../devicetree/bindings/display/mediatek/mediatek,wdma.yaml | 4 +---
4 files changed, 6 insertions(+), 12 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
index bacdfe7d08a6..ac0d924a451b 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
@@ -45,9 +45,8 @@ properties:
- description: OVL-2L Clock
iommus:
- description:
- This property should point to the respective IOMMU block with master port as argument,
- see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
+ minItems: 1
+ maxItems: 2
mediatek,gce-client-reg:
description: The register of client driver can be configured by gce with
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl.yaml
index 4f110635afb6..c0fd0a91c4d8 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl.yaml
@@ -65,9 +65,8 @@ properties:
- description: OVL Clock
iommus:
- description:
- This property should point to the respective IOMMU block with master port as argument,
- see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
+ minItems: 1
+ maxItems: 2
mediatek,gce-client-reg:
description: The register of client driver can be configured by gce with
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,rdma.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,rdma.yaml
index 878f676b581f..7e5234def39a 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,rdma.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,rdma.yaml
@@ -64,9 +64,7 @@ properties:
- description: RDMA Clock
iommus:
- description:
- This property should point to the respective IOMMU block with master port as argument,
- see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
+ maxItems: 1
mediatek,rdma-fifo-size:
description:
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.yaml
index a3a2b71a4523..276868c0fde7 100644
--- a/Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.yaml
+++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,wdma.yaml
@@ -43,9 +43,7 @@ properties:
- description: WDMA Clock
iommus:
- description:
- This property should point to the respective IOMMU block with master port as argument,
- see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details.
+ maxItems: 1
mediatek,gce-client-reg:
description: The register of client driver can be configured by gce with
--
2.45.2
On Sun, May 25, 2025 at 07:16:40AM +0200, Krzysztof Kozlowski wrote: > Lists should have fixed constraints, because binding must be specific in > respect to hardware. Add missing constraints to number of iommus in > Mediatek media devices. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Acked-by: Conor Dooley <conor.dooley@microchip.com>
On Sun, 25 May 2025 at 06:16, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote: > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml > @@ -45,9 +45,8 @@ properties: > - description: OVL-2L Clock > > iommus: > - description: > - This property should point to the respective IOMMU block with master port as argument, > - see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details. > + minItems: 1 > + maxItems: 2 The comment removals are not documented in the commit message, and it's not clear why removing information and references would be a good thing. Please see https://www.kernel.org/doc/html/latest/process/submitting-patches.html for information on how to submit good-quality patches that can be better reviwed by maintainers.
On 25/05/2025 12:48, Daniel Stone wrote: > On Sun, 25 May 2025 at 06:16, Krzysztof Kozlowski > <krzysztof.kozlowski@linaro.org> wrote: >> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml >> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml >> @@ -45,9 +45,8 @@ properties: >> - description: OVL-2L Clock >> >> iommus: >> - description: >> - This property should point to the respective IOMMU block with master port as argument, >> - see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details. >> + minItems: 1 >> + maxItems: 2 > > The comment removals are not documented in the commit message, and > it's not clear why removing information and references would be a good > thing. It's obvious, isn't? The consumer shall not define which provider has to use or how many cells provider has. Best regards, Krzysztof
Hi, On Sun, 25 May 2025 at 11:51, Krzysztof Kozlowski <krzk@kernel.org> wrote: > On 25/05/2025 12:48, Daniel Stone wrote: > > On Sun, 25 May 2025 at 06:16, Krzysztof Kozlowski > > <krzysztof.kozlowski@linaro.org> wrote: > >> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml > >> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml > >> @@ -45,9 +45,8 @@ properties: > >> - description: OVL-2L Clock > >> > >> iommus: > >> - description: > >> - This property should point to the respective IOMMU block with master port as argument, > >> - see Documentation/devicetree/bindings/iommu/mediatek,iommu.yaml for details. > >> + minItems: 1 > >> + maxItems: 2 > > > > The comment removals are not documented in the commit message, and > > it's not clear why removing information and references would be a good > > thing. > It's obvious, isn't? The consumer shall not define which provider has to > use or how many cells provider has. If you feel the change is good, then document it in the commit message, and ideally also use separate commits rather than throwing in unrelated changes into a commit which does not explain anything. Again, the kernel documentation explains how you can structure your commits in a better way. Cheers, Daniel
© 2016 - 2025 Red Hat, Inc.