public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Tom Rini <trini@konsulko.com>
Cc: Nishanth Menon <nm@ti.com>, Conor Dooley <conor+dt@kernel.org>,
	 devicetree@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
	 Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] ARM: dts: omap4-panda-a4: Add missing model and compatible properties
Date: Thu, 23 Jan 2025 09:57:46 -0600	[thread overview]
Message-ID: <173764775069.3793491.1320038672918259827.robh@kernel.org> (raw)
In-Reply-To: <20250121200749.4131923-1-trini@konsulko.com>


On Tue, 21 Jan 2025 14:07:49 -0600, Tom Rini wrote:
> When moving the model and compatible properties out of the common
> Pandaboard files and in to the specific boards, the omap4-panda-a4
> file wasn't updated as well and so has lacked a model and compatible
> entry ever since.
> 
> Fixes: a1a57abaaf82 ("ARM: dts: omap4-panda: Fix model and SoC family details")
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> Given how long this has been broken it's entirely plausible no a4
> hardware even exists anymore and so dropping this file instead makes
> sense. I only found this because scripts/make_fit.py crashed on these
> properties being missing.
> 
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: linux-omap@vger.kernel.org
> Cc: devicetree@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
>  arch/arm/boot/dts/ti/omap/omap4-panda-a4.dts | 5 +++++
>  1 file changed, 5 insertions(+)
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/ti/' for 20250121200749.4131923-1-trini@konsulko.com:

arch/arm/boot/dts/ti/omap/omap4-panda-a4.dtb: /: failed to match any schema with compatible: ['ti,omap4-panda-a4', 'ti,omap4-panda', 'ti,omap4430', 'ti,omap4']






  parent reply	other threads:[~2025-01-23 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 20:07 [PATCH] ARM: dts: omap4-panda-a4: Add missing model and compatible properties Tom Rini
2025-01-21 22:50 ` Kevin Hilman
2025-01-22  0:08   ` Tom Rini
2025-01-22 20:46     ` Andreas Kemnade
2025-01-22 20:56       ` Robert Nelson
2025-01-22 21:10         ` Tom Rini
2025-01-22 21:52           ` Robert Nelson
2025-01-22 22:18             ` Tom Rini
2025-01-22 22:25               ` Robert Nelson
2025-01-22 22:41               ` Andreas Kemnade
2025-01-22 22:22           ` Andreas Kemnade
2025-01-23 15:57 ` Rob Herring (Arm) [this message]
2025-02-06  0:37 ` Kevin Hilman

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=173764775069.3793491.1320038672918259827.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=tony@atomide.com \
    --cc=trini@konsulko.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