From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: vexpress: Add interrupt-affinity
Date: Fri, 01 May 2015 14:44:45 +0100 [thread overview]
Message-ID: <5543834D.6040506@arm.com> (raw)
In-Reply-To: <20150430175541.GL15254@pengutronix.de>
On 30/04/15 18:55, Robert Schwebel wrote:
> On Thu, Apr 30, 2015 at 07:54:08PM +0200, Robert Schwebel wrote:
>> Without this property, we get this boot warning:
>>
>> [ 0.459361] CPU PMU: Failed to parse <no-node>/interrupt-affinity[0]
>>
>> Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
May be you can also mention the commit introducing the change in the log
something like:
"
Commit 9fd85eb502a7 ("ARM: pmu: add support for interrupt-affinity
property") added optional optional "interrupt-affinity" property, to
specify 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 add interrupt-affinity to the PMU node in CA9x4 device tree.
"
Otherwise:
Acked-by: Sudeep Holla <sudeep.holla@arm.com>
>
> However, with this patch applied, the messages above disappear, but I
> still get this:
>
> [ 0.495280] CPU PMU: Failed to find logical CPU for cpu
>
> on a kernel configured with CONFIG_SMP=n. nr_cpu_ids is 1 there, while
> the loop still loops over all available cores. Ths makes the logic fail.
This is a different issue. You must also see warning from devtree.c when
parsing CPUs complaining about more CPU nodes found in DT. IIUC the
functionality still works fine.
Regards,
Sudeep
prev parent reply other threads:[~2015-05-01 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 17:54 [PATCH 2/2] ARM: vexpress: Add interrupt-affinity Robert Schwebel
2015-04-30 17:55 ` Robert Schwebel
2015-05-01 13:44 ` Sudeep Holla [this message]
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=5543834D.6040506@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;
as well as URLs for NNTP newsgroup(s).