From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bhargav Joshi <j.bhargav.u@gmail.com>
Cc: 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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/7] dt-bindings: arm: omap: document missing AM33xx boards and SoMs
Date: Fri, 13 Nov 2026 11:50:41 +0100 [thread overview]
Message-ID: <20261113-marvellous-prompt-cuttlefish-c4f1a3@quoll> (raw)
In-Reply-To: <20261111-ti-omap-dts-fix-v1-2-19022d1ff4b4@gmail.com>
On Wed, Nov 11, 2026 at 01:22:32AM +0530, Bhargav Joshi wrote:
> Several AM33xx devicetrees trigger dtbs_check warnings because their
> compatibles are missing from omap.yaml.
>
> Document the missing AM33xx compatibles (Bosch Guardian, Gumstix Pepper,
> Moxa UC-2101, TCL SL50, BeagleBone Blue, AM335x EVM-SK, and VScom
> OnRISC), add entries for the EETS PDU001 and Newflow NanoBone boards,
> and for boards based on the MYiR MYC-AM335X and Grinn ChiliSOM modules.
>
> Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
> ---
> Documentation/devicetree/bindings/arm/ti/omap.yaml | 23 ++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> index f694dcbf23486..c97eb4953ed25 100644
> --- a/Documentation/devicetree/bindings/arm/ti/omap.yaml
> +++ b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> @@ -104,13 +104,22 @@ properties:
> - description: TI AM33 based platform
> items:
> - enum:
> + - bosch,am335x-guardian
> - compulab,cm-t335
> + - eets,pdu001
No such compatible, so it cannot be missing from omap.yaml.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-13 10:50 UTC|newest]
Thread overview: 11+ 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-13 10:48 ` Krzysztof Kozlowski
2026-11-10 19:52 ` [PATCH 2/7] dt-bindings: arm: omap: document missing AM33xx boards and SoMs Bhargav Joshi
2026-11-13 10:50 ` Krzysztof Kozlowski [this message]
2026-11-10 19:52 ` [PATCH 3/7] dt-bindings: arm: omap: document BeagleBone family board compatibles Bhargav Joshi
2026-11-13 10:51 ` Krzysztof Kozlowski
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 ` [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=20261113-marvellous-prompt-cuttlefish-c4f1a3@quoll \
--to=krzk@kernel.org \
--cc=aaro.koskinen@iki.fi \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j.bhargav.u@gmail.com \
--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®