From: Marc Zyngier <maz@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Thomas Gleixner <tglx@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrupt-controller: arm,gic-v3: Fix EPPI range
Date: Wed, 04 Mar 2026 14:32:47 +0000 [thread overview]
Message-ID: <86y0k77jhs.wl-maz@kernel.org> (raw)
In-Reply-To: <107183629106ad392e17fdf539a3d79873024377.1772632987.git.geert+renesas@glider.be>
On Wed, 04 Mar 2026 14:04:10 +0000,
Geert Uytterhoeven <geert+renesas@glider.be> wrote:
>
> According to the "Arm Generic Interrupt Controller (GIC) Architecture
> Specification, v3 and v3", revision H.b[1], there can be only 64
v3 and v4?
> Extended PPI interrupts.
>
> [1] https://developer.arm.com/documentation/ihi0069/hb/
>
> Fixes: 4b049063e0bcbfd3 ("dt-bindings: interrupt-controller: arm,gic-v3: Describe EPPI range support")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> .../devicetree/bindings/interrupt-controller/arm,gic-v3.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml
> index bfd30aae682bf3f7..360a0643a0b567a4 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,gic-v3.yaml
> @@ -50,7 +50,7 @@ properties:
> The 2nd cell contains the interrupt number for the interrupt type.
> SPI interrupts are in the range [0-987]. PPI interrupts are in the
> range [0-15]. Extended SPI interrupts are in the range [0-1023].
> - Extended PPI interrupts are in the range [0-127].
> + Extended PPI interrupts are in the range [0-63].
>
> The 3rd cell is the flags, encoded as follows:
> bits[3:0] trigger type and level flags.
Duh. Thankfully the code didn't have the same problem... Thanks for
noticing it. With the above fixed:
Brain-farted-by: Marc Zyngier <maz@kernel.org>
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-03-04 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:04 [PATCH] dt-bindings: interrupt-controller: arm,gic-v3: Fix EPPI range Geert Uytterhoeven
2026-03-04 14:32 ` Marc Zyngier [this message]
2026-03-04 15:09 ` 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=86y0k77jhs.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tglx@kernel.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