From: Tom Rini <trini@konsulko.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Michael Walle <michael@walle.cc>,
u-boot@lists.denx.de, Vladimir Oltean <vladimir.oltean@nxp.com>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Bharat Gooty <bharat.gooty@broadcom.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Simon Glass <sjg@chromium.org>,
Priyanka Jain <priyanka.jain@nxp.com>
Subject: Re: [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree
Date: Thu, 28 Oct 2021 09:51:24 -0400 [thread overview]
Message-ID: <20211028135124.GU8284@bill-the-cat> (raw)
In-Reply-To: <87wnlx9sml.wl-maz@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]
On Thu, Oct 28, 2021 at 02:38:26PM +0100, Marc Zyngier wrote:
> On Thu, 28 Oct 2021 13:31:13 +0100,
> Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Oct 28, 2021 at 10:01:34AM +0100, Marc Zyngier wrote:
> > > On Wed, 27 Oct 2021 17:54:52 +0100,
> > > Michael Walle <michael@walle.cc> wrote:
> > > >
> > > > Please stop throwing every ad-hoc information in the device tree. Use the
> > > > official bindings (or maybe some bindings which will get approved soon).
> > > >
> > > > On the quest of syncing the device tree used in u-boot with the one used in
> > > > linux, there is this nice piece:
> > > >
> > > > gic_lpi_base: syscon@0x80000000 {
> > > > compatible = "gic-lpi-base";
> > > > reg = <0x0 0x80000000 0x0 0x100000>;
> > > > max-gic-redistributors = <2>;
> > > > };
> > > >
> > > > There is no offical binding for it. Also, the chances that there will be
> > > > one are virtually zero. We need to get rid of it. In fact, most information
> > > > there are already known or can be deduced via the offical binding.
> > >
> > > It is not "virtually zero". It is *exactly* zero. This node only shows
> > > that the author didn't understand the nature of the problem, nor were
> > > they aware of the existing solution which has been around since July
> > > 2018. This solution doesn't require any update to the binding, only to
> > > reserve the memory.
> > >
> > > I really wish people would stop piling crap in u-boot, and that the
> > > u-boot maintainers would reach out to people familiar with the
> > > architecture before merging this sort of changes.
> >
> > I'd be happy to reach out to people if I knew who would be receptive to
> > spending some of their already I assume overload spare time looking in
> > to things. If you're volunteering for "GIC related things" I'd be happy
> > to CC you when patches come up. Thanks!
>
> Absolutely. It is far less painful for me to quickly eyeball a change
> and ask pointed questions on the spot, rather than having to reverse
> engineer a set of dubious changes months after they have been merged.
>
> I already provide similar "services" for EDK2, for example, so getting
> the odd u-boot patch in my k.org inbox isn't a big deal.
Will do, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-28 13:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 16:54 [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree Michael Walle
2021-10-27 16:54 ` [PATCH 1/2] Revert "arm64: Layerscape: Survive LPI one-way reset workaround" Michael Walle
2021-10-28 21:11 ` Marc Zyngier
2021-10-31 16:23 ` Tom Rini
2021-10-27 16:54 ` [PATCH 2/2] Revert "arch: arm: use dt and UCLASS_SYSCON to get gic lpi details" Michael Walle
2021-10-28 21:09 ` Marc Zyngier
2021-10-28 21:35 ` Tom Rini
2021-10-29 11:49 ` Michael Walle
2021-10-29 12:00 ` Marc Zyngier
2021-10-31 16:45 ` Z.Q. Hou
2021-10-31 16:58 ` Michael Walle
2021-11-01 9:38 ` Marc Zyngier
2021-10-31 16:24 ` Tom Rini
2021-10-28 9:01 ` [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree Marc Zyngier
2021-10-28 9:20 ` Bharat Gooty
2021-10-28 9:49 ` Marc Zyngier
2021-10-28 10:27 ` Bharat Gooty
2021-10-28 14:39 ` Marc Zyngier
2021-10-28 11:21 ` Michael Walle
2021-10-28 11:35 ` Bharat Gooty
2021-10-28 12:09 ` Michael Walle
2021-10-28 14:42 ` Marc Zyngier
2021-10-28 12:31 ` Tom Rini
2021-10-28 13:38 ` Marc Zyngier
2021-10-28 13:51 ` Tom Rini [this message]
2021-10-28 22:36 ` Simon Glass
2021-10-29 11:54 ` Michael Walle
2021-10-29 21:17 ` Simon Glass
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=20211028135124.GU8284@bill-the-cat \
--to=trini@konsulko.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bharat.gooty@broadcom.com \
--cc=maz@kernel.org \
--cc=michael@walle.cc \
--cc=priyanka.jain@nxp.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=vladimir.oltean@nxp.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