[PATCH net-next v11 01/13] dt-bindings: dpll: allow hex unit addresses on output pins

From: Ali Rouhi

Date: Wed Sep 30 2026 - 19:37:48 EST


From: Oleg Zadorozhnyi <Oleg.Zadorozhnyi@xxxxxxxxxxxxxxxxx>

The output-pins node matches its children against "^pin@[0-9]+$", while
input-pins takes "^pin@[0-9a-f]+$". A unit address is the reg value in
hex, so a device with more than ten outputs cannot describe the
eleventh: dtc wants pin@a for reg = <10>, and the output pattern refuses
it.

Use the input pattern for the outputs as well.

Fixes: 0afcee10dda1 ("dt-bindings: dpll: Add DPLL device and pin")
Signed-off-by: Oleg Zadorozhnyi <Oleg.Zadorozhnyi@xxxxxxxxxxxxxxxxx>
Assisted-by: Claude:claude-4-opus [chat]
Signed-off-by: Ali Rouhi <arouhi@xxxxxxxxxx>
---
Documentation/devicetree/bindings/dpll/dpll-device.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/dpll/dpll-device.yaml b/Documentation/devicetree/bindings/dpll/dpll-device.yaml
index fb8d7a9a3693..4b5184500b9f 100644
--- a/Documentation/devicetree/bindings/dpll/dpll-device.yaml
+++ b/Documentation/devicetree/bindings/dpll/dpll-device.yaml
@@ -65,7 +65,7 @@ properties:
const: 0

patternProperties:
- "^pin@[0-9]+$":
+ "^pin@[0-9a-f]+$":
$ref: /schemas/dpll/dpll-pin.yaml
unevaluatedProperties: false

--
2.43.0