From: David Daney <ddaney.cavm@gmail.com>
To: Alexander Sverdlin <alexander.sverdlin@nsn.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] Make Octeon GPIO IRQ chip CPU hotplug-aware
Date: Thu, 23 Oct 2014 08:59:08 -0700 [thread overview]
Message-ID: <544925CC.7040801@gmail.com> (raw)
In-Reply-To: <544908B8.7050109@nsn.com>
On 10/23/2014 06:55 AM, Alexander Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@nsn.com>
>
> Make Octeon GPIO IRQ chip CPU hotplug-aware
>
> Seems that irq_cpu_offline callbacks were forgotten in v1 and v2 CIU
> GPIO chips. There is such a callback for octeon_irq_chip_ciu2_gpio,
> covering CIU2 chips. Without this callback GPIO IRQs are not being migrated
> during core offlining. Patch is tested on Octeon II.
>
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@nsn.com>
Acked-by: David Daney <david.daney@cavium.com>
Ralf, please apply.
Thanks,
David Daney
>
> ---
> --- a/arch/mips/cavium-octeon/octeon-irq.c
> +++ b/arch/mips/cavium-octeon/octeon-irq.c
> @@ -809,6 +809,7 @@ static struct irq_chip octeon_irq_chip_ciu_gpio_v2 = {
> .irq_set_type = octeon_irq_ciu_gpio_set_type,
> #ifdef CONFIG_SMP
> .irq_set_affinity = octeon_irq_ciu_set_affinity_v2,
> + .irq_cpu_offline = octeon_irq_cpu_offline_ciu,
> #endif
> .flags = IRQCHIP_SET_TYPE_MASKED,
> };
> @@ -823,6 +824,7 @@ static struct irq_chip octeon_irq_chip_ciu_gpio = {
> .irq_set_type = octeon_irq_ciu_gpio_set_type,
> #ifdef CONFIG_SMP
> .irq_set_affinity = octeon_irq_ciu_set_affinity,
> + .irq_cpu_offline = octeon_irq_cpu_offline_ciu,
> #endif
> .flags = IRQCHIP_SET_TYPE_MASKED,
> };
>
>
>
next prev parent reply other threads:[~2014-10-23 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 13:55 [PATCH] Make Octeon GPIO IRQ chip CPU hotplug-aware Alexander Sverdlin
2014-10-23 15:59 ` David Daney [this message]
2014-10-23 16:41 ` Ralf Baechle
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=544925CC.7040801@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=alexander.sverdlin@nsn.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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