From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 4/4] irqchip: Add bcm2836 interrupt controller for Raspberry Pi 2.
Date: Sun, 26 Jul 2015 11:52:52 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1507261150500.18576@nanos> (raw)
In-Reply-To: <1436837718-956-5-git-send-email-eric@anholt.net>
On Mon, 13 Jul 2015, Eric Anholt wrote:
> +static void
> +bcm2836_arm_irqchip_smp_init(void)
> +{
> +#ifdef CONFIG_SMP
> + int i;
> +
> + /* unmask IPIs */
> + for_each_possible_cpu(i) {
> + bcm2836_arm_irqchip_unmask_per_cpu_irq(
> + LOCAL_MAILBOX_INT_CONTROL0, 0, i);
Do you really want to enable these interrupts on all possible cpus? Why so?
Shouldn't that be done at the point where a hotplugged CPU is starting ?
Thanks,
tglx
next prev parent reply other threads:[~2015-07-26 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 1:35 Raspberry Pi 2 interrupt controller support (v2) Second round Eric Anholt
2015-07-14 1:35 ` [PATCH v2 1/4] irqchip: bcm2835: Refactor handle_IRQ() calls out of MAKE_HWIRQ Eric Anholt
2015-07-14 1:35 ` [PATCH v2 2/4] irqchip: bcm2835: If a parent interrupt is registered, chain from it Eric Anholt
2015-07-22 2:08 ` Stephen Warren
2015-07-22 18:17 ` Eric Anholt
2015-07-24 4:13 ` Stephen Warren
2015-07-14 1:35 ` [PATCH v2 3/4] irqchip: Add documentation for the bcm2836 interrupt controller Eric Anholt
2015-07-14 1:35 ` [PATCH v2 4/4] irqchip: Add bcm2836 interrupt controller for Raspberry Pi 2 Eric Anholt
2015-07-22 2:09 ` Stephen Warren
2015-07-22 18:02 ` Eric Anholt
2015-07-26 9:52 ` Thomas Gleixner [this message]
2015-07-27 18:42 ` [PATCH] irq-bcm2836: Move SMP boot to the irqchip code Eric Anholt
2015-07-27 18:46 ` Florian Fainelli
2015-07-27 20:09 ` [PATCH] irqchip: bcm2836: Use a CPU notifier enable IPIs Eric Anholt
2015-08-02 10:22 ` Thomas Gleixner
2015-08-03 23:23 ` Eric Anholt
2015-08-04 7:14 ` Thomas Gleixner
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=alpine.DEB.2.11.1507261150500.18576@nanos \
--to=tglx@linutronix.de \
--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).