From: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
To: lee@kernel.org, andreas@kemnade.info
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
jihed.chaibi.dev@gmail.com
Subject: [PATCH] dt-bindings: mfd: twl: Reference converted YAML schemas for subnodes
Date: Wed, 25 Mar 2026 10:50:16 +0100 [thread overview]
Message-ID: <20260325095016.48752-1-jihed.chaibi.dev@gmail.com> (raw)
Now that all TWL subnode bindings (audio, keypad, twl4030-usb, gpio,
usb-comparator) have been converted to YAML and merged into mainline,
update the parent ti,twl.yaml to properly reference them via $ref.
Previously these subnodes used inline compatible definitions with
additionalProperties: true, which meant properties defined in the
subnode schemas were not being validated. Replace them with $ref to the
appropriate schemas and unevaluatedProperties: false, matching the
pattern already used by the madc, gpadc, and charger subnodes.
Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
---
.../devicetree/bindings/mfd/ti,twl.yaml | 50 ++++---------------
1 file changed, 10 insertions(+), 40 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/ti,twl.yaml b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
index 9cc3e4721612..a3af8e717ec7 100644
--- a/Documentation/devicetree/bindings/mfd/ti,twl.yaml
+++ b/Documentation/devicetree/bindings/mfd/ti,twl.yaml
@@ -265,47 +265,23 @@ properties:
audio:
type: object
- additionalProperties: true
-
- properties:
- compatible:
- const: ti,twl4030-audio
-
- required:
- - compatible
+ $ref: /schemas/sound/ti,twl4030-audio.yaml
+ unevaluatedProperties: false
keypad:
type: object
- additionalProperties: true
-
- properties:
- compatible:
- const: ti,twl4030-keypad
-
- required:
- - compatible
+ $ref: /schemas/input/ti,twl4030-keypad.yaml
+ unevaluatedProperties: false
twl4030-usb:
type: object
- additionalProperties: true
-
- properties:
- compatible:
- const: ti,twl4030-usb
-
- required:
- - compatible
+ $ref: /schemas/usb/ti,twl4030-usb.yaml
+ unevaluatedProperties: false
gpio:
type: object
- additionalProperties: true
-
- properties:
- compatible:
- const: ti,twl4030-gpio
-
- required:
- - compatible
+ $ref: /schemas/gpio/ti,twl4030-gpio.yaml
+ unevaluatedProperties: false
power:
type: object
@@ -371,14 +347,8 @@ properties:
usb-comparator:
type: object
- additionalProperties: true
-
- properties:
- compatible:
- const: ti,twl6030-usb
-
- required:
- - compatible
+ $ref: /schemas/usb/ti,twl6030-usb.yaml
+ unevaluatedProperties: false
pwm:
type: object
--
2.47.3
next reply other threads:[~2026-03-25 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:50 Jihed Chaibi [this message]
2026-03-27 7:37 ` [PATCH] dt-bindings: mfd: twl: Reference converted YAML schemas for subnodes Krzysztof Kozlowski
2026-04-01 17:57 ` Jihed Chaibi
2026-04-01 18:04 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2026-04-06 9:26 kernel test robot
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=20260325095016.48752-1-jihed.chaibi.dev@gmail.com \
--to=jihed.chaibi.dev@gmail.com \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.