From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: vexpress/tc2: Add interrupt-affinity to the PMU node
Date: Thu, 7 May 2015 15:45:05 +0100 [thread overview]
Message-ID: <1431009905-29265-5-git-send-email-sudeep.holla@arm.com> (raw)
In-Reply-To: <1431009905-29265-1-git-send-email-sudeep.holla@arm.com>
Commit 9fd85eb502a7 ("ARM: pmu: add support for interrupt-affinity
property") added an optional "interrupt-affinity" property, to specify
the CPU affinity for each SPI listed in the interrupts property.
Without this property, we get this boot warning:
CPU PMU: Failed to parse <no-node>/interrupt-affinity[0]
This patch adds interrupt-affinity to the PMU node in the
vexpress-ca15_a7(a.k.a TC2) device tree.
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
---
arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts b/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
index 7a2aeacd62c0..107395c32d82 100644
--- a/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
+++ b/arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts
@@ -191,6 +191,7 @@
compatible = "arm,cortex-a15-pmu";
interrupts = <0 68 4>,
<0 69 4>;
+ interrupt-affinity = <&cpu0>, <&cpu1>;
};
oscclk6a: oscclk6a {
--
1.9.1
next prev parent reply other threads:[~2015-05-07 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 14:45 [PATCH 0/4] ARM/ARM64: vexpress: fixes for v4.1 Sudeep Holla
2015-05-07 14:45 ` [PATCH 1/4] ARM64: juno: add sp810 support and fix sp804 clock frequency Sudeep Holla
2015-05-07 14:45 ` [PATCH 2/4] ARM: vexpress/ca9: Add unified-cache property to l2 cache node Sudeep Holla
2015-05-07 14:45 ` [PATCH 3/4] ARM: vexpress/ca9: Add interrupt-affinity to the PMU node Sudeep Holla
2015-05-07 14:45 ` Sudeep Holla [this message]
2015-05-12 13:52 ` [PATCH 0/4] ARM/ARM64: vexpress: fixes for v4.1 Sudeep Holla
2015-05-12 13:55 ` Sudeep Holla
2015-05-12 14:40 ` Arnd Bergmann
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=1431009905-29265-5-git-send-email-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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