mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 5/7] ARM: dts: ti: omap: am335x: add board compatibles for nano and pdu001
Date: Wed, 11 Nov 2026 01:22:35 +0530	[thread overview]
Message-ID: <20261111-ti-omap-dts-fix-v1-5-19022d1ff4b4@gmail.com> (raw)
In-Reply-To: <20261111-ti-omap-dts-fix-v1-0-19022d1ff4b4@gmail.com>

am335x-nano.dts and am335x-pdu001.dts only specify the SoC compatible
"ti,am33xx", causing dtbs_check warnings. Add board specific
"newflow,am335x-nanobone" for the Newflow NanoBone and "eets,pdu001" for
the EETS PDU001.

Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
 arch/arm/boot/dts/ti/omap/am335x-nano.dts   | 2 +-
 arch/arm/boot/dts/ti/omap/am335x-pdu001.dts | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/ti/omap/am335x-nano.dts b/arch/arm/boot/dts/ti/omap/am335x-nano.dts
index d51cdd6e1ab40..40e60e0abaa87 100644
--- a/arch/arm/boot/dts/ti/omap/am335x-nano.dts
+++ b/arch/arm/boot/dts/ti/omap/am335x-nano.dts
@@ -8,7 +8,7 @@
 
 / {
 	model = "Newflow AM335x NanoBone";
-	compatible = "ti,am33xx";
+	compatible = "newflow,am335x-nanobone", "ti,am33xx";
 
 	cpus {
 		cpu@0 {
diff --git a/arch/arm/boot/dts/ti/omap/am335x-pdu001.dts b/arch/arm/boot/dts/ti/omap/am335x-pdu001.dts
index 9f611debc2090..c36e1b7922c9c 100644
--- a/arch/arm/boot/dts/ti/omap/am335x-pdu001.dts
+++ b/arch/arm/boot/dts/ti/omap/am335x-pdu001.dts
@@ -18,7 +18,7 @@
 
 / {
 	model = "EETS,PDU001";
-	compatible = "ti,am33xx";
+	compatible = "eets,pdu001", "ti,am33xx";
 
 	chosen {
 		stdout-path = "serial3:115200n8";

-- 
2.56.0


  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 ` Bhargav Joshi [this message]
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-5-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®