[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1508040913490.3959@nanos>
Date: Tue, 4 Aug 2015 09:14:34 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Eric Anholt <eric@...olt.net>
cc: linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Stephen Warren <swarren@...dotorg.org>,
Lee Jones <lee@...nel.org>, devicetree@...r.kernel.org,
Jason Cooper <jason@...edaemon.net>
Subject: Re: [PATCH] irqchip: bcm2836: Use a CPU notifier enable IPIs.
On Mon, 3 Aug 2015, Eric Anholt wrote:
> Thomas Gleixner <tglx@...utronix.de> writes:
>
> > On Mon, 27 Jul 2015, Eric Anholt wrote:
> >> +/* Unmasks the IPI on the CPU wen it's first brought online. */
> >
> > when
> >
> >> +static int bcm2836_arm_irqchip_cpu_notify(struct notifier_block *nfb,
> >> + unsigned long action, void *hcpu)
> >> +{
> >> + unsigned int cpu = (unsigned long)hcpu;
> >> + unsigned int int_reg = LOCAL_MAILBOX_INT_CONTROL0;
> >> + unsigned int mailbox = 0;
> >> +
> >> + if (action == CPU_STARTING || action == CPU_STARTING_FROZEN)
> >> + bcm2836_arm_irqchip_unmask_per_cpu_irq(int_reg, mailbox, cpu);
> >
> > Shouldn't you mask the irq on CPU_DYING?
>
> I was just following what other drivers were doing. Is CPU_DYING the
> only thing that needs masking?
CPPU_DYING is the counterpart of CPU_STARTING. It's called from the
CPU which goes down.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists