Thread (17 messages) 17 messages, 4 authors, 2017-02-27

Re: [PATCH 08/11] ARM: dts: Prepare Actions Semi S500 and LeMaker Guitar

From: Mark Rutland <hidden>
Date: 2017-02-15 17:36:25
Also in: linux-arm-kernel, lkml

On Wed, Feb 15, 2017 at 06:28:31PM +0100, Andreas Färber wrote:
quoted hunk ↗ jump to hunk
Hi Mark,

Am 15.02.2017 um 18:07 schrieb Mark Rutland:
quoted
On Wed, Feb 15, 2017 at 05:55:25PM +0100, Andreas Färber wrote:
quoted
+	arm-pmu {
+		compatible = "arm,cortex-a9-pmu";
+		interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>,
+		             <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>,
+		             <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
+		             <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
+        };
Please add an interrupt-affinity property, as described in
Documentation/devicetree/bindings/arm/pmu.txt
That's not in the vendor tree... My guess is it would be like this then?
diff --git a/arch/arm/boot/dts/s500.dtsi b/arch/arm/boot/dts/s500.dtsi
index ee93984..959c6e3 100644
--- a/arch/arm/boot/dts/s500.dtsi
+++ b/arch/arm/boot/dts/s500.dtsi
@@ -82,7 +82,8 @@
                             <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>,
                             <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
                             <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>;
-        };
+               interrupt-affinity = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>;
+       };
Assuming that's how they're wired up, yes.

You should be able to test this by using perf record in per-cpu mode,
on an application with its affintiy fixed to a particular CPU, and
verifying that overflow interrupts are recevied on the same CPU.

Thanks,
Mark.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help