From: Rob Herring <robh@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Andrew Davis <afd@ti.com>, Tony Lindgren <tony@atomide.com>,
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>,
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 v2 2/5] binding: omap: Add lots of missing omap AM33 compatibles
Date: Wed, 25 Jun 2025 14:44:53 -0500 [thread overview]
Message-ID: <20250625194453.GA2093083-robh@kernel.org> (raw)
In-Reply-To: <20250610100544.4beb07e2@kmaincent-XPS-13-7390>
On Tue, Jun 10, 2025 at 10:05:44AM +0200, Kory Maincent wrote:
> Le Mon, 9 Jun 2025 18:34:10 -0500,
> Andrew Davis <afd@ti.com> a écrit :
>
> > On 6/9/25 10:43 AM, Kory Maincent wrote:
> > > Add several compatible strings that were missing from the binding
> > > documentation. Add description for Bone, BoneBlack and BoneGreen
> > > variants.
> > >
> > > Add several compatible that were missing from the binding.
> > >
> > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > > ---
> > >
> > > Change in v2:
> > > - New patch
> > > ---
> > > Documentation/devicetree/bindings/arm/ti/omap.yaml | 38
> > > ++++++++++++++++++++++ 1 file changed, 38 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml
> > > b/Documentation/devicetree/bindings/arm/ti/omap.yaml index
> > > 3603edd7361d..c43fa4f4af81 100644 ---
> > > a/Documentation/devicetree/bindings/arm/ti/omap.yaml +++
> > > b/Documentation/devicetree/bindings/arm/ti/omap.yaml @@ -104,12 +104,50 @@
> > > properties:
> > > - description: TI AM33 based platform
> > > items:
> > > - enum:
> > > + - bosch,am335x-guardian
> > > - compulab,cm-t335
> > > + - grinn,am335x-chilisom
> > > + - gumstix,am335x-pepper
> > > + - moxa,uc-2101
> > > - moxa,uc-8100-me-t
> > > + - myir,myc-am335x
> > > + - myir,myd-am335x
> > > - novatech,am335x-lxm
> > > + - oct,osd3358-sm-refdesign
> > > + - tcl,am335x-sl50
> > > - ti,am335x-bone
> > > - ti,am335x-evm
> > > + - ti,am335x-evmsk
> > > + - ti,am335x-pocketbeagle
> > > + - ti,am335x-shc
> > > - ti,am3359-icev2
> > > + - vscom,onrisc
> > > + - const: ti,am33xx
> > > +
> > > + - description: TI bone variants based on TI AM335
> >
> > Do we really need these "bone variants" split out from the above
> > list of TI AM33 based boards? We don't do that for any of the other
> > boards, you get a SoC and a Board compatible, every classification
> > in-between is just unneeded.
>
> As omap maintainers prefer. I did that to have the least amount of change in
> the devicetree. We could have U-boot using these compatible but after a quick
> check it seems not.
I agree with both. The intermediate compatibles that TI in particular
went crazy on have proven to be not useful. However, between having to
fix existing .dts files and keeping them, I would just keep them.
Rob
next prev parent reply other threads:[~2025-06-25 19:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 15:43 [PATCH v2 0/5] Add support for BeagleBone Green Eco board Kory Maincent
2025-06-09 15:43 ` [PATCH v2 1/5] arm: dts: omap: Remove incorrect compatible strings from device trees Kory Maincent
2025-06-09 20:08 ` Andreas Kemnade
2025-06-09 20:35 ` Kory Maincent
2025-06-09 15:43 ` [PATCH v2 2/5] binding: omap: Add lots of missing omap AM33 compatibles Kory Maincent
2025-06-09 17:03 ` Conor Dooley
2025-06-09 19:50 ` Andreas Kemnade
2025-06-10 15:29 ` Conor Dooley
2025-06-10 12:48 ` Jason Kridner
2025-06-09 23:34 ` Andrew Davis
2025-06-10 8:05 ` Kory Maincent
2025-06-25 19:44 ` Rob Herring [this message]
2025-06-16 10:03 ` Andreas Kemnade
2025-06-11 9:06 ` Krzysztof Kozlowski
2025-06-09 15:43 ` [PATCH v2 3/5] arm: dts: omap: am335x-bone-common: Rename tps to generic pmic node Kory Maincent
2025-06-09 15:43 ` [PATCH v2 4/5] arm: dts: omap: Add support for BeagleBone Green Eco board Kory Maincent
2025-06-09 17:04 ` Conor Dooley
2025-06-09 20:45 ` Kory Maincent
2025-06-09 21:23 ` Andreas Kemnade
2025-06-10 15:26 ` Conor Dooley
2025-06-17 8:18 ` Krzysztof Kozlowski
2025-06-09 15:43 ` [PATCH v2 5/5] arm: omap2plus_defconfig: Enable TPS65219 regulator Kory Maincent
2025-06-11 21:13 ` Andrew Davis
2025-06-12 6:12 ` Andreas Kemnade
2025-06-12 13:09 ` Andrew Davis
2025-06-12 13:19 ` Mark Brown
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=20250625194453.GA2093083-robh@kernel.org \
--to=robh@kernel.org \
--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=khilman@baylibre.com \
--cc=kory.maincent@bootlin.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=praneeth@ti.com \
--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).