Some reg-mux users reference a controller without an argument cell
when there is only one mux control exposed by the provider.

Permit #mux-control-cells to be either 0 or 1 so the converted schema
matches both existing provider styles.

Assisted-by: LLM
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
 Documentation/devicetree/bindings/mux/reg-mux.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mux/reg-mux.yaml b/Documentation/devicetree/bindings/mux/reg-mux.yaml
index dc4be092fc2f..c8de11a90d90 100644
--- a/Documentation/devicetree/bindings/mux/reg-mux.yaml
+++ b/Documentation/devicetree/bindings/mux/reg-mux.yaml
@@ -22,7 +22,7 @@ properties:
   reg: true
 
   '#mux-control-cells':
-    const: 1
+    enum: [ 0, 1 ]
 
   mux-reg-masks:
     $ref: /schemas/types.yaml#/definitions/uint32-matrix
-- 
2.53.0

On Mon, 21 Sep 2026 18:26:16 -0500, Rob Herring (Arm) wrote:
> Some reg-mux users reference a controller without an argument cell
> when there is only one mux control exposed by the provider.
> 
> Permit #mux-control-cells to be either 0 or 1 so the converted schema
> matches both existing provider styles.
> 
> Assisted-by: LLM
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
>  Documentation/devicetree/bindings/mux/reg-mux.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied, thanks!

Acked-by: Conor Dooley <conor.dooley@microchip.com>