From: Conor Dooley <conor@kernel.org>
To: Yangyu Chen <cyy@cyyself.name>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
Anup Patel <anup.patel@oss.qualcomm.com>,
Samuel Holland <samuel.holland@sifive.com>,
Charles Mirabile <cmirabil@redhat.com>,
Lucas Zampieri <lzampier@redhat.com>,
Thomas Gleixner <tglx@kernel.org>, Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Mason Huo <mason.huo@starfivetech.com>,
Zhang Xincheng <zhangxincheng@ultrarisc.com>,
Charlie Jenkins <charlie@rivosinc.com>,
Marc Zyngier <maz@kernel.org>,
Sia Jee Heng <jeeheng.sia@starfivetech.com>,
Ley Foon Tan <leyfoon.tan@starfivetech.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, Jia Wang <wangjia@ultrarisc.com>
Subject: Re: [PATCH v3 2/2] dt-binding: riscv: Clarify the riscv,ndev meaning in PLIC
Date: Wed, 4 Feb 2026 17:49:47 +0000 [thread overview]
Message-ID: <20260204-cursor-wad-186f59d9c2ab@spud> (raw)
In-Reply-To: <tencent_720A4669773B1EE15EC720869C35C2F0490A@qq.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
On Wed, Feb 04, 2026 at 01:21:48AM +0800, Yangyu Chen wrote:
> In PLIC, interrupt source 0 is reserved and should not be used.
> Therefore, the valid interrupt sources are from 1 to riscv,ndev
> inclusive. This commit updates the documentation to clarify this point.
>
> Signed-off-by: Yangyu Chen <cyy@cyyself.name>
> ---
> .../bindings/interrupt-controller/sifive,plic-1.0.0.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> index 388fc2c620c0..df9578bcac89 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/sifive,plic-1.0.0.yaml
> @@ -109,6 +109,8 @@ properties:
> $ref: /schemas/types.yaml#/definitions/uint32
> description:
> Specifies how many external interrupts are supported by this controller.
> + Note that source 0 is reserved in PLIC, so the valid interrupt sources
> + are 1 to riscv,ndev inclusive.
The trm for mpfs says "in the plic, global interrupt id 0 means 'no
interrupt'". That sounds subtly different to me than "reserved", but
/shrug
I think this could just be truncated to "Valid interrupt sources are
1 to riscv,ndev, inclusive.".
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-02-04 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:17 [PATCH v3 0/2] irqchip/sifive-plic: Fix wrong nr_irqs handling Yangyu Chen
2026-02-03 17:21 ` [PATCH v3 1/2] " Yangyu Chen
2026-02-03 20:40 ` Thomas Gleixner
2026-02-04 4:40 ` Yangyu Chen
2026-02-04 17:46 ` Conor Dooley
2026-02-03 17:21 ` [PATCH v3 2/2] dt-binding: riscv: Clarify the riscv,ndev meaning in PLIC Yangyu Chen
2026-02-04 17:49 ` Conor Dooley [this message]
2026-02-20 4:10 ` [PATCH v3 0/2] irqchip/sifive-plic: Fix wrong nr_irqs handling patchwork-bot+linux-riscv
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=20260204-cursor-wad-186f59d9c2ab@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup.patel@oss.qualcomm.com \
--cc=charlie@rivosinc.com \
--cc=cmirabil@redhat.com \
--cc=conor+dt@kernel.org \
--cc=cyy@cyyself.name \
--cc=devicetree@vger.kernel.org \
--cc=jeeheng.sia@starfivetech.com \
--cc=krzk+dt@kernel.org \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lzampier@redhat.com \
--cc=mason.huo@starfivetech.com \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@kernel.org \
--cc=wangjia@ultrarisc.com \
--cc=zhangxincheng@ultrarisc.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