* [PATCH 1/3] dt-bindings: interrupt-controller: econet,en751221-intc: Allow up to 6 parent interrupts
2026-11-15 19:26 [PATCH 0/3] irqchip/econet-en751221: Deliver odd interrupts without VEIC Akshat Singh via B4 Relay
@ 2026-11-15 19:26 ` Akshat Singh via B4 Relay
2026-11-15 19:26 ` [PATCH 2/3] irqchip/econet-en751221: Chain the handler to all " Akshat Singh via B4 Relay
2026-11-15 19:26 ` [PATCH 3/3] mips: dts: Connect the EcoNet EN751221 intc to IP2-IP6 Akshat Singh via B4 Relay
2 siblings, 0 replies; 5+ messages in thread
From: Akshat Singh via B4 Relay @ 2026-11-15 19:26 UTC (permalink / raw)
To: Caleb James DeLisle, Thomas Gleixner, Radu Rendec, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Thomas Bogendoerfer
Cc: linux-mips, linux-kernel, devicetree, Akshat Singh
From: Akshat Singh <automobilehacks@gmail.com>
The controller is not connected to its parent through a single
interrupt line: it presents the number of the pending interrupt plus
one, in binary, on the CPU interrupt lines IP2-IP7. A CPU in VEIC mode
takes that number as the vector, but without VEIC each line is a
separate interrupt, and the controller has to be chained to all the
lines that can carry it.
Allow listing up to six parent interrupts, one per line.
Signed-off-by: Akshat Singh <automobilehacks@gmail.com>
---
.../bindings/interrupt-controller/econet,en751221-intc.yaml | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/econet,en751221-intc.yaml b/Documentation/devicetree/bindings/interrupt-controller/econet,en751221-intc.yaml
index 44c09785e..098fdeaa3 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/econet,en751221-intc.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/econet,en751221-intc.yaml
@@ -34,8 +34,13 @@ properties:
interrupt-controller: true
interrupts:
- maxItems: 1
- description: Interrupt line connecting this controller to its parent.
+ minItems: 1
+ maxItems: 6
+ description:
+ CPU interrupt lines connecting this controller to its parent. The
+ controller presents the number of the pending interrupt plus one, in
+ binary, on the CPU interrupt lines IP2-IP7, so it can be connected to
+ up to six of them.
econet,shadow-interrupts:
$ref: /schemas/types.yaml#/definitions/uint32-matrix
--
2.43.0
^ permalink raw reply [flat|nested] 5+ messages in thread* [PATCH 2/3] irqchip/econet-en751221: Chain the handler to all parent interrupts
2026-11-15 19:26 [PATCH 0/3] irqchip/econet-en751221: Deliver odd interrupts without VEIC Akshat Singh via B4 Relay
2026-11-15 19:26 ` [PATCH 1/3] dt-bindings: interrupt-controller: econet,en751221-intc: Allow up to 6 parent interrupts Akshat Singh via B4 Relay
@ 2026-11-15 19:26 ` Akshat Singh via B4 Relay
2026-11-17 11:09 ` Caleb James DeLisle
2026-11-15 19:26 ` [PATCH 3/3] mips: dts: Connect the EcoNet EN751221 intc to IP2-IP6 Akshat Singh via B4 Relay
2 siblings, 1 reply; 5+ messages in thread
From: Akshat Singh via B4 Relay @ 2026-11-15 19:26 UTC (permalink / raw)
To: Caleb James DeLisle, Thomas Gleixner, Radu Rendec, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Thomas Bogendoerfer
Cc: linux-mips, linux-kernel, devicetree, Akshat Singh
From: Akshat Singh <automobilehacks@gmail.com>
The EN751221 interrupt controller does not drive one CPU interrupt line
per source. It presents the number of the pending interrupt plus one, in
binary, on the CPU interrupt lines IP2-IP7. In VEIC mode the CPU takes
that number as the vector, but without VEIC the driver chains its handler
to the first parent interrupt only, IP2 in the existing device trees. An
odd-numbered interrupt then never interrupts the CPU by itself: it is
handled only when an even-numbered one happens to run the handler, which
on an idle system is the next timer interrupt. That covers the frame
engine's QDMA (21), xHCI (17) and the first PCIe port (23).
On a Nokia G-140W-C, whose 34Kc does not report VEIC, this delayed
received packets by up to 10 ms, and ping round-trip times to the device
cycled through 1-11 ms.
Without VEIC, chain the handler to every parent interrupt listed in the
device tree. One interrupt usually raises several lines, so the later
runs of the handler find nothing pending; don't count those as spurious.
VEIC mode is unchanged.
Signed-off-by: Akshat Singh <automobilehacks@gmail.com>
---
drivers/irqchip/irq-econet-en751221.c | 33 ++++++++++++++++++++++++++++++---
1 file changed, 30 insertions(+), 3 deletions(-)
diff --git a/drivers/irqchip/irq-econet-en751221.c b/drivers/irqchip/irq-econet-en751221.c
index 2ca5d9018..5930c67c3 100644
--- a/drivers/irqchip/irq-econet-en751221.c
+++ b/drivers/irqchip/irq-econet-en751221.c
@@ -18,6 +18,15 @@
* When VPE#1 requests IRQ 30, the driver manipulates the mask bit for IRQ 29,
* telling the hardware to mask VPE#1's view of IRQ 30.
*
+ * The controller does not give each source its own CPU interrupt line. It
+ * presents the number of the pending interrupt plus one, in binary, on the
+ * CPU interrupt lines IP2-IP7, which a CPU in VEIC mode takes as the vector.
+ * Without VEIC, IRQ 21, for example, shows up as 22 = 0b010110 on IP3, IP4
+ * and IP6, so the controller is chained to every CPU line listed in its
+ * "interrupts" property. Chained to IP2 alone, it would see the odd-numbered
+ * IRQs only when an even-numbered one, such as the timer, happened to run
+ * the handler.
+ *
* Copyright (C) 2025 Caleb James DeLisle <cjd@cjdns.fr>
*/
@@ -145,9 +154,12 @@ static void econet_intc_from_parent(struct irq_desc *desc)
pending0 = ioread32(econet_intc.membase + REG_PENDING0);
pending1 = ioread32(econet_intc.membase + REG_PENDING1);
- if (unlikely(!(pending0 | pending1))) {
- spurious_interrupt();
- } else {
+ /*
+ * An interrupt usually raises several CPU lines. It is handled when
+ * the first of them runs this function, and the others find nothing
+ * pending.
+ */
+ if (pending0 | pending1) {
domain = irq_desc_get_handler_data(desc);
econet_intc_handle_pending(domain, pending0, 0);
econet_intc_handle_pending(domain, pending1, 32);
@@ -461,7 +473,22 @@ static int __init econet_intc_of_init(struct device_node *node, struct device_no
if (ret)
return ret;
} else {
+ int nr_parents = of_irq_count(node);
+
irq_set_chained_handler_and_data(irq, econet_intc_from_parent, domain);
+
+ for (int i = 1; i < nr_parents; i++) {
+ int parent = irq_of_parse_and_map(node, i);
+
+ if (!parent) {
+ pr_warn("%pOF: DT: Failed to get IRQ %d from 'interrupts'\n",
+ node, i);
+ continue;
+ }
+
+ irq_set_chained_handler_and_data(parent, econet_intc_from_parent,
+ domain);
+ }
}
econet_intc.domain = domain;
--
2.43.0
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH 2/3] irqchip/econet-en751221: Chain the handler to all parent interrupts
2026-11-15 19:26 ` [PATCH 2/3] irqchip/econet-en751221: Chain the handler to all " Akshat Singh via B4 Relay
@ 2026-11-17 11:09 ` Caleb James DeLisle
0 siblings, 0 replies; 5+ messages in thread
From: Caleb James DeLisle @ 2026-11-17 11:09 UTC (permalink / raw)
To: automobilehacks, Thomas Gleixner, Radu Rendec, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Thomas Bogendoerfer
Cc: linux-mips, linux-kernel, devicetree
On 15/11/2026 20:26, Akshat Singh via B4 Relay wrote:
> From: Akshat Singh <automobilehacks@gmail.com>
>
> The EN751221 interrupt controller does not drive one CPU interrupt line
> per source. It presents the number of the pending interrupt plus one, in
> binary, on the CPU interrupt lines IP2-IP7. In VEIC mode the CPU takes
> that number as the vector, but without VEIC the driver chains its handler
> to the first parent interrupt only, IP2 in the existing device trees. An
> odd-numbered interrupt then never interrupts the CPU by itself: it is
> handled only when an even-numbered one happens to run the handler, which
> on an idle system is the next timer interrupt. That covers the frame
> engine's QDMA (21), xHCI (17) and the first PCIe port (23).
>
> On a Nokia G-140W-C, whose 34Kc does not report VEIC, this delayed
> received packets by up to 10 ms, and ping round-trip times to the device
> cycled through 1-11 ms.
>
> Without VEIC, chain the handler to every parent interrupt listed in the
> device tree. One interrupt usually raises several lines, so the later
> runs of the handler find nothing pending; don't count those as spurious.
>
> VEIC mode is unchanged.
>
> Signed-off-by: Akshat Singh <automobilehacks@gmail.com>
I tested and confirm that hardware indeed behaves as described.
Tested-by: Caleb James DeLisle <cjd@cjdns.fr>
> ---
> drivers/irqchip/irq-econet-en751221.c | 33 ++++++++++++++++++++++++++++++---
> 1 file changed, 30 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/irqchip/irq-econet-en751221.c b/drivers/irqchip/irq-econet-en751221.c
> index 2ca5d9018..5930c67c3 100644
> --- a/drivers/irqchip/irq-econet-en751221.c
> +++ b/drivers/irqchip/irq-econet-en751221.c
> @@ -18,6 +18,15 @@
> * When VPE#1 requests IRQ 30, the driver manipulates the mask bit for IRQ 29,
> * telling the hardware to mask VPE#1's view of IRQ 30.
> *
> + * The controller does not give each source its own CPU interrupt line. It
> + * presents the number of the pending interrupt plus one, in binary, on the
> + * CPU interrupt lines IP2-IP7, which a CPU in VEIC mode takes as the vector.
> + * Without VEIC, IRQ 21, for example, shows up as 22 = 0b010110 on IP3, IP4
> + * and IP6, so the controller is chained to every CPU line listed in its
> + * "interrupts" property. Chained to IP2 alone, it would see the odd-numbered
> + * IRQs only when an even-numbered one, such as the timer, happened to run
> + * the handler.
> + *
> * Copyright (C) 2025 Caleb James DeLisle <cjd@cjdns.fr>
> */
>
> @@ -145,9 +154,12 @@ static void econet_intc_from_parent(struct irq_desc *desc)
> pending0 = ioread32(econet_intc.membase + REG_PENDING0);
> pending1 = ioread32(econet_intc.membase + REG_PENDING1);
>
> - if (unlikely(!(pending0 | pending1))) {
> - spurious_interrupt();
> - } else {
> + /*
> + * An interrupt usually raises several CPU lines. It is handled when
> + * the first of them runs this function, and the others find nothing
> + * pending.
> + */
> + if (pending0 | pending1) {
> domain = irq_desc_get_handler_data(desc);
> econet_intc_handle_pending(domain, pending0, 0);
> econet_intc_handle_pending(domain, pending1, 32);
> @@ -461,7 +473,22 @@ static int __init econet_intc_of_init(struct device_node *node, struct device_no
> if (ret)
> return ret;
> } else {
> + int nr_parents = of_irq_count(node);
> +
> irq_set_chained_handler_and_data(irq, econet_intc_from_parent, domain);
> +
> + for (int i = 1; i < nr_parents; i++) {
> + int parent = irq_of_parse_and_map(node, i);
> +
> + if (!parent) {
> + pr_warn("%pOF: DT: Failed to get IRQ %d from 'interrupts'\n",
> + node, i);
> + continue;
> + }
> +
> + irq_set_chained_handler_and_data(parent, econet_intc_from_parent,
> + domain);
> + }
> }
>
> econet_intc.domain = domain;
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH 3/3] mips: dts: Connect the EcoNet EN751221 intc to IP2-IP6
2026-11-15 19:26 [PATCH 0/3] irqchip/econet-en751221: Deliver odd interrupts without VEIC Akshat Singh via B4 Relay
2026-11-15 19:26 ` [PATCH 1/3] dt-bindings: interrupt-controller: econet,en751221-intc: Allow up to 6 parent interrupts Akshat Singh via B4 Relay
2026-11-15 19:26 ` [PATCH 2/3] irqchip/econet-en751221: Chain the handler to all " Akshat Singh via B4 Relay
@ 2026-11-15 19:26 ` Akshat Singh via B4 Relay
2 siblings, 0 replies; 5+ messages in thread
From: Akshat Singh via B4 Relay @ 2026-11-15 19:26 UTC (permalink / raw)
To: Caleb James DeLisle, Thomas Gleixner, Radu Rendec, Rob Herring,
Krzysztof Kozlowski, Conor Dooley, Thomas Bogendoerfer
Cc: linux-mips, linux-kernel, devicetree, Akshat Singh
From: Akshat Singh <automobilehacks@gmail.com>
The interrupt controller presents the number of the pending interrupt
plus one, in binary, on the CPU interrupt lines IP2-IP7. Without VEIC,
chaining it to IP2 alone leaves the odd-numbered interrupts, such as the
QDMA, xHCI and the first PCIe port, waiting for an even-numbered one to
run the handler.
List IP2-IP6. IP7 is left out: the CPU can also signal its own timer on
it, and only hwirq 31, which is unused, needs it.
Signed-off-by: Akshat Singh <automobilehacks@gmail.com>
---
arch/mips/boot/dts/econet/en751221.dtsi | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/mips/boot/dts/econet/en751221.dtsi b/arch/mips/boot/dts/econet/en751221.dtsi
index 57ae84a8a..5e3f626b5 100644
--- a/arch/mips/boot/dts/econet/en751221.dtsi
+++ b/arch/mips/boot/dts/econet/en751221.dtsi
@@ -66,7 +66,12 @@ intc: interrupt-controller@1fb40000 {
compatible = "econet,en751221-intc";
reg = <0x1fb40000 0x100>;
interrupt-parent = <&cpuintc>;
- interrupts = <2>;
+ /*
+ * The number of the pending interrupt plus one is presented in
+ * binary on IP2-IP7. IP7 is left out: the CPU can also signal its
+ * own timer on it, and only hwirq 31, which is unused, needs it.
+ */
+ interrupts = <2>, <3>, <4>, <5>, <6>;
interrupt-controller;
#interrupt-cells = <1>;
--
2.43.0
^ permalink raw reply [flat|nested] 5+ messages in thread