From: Kory Maincent <kory.maincent@bootlin.com>
To: Jason Kridner <jkridner@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>, 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>,
Russell King <linux@armlinux.org.uk>,
Paul Barker <paul.barker@sancloud.com>,
Marc Murphy <marc.murphy@sancloud.com>, Andrew Davis <afd@ti.com>,
Bajjuri Praneeth <praneeth@ti.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/7] ARM: dts: omap: Remove incorrect compatible strings from device trees
Date: Mon, 16 Jun 2025 10:39:19 +0200 [thread overview]
Message-ID: <20250616103919.2d678c1a@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <CA+T6QPnaCFZyRsv9q3bcOrTc22nA0AOXy0tR_SpAkGVVPQqfLg@mail.gmail.com>
Le Fri, 13 Jun 2025 13:52:23 -0500,
Jason Kridner <jkridner@gmail.com> a écrit :
> On Fri, Jun 13, 2025 at 10:49 AM Kory Maincent <kory.maincent@bootlin.com>
> wrote:
>
> > Several device trees incorrectly included extraneous compatible strings
> > in their compatible property lists. The policy is to only describe the
> > specific board name and SoC name to avoid confusion.
> >
> > Remove these incorrect compatible strings to fix the inconsistency.
> >
> > Also fix board vendor prefixes for BeagleBoard variants that were
> > incorrectly using "ti" instead of "beagle" or "seeed".
> >
> > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > ---
> >
> > Changes in v3:
> > - Remove extraneous compatible strings.
> > - Replace BeagleBone board name vendor.
> >
> > Changes in v2:
> > - New patch
> > ---
> > arch/arm/boot/dts/ti/omap/am335x-base0033.dts | 2 +-
> > arch/arm/boot/dts/ti/omap/am335x-bone.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-boneblack-wireless.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-boneblack.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-boneblue.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-bonegreen-wireless.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-bonegreen.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-chiliboard.dts | 3 +--
> > arch/arm/boot/dts/ti/omap/am335x-myirtech-myd.dts | 2 +-
> > arch/arm/boot/dts/ti/omap/am335x-osd3358-sm-red.dts | 2 +-
> > arch/arm/boot/dts/ti/omap/am335x-pocketbeagle.dts | 4 ++--
> > arch/arm/boot/dts/ti/omap/am335x-sancloud-bbe-extended-wifi.dts | 5 +----
> > arch/arm/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 +-
> > 15 files changed, 22 insertions(+), 29 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/ti/omap/am335x-base0033.dts
> > b/arch/arm/boot/dts/ti/omap/am335x-base0033.dts
> > index 46078af4b7a3..176de29de2a6 100644
> > --- a/arch/arm/boot/dts/ti/omap/am335x-base0033.dts
> > +++ b/arch/arm/boot/dts/ti/omap/am335x-base0033.dts
> > @@ -9,7 +9,7 @@
> >
> > / {
> > model = "IGEP COM AM335x on AQUILA Expansion";
> > - compatible = "isee,am335x-base0033", "isee,am335x-igep0033",
> > "ti,am33xx";
> > + compatible = "isee,am335x-base0033", "ti,am33xx";
> >
> > hdmi {
> > compatible = "ti,tilcdc,slave";
> > diff --git a/arch/arm/boot/dts/ti/omap/am335x-bone.dts
> > b/arch/arm/boot/dts/ti/omap/am335x-bone.dts
> > index b5d85ef51a02..2790c0c5a473 100644
> > --- a/arch/arm/boot/dts/ti/omap/am335x-bone.dts
> > +++ b/arch/arm/boot/dts/ti/omap/am335x-bone.dts
> > @@ -8,8 +8,8 @@
> > #include "am335x-bone-common.dtsi"
> >
> > / {
> > - model = "TI AM335x BeagleBone";
> > - compatible = "ti,am335x-bone", "ti,am33xx";
> > + model = "AM335x BeagleBone";
>
>
> We have software that looks at these in running systems, so I’d be ok not
> to change. If changing, why not “BeagleBoard.org BeagleBone”? Not sure of
> the convention to mention the SoC, but AM335x is not part of the product
> name.
Is it ok to change it or not then? Ok to move on to BeagleBoard.org.
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-06-16 8:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 15:49 [PATCH v3 0/7] Add support for BeagleBone Green Eco board Kory Maincent
2025-06-13 15:49 ` [PATCH v3 1/7] dt-bindings: omap: Add missing AM33xx compatible strings Kory Maincent
2025-06-13 17:10 ` Andrew Davis
2025-06-13 17:21 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 2/7] ARM: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-13 20:33 ` Jason Kridner
[not found] ` <CA+T6QPnaCFZyRsv9q3bcOrTc22nA0AOXy0tR_SpAkGVVPQqfLg@mail.gmail.com>
2025-06-16 8:39 ` Kory Maincent [this message]
2025-06-16 11:39 ` Josua Mayer
2025-06-16 12:29 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 3/7] arm: dts: omap: am335x-bone-common: Rename tps to generic pmic node Kory Maincent
2025-06-13 15:49 ` [PATCH v3 4/7] dt-bindings: omap: Add Seeed BeagleBone Green Eco Kory Maincent
2025-06-13 16:05 ` Robert Nelson
2025-06-16 14:52 ` Conor Dooley
2025-06-13 15:49 ` [PATCH v3 5/7] arm: dts: omap: Add support for BeagleBone Green Eco board Kory Maincent
2025-06-13 16:03 ` Robert Nelson
2025-06-13 16:15 ` Kory Maincent
2025-06-13 15:49 ` [PATCH v3 6/7] arm: omap2plus_defconfig: Enable TPS65219 regulator Kory Maincent
2025-06-13 15:49 ` [PATCH v3 7/7] arm: multi_v7_defconfig: " Kory Maincent
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=20250616103919.2d678c1a@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marc.murphy@sancloud.com \
--cc=paul.barker@sancloud.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).