[PATCH 1/3] dt-bindings: arm: mediatek: mmsys: Allow single vdo/mmsys endpoint
From: AngeloGioacchino Del Regno
Date: Thu Jan 08 2026 - 09:42:09 EST
The hardware supports using just a single output while leaving all
of the others unconfigured (disabled), but the binding did not
really allow specifying a single endpoint@0, because in this case
one must either:
- Call the subnode `endpoint` and not declare any address and/or
size cells; or
- Call the subnode `endpoint@0` and have at least one more other
endpoint(@1 or @2), and declare address/size cells.
Allow specifying a single `endpoint` subnode, without the `@0`
implicit suffix to suppress warnings happening on this kind of
valid usecase.
Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@xxxxxxxxxxxxx>
---
.../bindings/arm/mediatek/mediatek,mmsys.yaml | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
index 3f4262e93c78..e3ef7540c24f 100644
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
+++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
@@ -100,11 +100,12 @@ properties:
the first component of one display pipeline, for example one of
the available OVL or RDMA blocks.
Some MediaTek SoCs support multiple display outputs per MMSYS.
- properties:
- endpoint@0:
+ patternProperties:
+ "^endpoint(@0)?$":
$ref: /schemas/graph.yaml#/properties/endpoint
description: Output to the primary display pipeline
+ properties:
endpoint@1:
$ref: /schemas/graph.yaml#/properties/endpoint
description: Output to the secondary display pipeline
@@ -114,8 +115,11 @@ properties:
description: Output to the tertiary display pipeline
anyOf:
- - required:
- - endpoint@0
+ - oneOf:
+ - required:
+ - endpoint
+ - required:
+ - endpoint@0
- required:
- endpoint@1
- required:
--
2.52.0