From: Marc Zyngier <maz@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Thierry Reding" <treding@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, imx@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: Drop CPU masks from GICv3 PPI interrupts
Date: Thu, 05 Mar 2026 11:03:17 +0000 [thread overview]
Message-ID: <86qzpy7d3e.wl-maz@kernel.org> (raw)
In-Reply-To: <24685144-c1bb-4084-80de-40989efbf4a1@oss.qualcomm.com>
On Thu, 05 Mar 2026 10:02:01 +0000,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>
> On 3/5/26 10:55 AM, Geert Uytterhoeven wrote:
> > Hi Konrad,
> >
> > On Thu, 5 Mar 2026 at 10:33, Konrad Dybcio
> > <konrad.dybcio@oss.qualcomm.com> wrote:
> >> On 3/4/26 6:10 PM, Geert Uytterhoeven wrote:
> >>> 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.
> >>
> >> I'm having trouble finding where that's used on pre-v3 even.. does
> >> that actually get processed on the older iterations?
> >
> > I had noticed the same, and had asked maz on IRC.
> > His answer:
> >
> > "so far, we have never seen a GICv{1,2} system that didn't have all
> > of its PPIs
> > connected to the same set of devices."
>
> lol, that's fun!
For some definition of fun. If you want to get a top-class headache,
have a look at what that means to handle a single INTID being routed
different drivers based on the *affinity* of the interrupt.
HW people who come up with these contraptions should be spanked
repeatedly and preferably asymmetrically.
N,
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Kevin Hilman" <khilman@baylibre.com>,
"Jerome Brunet" <jbrunet@baylibre.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Tudor Ambarus" <tudor.ambarus@linaro.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Thierry Reding" <treding@nvidia.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, imx@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] arm64: dts: Drop CPU masks from GICv3 PPI interrupts
Date: Thu, 05 Mar 2026 11:03:17 +0000 [thread overview]
Message-ID: <86qzpy7d3e.wl-maz@kernel.org> (raw)
In-Reply-To: <24685144-c1bb-4084-80de-40989efbf4a1@oss.qualcomm.com>
On Thu, 05 Mar 2026 10:02:01 +0000,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>
> On 3/5/26 10:55 AM, Geert Uytterhoeven wrote:
> > Hi Konrad,
> >
> > On Thu, 5 Mar 2026 at 10:33, Konrad Dybcio
> > <konrad.dybcio@oss.qualcomm.com> wrote:
> >> On 3/4/26 6:10 PM, Geert Uytterhoeven wrote:
> >>> 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.
> >>
> >> I'm having trouble finding where that's used on pre-v3 even.. does
> >> that actually get processed on the older iterations?
> >
> > I had noticed the same, and had asked maz on IRC.
> > His answer:
> >
> > "so far, we have never seen a GICv{1,2} system that didn't have all
> > of its PPIs
> > connected to the same set of devices."
>
> lol, that's fun!
For some definition of fun. If you want to get a top-class headache,
have a look at what that means to handle a single INTID being routed
different drivers based on the *affinity* of the interrupt.
HW people who come up with these contraptions should be spanked
repeatedly and preferably asymmetrically.
N,
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-03-05 11:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 17:10 [PATCH 0/7] arm64: dts: Drop CPU masks from GICv3 PPI interrupts Geert Uytterhoeven
2026-03-04 17:10 ` Geert Uytterhoeven
2026-03-04 17:10 ` [PATCH 1/7] arm64: dts: amlogic: s6: " Geert Uytterhoeven
2026-03-04 17:10 ` Geert Uytterhoeven
2026-03-06 10:12 ` Neil Armstrong
2026-03-06 10:12 ` Neil Armstrong
2026-03-04 17:10 ` [PATCH 2/7] arm64: dts: exynos: gs101: " Geert Uytterhoeven
2026-03-04 17:10 ` Geert Uytterhoeven
2026-03-04 17:11 ` [PATCH 3/7] arm64: dts: fsl-ls1028a: " Geert Uytterhoeven
2026-03-04 17:11 ` Geert Uytterhoeven
2026-03-04 17:11 ` [PATCH 4/7] arm64: dts: freescale: imx: " Geert Uytterhoeven
2026-03-04 17:11 ` Geert Uytterhoeven
2026-03-04 17:11 ` [PATCH 5/7] arm64: dts: intel: agilex5: " Geert Uytterhoeven
2026-03-04 17:11 ` Geert Uytterhoeven
2026-03-11 2:12 ` Dinh Nguyen
2026-03-11 2:12 ` Dinh Nguyen
2026-03-04 17:11 ` [PATCH 6/7] arm64: tegra: " Geert Uytterhoeven
2026-03-04 17:11 ` Geert Uytterhoeven
2026-03-04 17:11 ` [PATCH 7/7] arm64: dts: qcom: " Geert Uytterhoeven
2026-03-04 17:11 ` Geert Uytterhoeven
2026-03-05 10:02 ` Konrad Dybcio
2026-03-05 10:02 ` Konrad Dybcio
2026-03-05 9:33 ` [PATCH 0/7] arm64: dts: " Konrad Dybcio
2026-03-05 9:33 ` Konrad Dybcio
2026-03-05 9:55 ` Geert Uytterhoeven
2026-03-05 9:55 ` Geert Uytterhoeven
2026-03-05 10:02 ` Konrad Dybcio
2026-03-05 10:02 ` Konrad Dybcio
2026-03-05 11:03 ` Marc Zyngier [this message]
2026-03-05 11:03 ` Marc Zyngier
2026-03-24 14:56 ` (subset) " Frank Li
2026-03-24 14:56 ` Frank Li
2026-03-26 3:19 ` Bjorn Andersson
2026-03-26 3:19 ` Bjorn Andersson
2026-03-26 8:58 ` Neil Armstrong
2026-03-26 8:58 ` Neil Armstrong
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=86qzpy7d3e.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=dinguyen@kernel.org \
--cc=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=imx@lists.linux.dev \
--cc=jbrunet@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=peter.griffin@linaro.org \
--cc=s.hauer@pengutronix.de \
--cc=treding@nvidia.com \
--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 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.