* [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
@ 2026-07-25 21:57 Rosen Penev
2026-07-25 22:00 ` sashiko-bot
0 siblings, 1 reply; 3+ messages in thread
From: Rosen Penev @ 2026-07-25 21:57 UTC (permalink / raw)
To: devicetree
Cc: Florian Fainelli, Hauke Mehrtens, Rafał Miłecki,
Broadcom internal kernel review list, Rob Herring,
Krzysztof Kozlowski, Conor Dooley,
moderated list:BROADCOM BCM5301X ARM ARCHITECTURE, open list
PCIe controller 2 has interrupts 0-4 mapping to GIC SPI 138-142. The
mapping for interrupt 1 was incorrectly set to 138 due to a copy-paste
error. Fix it to 139.
Assisted-by: opencode:big-pickle
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
arch/arm/boot/dts/broadcom/bcm-ns.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/broadcom/bcm-ns.dtsi b/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
index 392a25713669..bd52de0faa3e 100644
--- a/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
+++ b/arch/arm/boot/dts/broadcom/bcm-ns.dtsi
@@ -141,7 +141,7 @@ axi@18000000 {
/* PCIe Controller 2 */
<0x00014000 0 &gic GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>,
- <0x00014000 1 &gic GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>,
+ <0x00014000 1 &gic GIC_SPI 139 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 2 &gic GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 3 &gic GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 4 &gic GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>,
--
2.55.0
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
2026-07-25 21:57 [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt Rosen Penev
@ 2026-07-25 22:00 ` sashiko-bot
2026-07-25 22:04 ` Rosen Penev
0 siblings, 1 reply; 3+ messages in thread
From: sashiko-bot @ 2026-07-25 22:00 UTC (permalink / raw)
To: Rosen Penev; +Cc: conor+dt, robh, devicetree
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The commit message inaccurately claims that PCIe controller 2 has interrupts 0-4 mapping to GIC SPI 138-142, omitting the mapping for interrupt 5 to GIC SPI 143.
--
--- Patch [1]: [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt ---
commit 61d1b598a171b93e277ba55c095b09aad8291a33
Author: Rosen Penev <rosenp@gmail.com>
ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
This commit corrects the interrupt mapping for PCIe controller 2 in the
device tree. It updates interrupt 1 to map to GIC SPI 139, fixing a
copy-paste error where it was previously mapped to 138.
> PCIe controller 2 has interrupts 0-4 mapping to GIC SPI 138-142. The
> mapping for interrupt 1 was incorrectly set to 138 due to a copy-paste
> error. Fix it to 139.
[Severity: Medium]
Is this description accurate regarding the number of mapped interrupts?
Looking at arch/arm/boot/dts/broadcom/bcm-ns.dtsi, the device tree explicitly
maps interrupts 0 through 5 for PCIe controller 2:
/* PCIe Controller 2 */
<0x00014000 0 &gic GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 1 &gic GIC_SPI 139 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 2 &gic GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 3 &gic GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 4 &gic GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>,
<0x00014000 5 &gic GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>,
Could the commit message be updated to mention that interrupts 0-5 map to
GIC SPI 138-143?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260725215722.9323-1-rosenp@gmail.com?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
2026-07-25 22:00 ` sashiko-bot
@ 2026-07-25 22:04 ` Rosen Penev
0 siblings, 0 replies; 3+ messages in thread
From: Rosen Penev @ 2026-07-25 22:04 UTC (permalink / raw)
To: sashiko-reviews; +Cc: conor+dt, robh, devicetree
On Sat, Jul 25, 2026 at 3:00 PM <sashiko-bot@kernel.org> wrote:
>
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The commit message inaccurately claims that PCIe controller 2 has interrupts 0-4 mapping to GIC SPI 138-142, omitting the mapping for interrupt 5 to GIC SPI 143.
Quite pedantic.
> --
>
> --- Patch [1]: [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt ---
> commit 61d1b598a171b93e277ba55c095b09aad8291a33
> Author: Rosen Penev <rosenp@gmail.com>
>
> ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt
>
> This commit corrects the interrupt mapping for PCIe controller 2 in the
> device tree. It updates interrupt 1 to map to GIC SPI 139, fixing a
> copy-paste error where it was previously mapped to 138.
>
> > PCIe controller 2 has interrupts 0-4 mapping to GIC SPI 138-142. The
> > mapping for interrupt 1 was incorrectly set to 138 due to a copy-paste
> > error. Fix it to 139.
>
> [Severity: Medium]
> Is this description accurate regarding the number of mapped interrupts?
>
> Looking at arch/arm/boot/dts/broadcom/bcm-ns.dtsi, the device tree explicitly
> maps interrupts 0 through 5 for PCIe controller 2:
>
> /* PCIe Controller 2 */
> <0x00014000 0 &gic GIC_SPI 138 IRQ_TYPE_LEVEL_HIGH>,
> <0x00014000 1 &gic GIC_SPI 139 IRQ_TYPE_LEVEL_HIGH>,
> <0x00014000 2 &gic GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>,
> <0x00014000 3 &gic GIC_SPI 141 IRQ_TYPE_LEVEL_HIGH>,
> <0x00014000 4 &gic GIC_SPI 142 IRQ_TYPE_LEVEL_HIGH>,
> <0x00014000 5 &gic GIC_SPI 143 IRQ_TYPE_LEVEL_HIGH>,
>
> Could the commit message be updated to mention that interrupts 0-5 map to
> GIC SPI 138-143?
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260725215722.9323-1-rosenp@gmail.com?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-07-25 22:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-25 21:57 [PATCH] ARM: dts: BCM5301X: fix PCIe controller 2 second interrupt Rosen Penev
2026-07-25 22:00 ` sashiko-bot
2026-07-25 22:04 ` Rosen Penev
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.