From: Andreas Kemnade <andreas@kemnade.info>
To: Tom Rini <trini@konsulko.com>
Cc: Robert Nelson <robertcnelson@gmail.com>,
Kevin Hilman <khilman@kernel.org>,
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: Wed, 22 Jan 2025 23:41:19 +0100 [thread overview]
Message-ID: <20250122234119.0913cb4f@akair> (raw)
In-Reply-To: <20250122221843.GE60249@bill-the-cat>
Am Wed, 22 Jan 2025 16:18:43 -0600
schrieb Tom Rini <trini@konsulko.com>:
> On Wed, Jan 22, 2025 at 03:52:47PM -0600, Robert Nelson wrote:
> > On Wed, Jan 22, 2025 at 3:10 PM Tom Rini <trini@konsulko.com> wrote:
> > >
> > > On Wed, Jan 22, 2025 at 02:56:19PM -0600, Robert Nelson wrote:
> > > > On Wed, Jan 22, 2025 at 2:46 PM Andreas Kemnade <andreas@kemnade.info> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Am Tue, 21 Jan 2025 18:08:24 -0600
> > > > > schrieb Tom Rini <trini@konsulko.com>:
> > > > >
> > > > > > > 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.
> > > > >
> > > > > I am still testing stuff with pandaboards. But I do not have the a4
> > > > > one. So yes they are functional. Compared with other devices still in
> > > > > use using the same SoC, here you can play around with everything, know
> > > > > the device. so it is a reference for keeping the really interesting
> > > > > devices working.
> > > > >
> > > > > Regarding the a4: I think it is better to keep that one in, just that
> > > > > nobody gets confused if he/she digs out his panda board for some
> > > > > comparison test and uses a wrong board revision.
> > > >
> > > > Do you want an a4? I could dig one or two out! ;)
> > >
> > > Unless I'm missing something, the a4 hasn't been bootable by upstream in
> > > about 10 years now... There's no top-level compatible, so there's no
> > > match in the generic board code. I can't recall if the A4 versions were
> > > available to anyone other than maintainers and beagleboard.org folks
> > > themselves as part of bring-up/testing. I know I had one and ewasted it
> > > a while ago.
> >
> > PandaBoard EA1->A3 = omap4-panda.dtb
> > PandaBoard A4->+ (non ES) = omap4-panda-a4.dtb
> >
> > A4 was the final production version of the non ES Panda..
>
> Oh! My memory sucks here, sorry for the confusion. But it's also still
> the case that omap4-panda-a4.dtb hasn't had a top-level compatible
> string, so can it even be functionally used?
>
maybe people just revert to omap4-panda.dtb, it should not hurt having
internal and external pullups. I have the A2.
Regards,
Andreas
next prev parent reply other threads:[~2025-01-22 22:41 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 [this message]
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=20250122234119.0913cb4f@akair \
--to=andreas@kemnade.info \
--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=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.