From: Kory Maincent <kory.maincent@bootlin.com>
To: 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>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Barker <paul.barker@sancloud.com>,
Marc Murphy <marc.murphy@sancloud.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Romain Gantois <romain.gantois@bootlin.com>,
Thomas Bonnefille <thomas.bonnefille@bootlin.com>,
Bajjuri Praneeth <praneeth@ti.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Andrew Davis <afd@ti.com>
Subject: [PATCH 0/2] arm: dts: OMAP: Clean up devicetree bindings and compatible strings
Date: Fri, 20 Jun 2025 10:24:07 +0200 [thread overview]
Message-ID: <20250620-ti_dts_clean-v1-0-786a3059bca7@bootlin.com> (raw)
This series addresses inconsistencies in OMAP devicetree bindings and
compatible strings for AM33xx-based boards:
- Add missing compatible strings to binding documentation
- Update vendor prefix from "ti" to "beagle" for BeagleBone boards
to reflect actual hardware vendors
- Remove redundant compatible strings from device properties
Note: Originally attempted to align devicetree model descriptions but
received pushback due to Debian script dependencies (see thread at
https://lore.kernel.org/all/7e854232-f02f-4ad6-b65e-22c18d1d9fe5@jm0.eu/).
The compatible string changes may face similar concerns and would
benefit from devicetree maintainer review.
This work was split from a larger series to address feedback and allow
independent progression of each topic area. Original series:
https://lore.kernel.org/r/20250617-bbg-v4-0-827cbd606db6@bootlin.com
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Kory Maincent (2):
dt-bindings: omap: Add missing AM33xx compatible strings
arm: dts: omap: Remove incorrect compatible strings from device trees
Documentation/devicetree/bindings/arm/ti/omap.yaml | 22 +++++++++++++++++++++-
arch/arm/boot/dts/ti/omap/am335x-base0033.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-bone.dts | 2 +-
.../boot/dts/ti/omap/am335x-boneblack-wireless.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-boneblack.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-boneblue.dts | 2 +-
.../boot/dts/ti/omap/am335x-bonegreen-wireless.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-bonegreen.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-chiliboard.dts | 3 +--
arch/arm/boot/dts/ti/omap/am335x-myirtech-myd.dts | 2 +-
.../arm/boot/dts/ti/omap/am335x-osd3358-sm-red.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-pocketbeagle.dts | 2 +-
.../ti/omap/am335x-sancloud-bbe-extended-wifi.dts | 5 +----
.../boot/dts/ti/omap/am335x-sancloud-bbe-lite.dts | 5 +----
arch/arm/boot/dts/ti/omap/am335x-sancloud-bbe.dts | 2 +-
arch/arm/boot/dts/ti/omap/am335x-shc.dts | 2 +-
16 files changed, 36 insertions(+), 23 deletions(-)
---
base-commit: e22b9ddaf3afd031abc350c303c7c07a51c569d8
change-id: 20250619-ti_dts_clean-d1d86c9e675f
Best regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next reply other threads:[~2025-06-20 8:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 8:24 Kory Maincent [this message]
2025-06-20 8:24 ` [PATCH 1/2] dt-bindings: omap: Add missing AM33xx " Kory Maincent
2025-06-20 14:08 ` Conor Dooley
2025-06-20 14:09 ` Conor Dooley
2025-06-20 14:26 ` Kory Maincent
2025-06-23 14:36 ` Conor Dooley
2025-06-20 8:24 ` [PATCH 2/2] arm: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-20 14:15 ` [PATCH 0/2] arm: dts: OMAP: Clean up devicetree bindings and compatible strings 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=20250620-ti_dts_clean-v1-0-786a3059bca7@bootlin.com \
--to=kory.maincent@bootlin.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--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=marc.murphy@sancloud.com \
--cc=paul.barker@sancloud.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.bonnefille@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--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®