From: Bhargav Joshi <j.bhargav.u@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>,
Mark Jackson <mpfj@newflow.co.uk>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org,
Bhargav Joshi <j.bhargav.u@gmail.com>
Subject: [PATCH 4/7] dt-bindings: arm: omap: document missing OMAP3, AM35, and OMAP5 boards
Date: Wed, 11 Nov 2026 01:22:34 +0530 [thread overview]
Message-ID: <20261111-ti-omap-dts-fix-v1-4-19022d1ff4b4@gmail.com> (raw)
In-Reply-To: <20261111-ti-omap-dts-fix-v1-0-19022d1ff4b4@gmail.com>
Several in-tree OMAP3, AM3517, and OMAP5 devicetrees fail dtbs_check
root node validation because their compatible tuples are missing or
incomplete in omap.yaml.
- Add missing "ti,omap3" const to the Gumstix Overo block.
- Document the IGEP OMAP3630 boards.
- Document CompuLab (CM-T3530, CM-T3730, CM-T3517, CM-T54), TechNexion
TAO3530 and Incostartec LILLY-A83X based platforms.
Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
Documentation/devicetree/bindings/arm/ti/omap.yaml | 56 +++++++++++++++++++++-
1 file changed, 55 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml b/Documentation/devicetree/bindings/arm/ti/omap.yaml
index e0af554388669..86c68f118c5a8 100644
--- a/Documentation/devicetree/bindings/arm/ti/omap.yaml
+++ b/Documentation/devicetree/bindings/arm/ti/omap.yaml
@@ -50,6 +50,24 @@ properties:
- const: ti,omap3430
- const: ti,omap3
+ - description: Compulab board variants based on TI OMAP3430
+ items:
+ - enum:
+ - compulab,omap3-sbc-t3530
+ - const: compulab,omap3-cm-t3530
+ - const: ti,omap3430
+ - const: ti,omap3
+
+ - description: TechNexion TAO3530 boards based on TI OMAP3430
+ items:
+ - enum:
+ - headacoustics,omap3-ha
+ - headacoustics,omap3-ha-lcd
+ - technexion,omap3-thunder
+ - const: technexion,omap3-tao3530
+ - const: ti,omap3430
+ - const: ti,omap3
+
- description: Early BeagleBoard revisions A to B4 with a timer quirk
items:
- const: ti,omap3-beagle-ab4
@@ -72,6 +90,7 @@ properties:
- enum:
- ti,omap3430
- ti,omap3630
+ - const: ti,omap3
- description: TI OMAP3630 SoC based platforms
items:
@@ -79,6 +98,10 @@ properties:
- amazon,omap3-echo # Amazon Echo (first generation)
- compulab,omap3-cm-t3730
- goldelico,gta04
+ - isee,omap3-igep0020
+ - isee,omap3-igep0020-rev-f
+ - isee,omap3-igep0030
+ - isee,omap3-igep0030-rev-g
- lg,omap3-sniper # LG Optimus Black
- logicpd,dm3730-som-lv-devkit # LogicPD Zoom DM3730 SOM-LV Development Kit
- logicpd,dm3730-torpedo-devkit # LogicPD Zoom DM3730 Torpedo + Wireless Development Kit
@@ -91,16 +114,40 @@ properties:
- const: ti,omap3630
- const: ti,omap3
+ - description: Compulab board variants based on TI OMAP3630
+ items:
+ - enum:
+ - compulab,omap3-sbc-t3730
+ - const: compulab,omap3-cm-t3730
+ - const: ti,omap3630
+ - const: ti,omap3
+
+ - description: Incostartec board variants based on TI OMAP3630
+ items:
+ - enum:
+ - incostartec,omap3-lilly-dbb056
+ - const: incostartec,omap3-lilly-a83x
+ - const: ti,omap3630
+ - const: ti,omap3
+
- description: TI AM35 SoC based platforms
items:
- enum:
- - compulab,omap3-sbc-t3517 # CompuLab SBC-T3517 with CM-T3517
+ - compulab,omap3-cm-t3517
- teejet,mt_ventoux
- ti,am3517-craneboard # TI AM3517 CraneBoard (TMDSEVM3517)
- ti,am3517-evm # TI AM3517 EVM (AM3517/05 TMDSEVM3517)
- const: ti,am3517
- const: ti,omap3
+ - description: Compulab board variants based on TI AM35
+ items:
+ - enum:
+ - compulab,omap3-sbc-t3517
+ - const: compulab,omap3-cm-t3517
+ - const: ti,am3517
+ - const: ti,omap3
+
- description: TI AM33 based platform
items:
- enum:
@@ -241,6 +288,13 @@ properties:
- ti,omap5-uevm
- const: ti,omap5
+ - description: Compulab board variants based on TI OMAP5
+ items:
+ - enum:
+ - compulab,omap5-sbc-t54
+ - const: compulab,omap5-cm-t54
+ - const: ti,omap5
+
additionalProperties: true
...
--
2.56.0
next prev parent reply other threads:[~2026-11-10 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 19:52 [PATCH 0/7] ARM: dts: ti: omap: fix dtbs_check warnings for omap binding Bhargav Joshi
2026-11-10 19:52 ` [PATCH 1/7] dt-bindings: vendor-prefixes: add eets and newflow Bhargav Joshi
2026-11-10 19:52 ` [PATCH 2/7] dt-bindings: arm: omap: document missing AM33xx boards and SoMs Bhargav Joshi
2026-11-10 19:52 ` [PATCH 3/7] dt-bindings: arm: omap: document BeagleBone family board compatibles Bhargav Joshi
2026-11-10 19:52 ` Bhargav Joshi [this message]
2026-11-10 19:52 ` [PATCH 5/7] ARM: dts: ti: omap: am335x: add board compatibles for nano and pdu001 Bhargav Joshi
2026-11-10 19:52 ` [PATCH 6/7] ARM: dts: ti: omap: omap4-panda-es: drop redundant fallback compatibles Bhargav Joshi
2026-11-10 19:52 ` [PATCH 7/7] ARM: dts: ti: omap: omap3: drop redundant ti,omap34xx compatible Bhargav Joshi
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=20261111-ti-omap-dts-fix-v1-4-19022d1ff4b4@gmail.com \
--to=j.bhargav.u@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj@newflow.co.uk \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
/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
all inboxes | Powered by JetHome®