From: sashiko-bot@kernel.org
To: "Markus Stockhausen" <markus.stockhausen@gmx.de>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: interrupt-controller: realtek,rtl-intc: Allow 2 interrupt cells
Date: Fri, 05 Jun 2026 21:25:33 +0000 [thread overview]
Message-ID: <20260605212533.75D231F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260605211646.2101652-2-markus.stockhausen@gmx.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The cell-count property `#interrupt-cells` uses an `enum` constraint instead of a `const` constraint, violating dt-bindings subsystem rules.
--
commit 11a7c1b034a74e6212dca3ea81cd1ec7e513c49c
Author: Markus Stockhausen <markus.stockhausen@gmx.de>
dt-bindings: interrupt-controller: realtek,rtl-intc: Allow 2 interrupt cells
This commit updates the #interrupt-cells property to accept either 1 or 2
cells to support explicit hardware interrupt routing to multiple parent CPU
interrupt lines.
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/realtek,rtl-intc.yaml b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtl-intc.yaml
> --- a/Documentation/devicetree/bindings/interrupt-controller/realtek,rtl-intc.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/realtek,rtl-intc.yaml
> @@ -32,8 +32,9 @@ properties:
>
> "#interrupt-cells":
> description:
> - SoC interrupt line index.
> - const: 1
> + First cell is the SoC interrupt line index. Optional second cell
> + specifies the parent interrupt index to route to.
> + enum: [1, 2]
[Severity: Medium]
Does this change violate the subsystem requirements for cell-count properties?
The device tree binding subsystem rules require that each cell-count property
must have a const constraint matching the hardware (for example, const: 2).
Changing this constraint to use an enum instead of a const can lead to
incomplete or unreliable schema validation during dt_binding_check, as
downstream node references rely on a fixed cell count constraint to validate
interrupt specifiers properly.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260605211646.2101652-1-markus.stockhausen@gmx.de?part=1
next prev parent reply other threads:[~2026-06-05 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 21:16 [PATCH 0/7] irqchip/irq-realtek-rtl: Add multi parent support Markus Stockhausen
2026-06-05 21:16 ` [PATCH 1/7] dt-bindings: interrupt-controller: realtek,rtl-intc: Allow 2 interrupt cells Markus Stockhausen
2026-06-05 21:25 ` sashiko-bot [this message]
2026-06-05 21:16 ` [PATCH 2/7] irqchip/irq-realtek-rtl: Use helper for parent setup Markus Stockhausen
2026-06-05 21:16 ` [PATCH 3/7] irqchip/irq-realtek-rtl: Add interrupt data structure Markus Stockhausen
2026-06-05 21:16 ` [PATCH 4/7] irqchip/irq-realtek-rtl: Add mask for interrupt handling Markus Stockhausen
2026-06-05 21:16 ` [PATCH 5/7] irqchip/irq-realtek-rtl: Add a select function Markus Stockhausen
2026-06-05 21:16 ` [PATCH 6/7] irqchip/irq-realtek-rtl: Allow shuffled interrupt order Markus Stockhausen
2026-06-05 21:16 ` [PATCH 7/7] irqchip/irq-realtek-rtl: Activate multiple parents Markus Stockhausen
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=20260605212533.75D231F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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