From: Conor Dooley <conor@kernel.org>
To: linusw@kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [rfc 2/2] dt-bindings: pinctrl: pincfg-node: add restrictions on conflicting properties
Date: Tue, 3 Feb 2026 17:29:43 +0000 [thread overview]
Message-ID: <20260203-gleaming-perky-e12d6a5fe86f@spud> (raw)
In-Reply-To: <20260203-device-unwashed-ed24f8592d79@spud>
From: Conor Dooley <conor.dooley@microchip.com>
Many of the possible pincfg properties are not compatible with one
another, either because they represent mutually exclusive states for a
pin or because they provide the same information in different units.
Add some simple restrictions to prevent invalid configurations.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
.../bindings/pinctrl/pincfg-node.yaml | 105 ++++++++++++++++--
1 file changed, 98 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml b/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml
index d1bc389e0a6d..874f0781d2fc 100644
--- a/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/pincfg-node.yaml
@@ -162,12 +162,103 @@ properties:
this affects the expected delay in ps before latching a value to
an output pin.
-if:
- required:
- - skew-delay
-then:
- properties:
- skew-delay-input-ps: false
- skew-delay-output-ps: false
+allOf:
+ - if:
+ required:
+ - skew-delay
+ then:
+ properties:
+ skew-delay-input-ps: false
+ skew-delay-output-ps: false
+
+ - if:
+ required:
+ - input-disable
+ then:
+ properties:
+ input-enable: false
+
+ - if:
+ required:
+ - output-disable
+ then:
+ properties:
+ output-enable: false
+ output-impedance-ohms: false
+
+ - if:
+ required:
+ - output-low
+ then:
+ properties:
+ output-high: false
+
+ - if:
+ required:
+ - low-power-enable
+ then:
+ properties:
+ low-power-disable: false
+
+ - if:
+ required:
+ - input-schmitt-disable
+ then:
+ properties:
+ input-schmitt-enable: false
+ input-schmitt-microvolt: false
+
+ - if:
+ required:
+ - drive-strength
+ then:
+ properties:
+ drive-strength-microamp: false
+
+ - if:
+ anyOf:
+ - required:
+ - drive-open-source
+ - required:
+ - drive-open-drain
+ - required:
+ - drive-push-pull
+ then:
+ oneOf:
+ - required:
+ - drive-open-source
+ - required:
+ - drive-open-drain
+ - required:
+ - drive-push-pull
+
+ - if:
+ anyOf:
+ - required:
+ - bias-disable
+ - required:
+ - bias-high-impedance
+ - required:
+ - bias-bus-hold
+ - required:
+ - bias-pull-up
+ - required:
+ - bias-pull-down
+ - required:
+ - bias-pull-pin-default
+ then:
+ oneOf:
+ - required:
+ - bias-disable
+ - required:
+ - bias-high-impedance
+ - required:
+ - bias-bus-hold
+ - required:
+ - bias-pull-up
+ - required:
+ - bias-pull-down
+ - required:
+ - bias-pull-pin-default
additionalProperties: true
--
2.51.0
next prev parent reply other threads:[~2026-02-03 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:29 [rfc 0/2] pinctrl property checks Conor Dooley
2026-02-03 17:29 ` [rfc 1/2] pinctrl: pinconf-generic: perform basic checks on pincfg properties Conor Dooley
2026-02-03 17:29 ` Conor Dooley [this message]
2026-02-03 23:30 ` [rfc 0/2] pinctrl property checks Linus Walleij
2026-02-04 14:11 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260203-gleaming-perky-e12d6a5fe86f@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox