Thread (1 message) 1 message, 1 author, 2021-12-08

Re: [PATCH v5 08/10] irqchip: Add Sunplus SP7021 interrupt controller driver

From: Marc Zyngier <maz@kernel.org>
Date: 2021-12-08 16:02:24
Also in: linux-clk, linux-devicetree, lkml

On Wed, 08 Dec 2021 09:28:42 +0000,
"qinjian[覃健]" [off-list ref] wrote:
quoted
-----Original Message-----
From: Marc Zyngier <maz@kernel.org>
Sent: Wednesday, December 8, 2021 3:45 PM
To: qinjian[覃健] <qinjian@cqplus1.com>
Cc: robh+dt@kernel.org; mturquette@baylibre.com; sboyd@kernel.org; tglx@linutronix.de; p.zabel@pengutronix.de;
linux@armlinux.org.uk; broonie@kernel.org; arnd@arndb.de; linux-arm-kernel@lists.infradead.org; devicetree@vger.kernel.org; linux-
kernel@vger.kernel.org; linux-clk@vger.kernel.org; Wells Lu 呂芳騰 [off-list ref]
Subject: Re: [PATCH v5 08/10] irqchip: Add Sunplus SP7021 interrupt controller driver

On 2021-12-08 07:15, qinjian[覃健] wrote:
quoted
quoted
quoted
+void sp_intc_set_ext(u32 hwirq, int ext_num)
+{
+	sp_intc_assign_bit(hwirq, REG_INTR_PRIORITY, !ext_num);
+}
+EXPORT_SYMBOL_GPL(sp_intc_set_ext);
No way. We don't export random symbols without a good justification,
and you didn't give any.
This function called by SP7021 display driver to decide DISPLAY_IRQ
routing to which parent irq (EXT_INT0 or EXT_INT1).
Based on what? How can a display driver decide which parent is
appropriate? What improvement does this bring?
In default, all IRQ routing to EXT_INT0, which processed by CPU0
Some device's IRQ need low latency, like display, so routing
DISPLAY_IRQ to EXT_INT1, which processed by CPU1 (set
/proc/irq/<EXT_INT1>/smp_affinity_list)
Why would that have a lower latency? What if CPU1 is busy with
interrupts disabled most of the time? How does the display driver
finds out what is better?

And if you really wanted a lower latency, why route the interrupt via
a secondary interrupt controller, instead of attaching it directly to
the upstream GIC?

I really don't think this is an acceptable thing to do. Configure the
interrupt route statically if you want, but we're not exposing this
sort of SoC-specific API to other drivers.

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help