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 7/7] ARM: dts: ti: omap: omap3: drop redundant ti,omap34xx compatible
Date: Wed, 11 Nov 2026 01:22:37 +0530 [thread overview]
Message-ID: <20261111-ti-omap-dts-fix-v1-7-19022d1ff4b4@gmail.com> (raw)
In-Reply-To: <20261111-ti-omap-dts-fix-v1-0-19022d1ff4b4@gmail.com>
Commit 6ddf6c91e6f8 ("ARM: dts: omap3: bulk convert compatible to be
explicitly ti,omap3430 or ti,omap3630 or ti,am3517") added "ti,omap3430"
to but left "ti,omap34xx" behind. Drop the redundant "ti,omap34xx".
Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
arch/arm/boot/dts/ti/omap/omap3-cm-t3530.dts | 2 +-
arch/arm/boot/dts/ti/omap/omap3-ha-lcd.dts | 3 ++-
arch/arm/boot/dts/ti/omap/omap3-ha.dts | 3 ++-
arch/arm/boot/dts/ti/omap/omap3-sbc-t3530.dts | 3 ++-
arch/arm/boot/dts/ti/omap/omap3-thunder.dts | 3 ++-
5 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/arch/arm/boot/dts/ti/omap/omap3-cm-t3530.dts b/arch/arm/boot/dts/ti/omap/omap3-cm-t3530.dts
index 0c6f14963e5ea..0a32ccc84e932 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-cm-t3530.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-cm-t3530.dts
@@ -9,7 +9,7 @@
/ {
model = "CompuLab CM-T3530";
- compatible = "compulab,omap3-cm-t3530", "ti,omap3430", "ti,omap34xx", "ti,omap3";
+ compatible = "compulab,omap3-cm-t3530", "ti,omap3430", "ti,omap3";
/* Regulator to trigger the reset signal of the Wifi module */
mmc2_sdio_reset: regulator-mmc2-sdio-reset {
diff --git a/arch/arm/boot/dts/ti/omap/omap3-ha-lcd.dts b/arch/arm/boot/dts/ti/omap/omap3-ha-lcd.dts
index 94f6b7931e333..e231209be3a15 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-ha-lcd.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-ha-lcd.dts
@@ -8,7 +8,8 @@
/ {
model = "TI OMAP3 HEAD acoustics LCD-baseboard with TAO3530 SOM";
- compatible = "headacoustics,omap3-ha-lcd", "technexion,omap3-tao3530", "ti,omap3430", "ti,omap34xx", "ti,omap3";
+ compatible = "headacoustics,omap3-ha-lcd", "technexion,omap3-tao3530",
+ "ti,omap3430", "ti,omap3";
};
&omap3_pmx_core {
diff --git a/arch/arm/boot/dts/ti/omap/omap3-ha.dts b/arch/arm/boot/dts/ti/omap/omap3-ha.dts
index 19e471eb3b4e1..d4d883f588eca 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-ha.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-ha.dts
@@ -8,7 +8,8 @@
/ {
model = "TI OMAP3 HEAD acoustics baseboard with TAO3530 SOM";
- compatible = "headacoustics,omap3-ha", "technexion,omap3-tao3530", "ti,omap3430", "ti,omap34xx", "ti,omap3";
+ compatible = "headacoustics,omap3-ha", "technexion,omap3-tao3530",
+ "ti,omap3430", "ti,omap3";
};
&omap3_pmx_core {
diff --git a/arch/arm/boot/dts/ti/omap/omap3-sbc-t3530.dts b/arch/arm/boot/dts/ti/omap/omap3-sbc-t3530.dts
index 1beefc3194224..c2b4c707cd9e0 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-sbc-t3530.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-sbc-t3530.dts
@@ -8,7 +8,8 @@
/ {
model = "CompuLab SBC-T3530 with CM-T3530";
- compatible = "compulab,omap3-sbc-t3530", "compulab,omap3-cm-t3530", "ti,omap3430", "ti,omap34xx", "ti,omap3";
+ compatible = "compulab,omap3-sbc-t3530", "compulab,omap3-cm-t3530",
+ "ti,omap3430", "ti,omap3";
aliases {
display0 = &dvi0;
diff --git a/arch/arm/boot/dts/ti/omap/omap3-thunder.dts b/arch/arm/boot/dts/ti/omap/omap3-thunder.dts
index c87956c59b083..a0cd06d4e39ac 100644
--- a/arch/arm/boot/dts/ti/omap/omap3-thunder.dts
+++ b/arch/arm/boot/dts/ti/omap/omap3-thunder.dts
@@ -8,7 +8,8 @@
/ {
model = "TI OMAP3 Thunder baseboard with TAO3530 SOM";
- compatible = "technexion,omap3-thunder", "technexion,omap3-tao3530", "ti,omap3430", "ti,omap34xx", "ti,omap3";
+ compatible = "technexion,omap3-thunder", "technexion,omap3-tao3530",
+ "ti,omap3430", "ti,omap3";
};
&omap3_pmx_core {
--
2.56.0
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 ` [PATCH 4/7] dt-bindings: arm: omap: document missing OMAP3, AM35, and OMAP5 boards Bhargav Joshi
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 ` Bhargav Joshi [this message]
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-7-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®