public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: linux-kernel@vger.kernel.org, Nishanth Menon <nm@ti.com>,
	Tony Lindgren <tony@atomide.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap4-panda-a4: Add missing model and compatible properties
Date: Tue, 21 Jan 2025 18:08:24 -0600	[thread overview]
Message-ID: <20250122000824.GJ3476@bill-the-cat> (raw)
In-Reply-To: <7hmsfjn5mm.fsf@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

On Tue, Jan 21, 2025 at 02:50:41PM -0800, Kevin Hilman wrote:
> Hi Tom,
> 
> Tom Rini <trini@konsulko.com> writes:
> 
> > 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>
> > ---
> 
> Checkpatch tells me:
> 
>  WARNING: DT compatible string "ti,omap4-panda-a4" appears un-documented
> 
> So I think Documentation/devicetree/bindings/arm/ti/omap.yaml needs an
> update too.  (and note the binding update should be a separate patch[1])

Regular panda is there, so yeah, it's easy enough to add the a4 variant.
I assume if I post that they'll get merged in the right order?

> > 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.
> 
> If keeping it is just this binding update, then I'd say we keep it, but
> if it gets any more paninful to maintain, I'm also not going to argue
> very hard to keep it.

I'm not in the position to see if any of the Pandaboards work at this
point, so I don't know if they're otherwise functional or a huge pile of
problems.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2025-01-22  0:08 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 [this message]
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)
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=20250122000824.GJ3476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@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