From: Marc Zyngier <maz@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: Bharat Gooty <bharat.gooty@broadcom.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Simon Glass <sjg@chromium.org>,
Priyanka Jain <priyanka.jain@nxp.com>,
Tom Rini <trini@konsulko.com>,
Roman Bacik <roman.bacik@broadcom.com>
Subject: Re: [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree
Date: Thu, 28 Oct 2021 15:42:43 +0100 [thread overview]
Message-ID: <87tuh19png.wl-maz@kernel.org> (raw)
In-Reply-To: <15b7dc28e0226621fe8c746afe321832@walle.cc>
On Thu, 28 Oct 2021 12:21:59 +0100,
Michael Walle <michael@walle.cc> wrote:
>
> Am 2021-10-28 11:20, schrieb Bharat Gooty:
> > On Thu, Oct 28, 2021 at 2:33 PM Marc Zyngier <maz@kernel.org> wrote:
>
> > For GIC V3, once the LPI tables are programmed, we can not update it,
> > unless we do a reset.
> > For the kexec kernel, where the reboot does not happen, in this case,
> > during the new kernel boot, the new LPI tables address will not be
> > updated.
>
> kexec.. this should have really gone into both the commit message _and_
> the kconfig menu. In fact, it is really just a workaround for the kexec
> case. If I understand it correctly, the kernel is able to communicate
> the reserved memory area, but only if you have EFI support. So, as a
> workaround, the bootloader can pre-allocate the memory and put it in
> the device tree, which is then passed from the old to the new kernel
> and the reservation is preserved. Correct, Marc?
See my reply to Bharat. Either you use EFI, or you reserve the memory
and program the RDs. In either of these two cases, kexec will just work.
> But all of this doesn't need any new device tree node.
Exactly. The whole syscon stuff is a point hack that makes no sense,
and which isn't parsed by any upstream SW.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-10-28 14:42 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 [this message]
2021-10-28 12:31 ` Tom Rini
2021-10-28 13:38 ` Marc Zyngier
2021-10-28 13:51 ` Tom Rini
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=87tuh19png.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bharat.gooty@broadcom.com \
--cc=michael@walle.cc \
--cc=priyanka.jain@nxp.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=roman.bacik@broadcom.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--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