From: Geert Uytterhoeven <geert+renesas@glider.be>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Thierry Reding" <thierry.reding@kernel.org>,
"Jonathan Hunter" <jonathanh@nvidia.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/2] arm64: dts: Drop CPU masks from GICv3 PPI interrupts
Date: Wed, 10 Jun 2026 17:09:52 +0200 [thread overview]
Message-ID: <cover.1781103355.git.geert+renesas@glider.be> (raw)
Hi all,
Unlike older GIC variants, the GICv3 DT bindings do not support
specifying a CPU mask in PPI interrupt specifiers. Hence this patch
series drop all such masks where they are still present.
Changes compared to v1:
- Drop applied patches,
- Rebase on top of commit d0298724f901d45c ("arm64: dts: exynos: Add
EL2 virtual timer interrupt") in soc/for-next.
This has been compile-tested only. But note that all such masks were
removed before from Renesas SoCs in commit 8b6a006c914aac17 ("arm64:
dts: renesas: Drop specifying the GIC_CPU_MASK_SIMPLE() for GICv3
systems")).
Thanks for your comments!
[1] "[PATCH 0/7] arm64: dts: Drop CPU masks from GICv3 PPI interrupts"
https://lore.kernel.org/cover.1772643434.git.geert+renesas@glider.be
Geert Uytterhoeven (2):
arm64: dts: exynos: gs101: Drop CPU masks from GICv3 PPI interrupts
arm64: dts: tegra: Drop CPU masks from GICv3 PPI interrupts
arch/arm64/boot/dts/exynos/google/gs101.dtsi | 10 +++++-----
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 10 +++++-----
2 files changed, 10 insertions(+), 10 deletions(-)
--
2.43.0
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2026-06-10 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:09 Geert Uytterhoeven [this message]
2026-06-10 15:09 ` [PATCH v2 1/2] arm64: dts: exynos: gs101: Drop CPU masks from GICv3 PPI interrupts Geert Uytterhoeven
2026-06-10 15:09 ` [PATCH v2 2/2] arm64: tegra: " Geert Uytterhoeven
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=cover.1781103355.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=andre.draszik@linaro.org \
--cc=arnd@arndb.de \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=thierry.reding@kernel.org \
--cc=tudor.ambarus@linaro.org \
/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