All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: GIC irq desciptor bug fix
Date: Wed, 08 Dec 2010 00:43:24 +0000	[thread overview]
Message-ID: <4CFED4AC.3040304@fluff.org> (raw)
In-Reply-To: <1291270659-24903-1-git-send-email-cxie4@marvell.com>

On 02/12/10 06:17, Chao at marvell.com wrote:
> From: cxie4 <cxie4@marvell.com>

I think you should have your full name here.

> 
> gic_set_cpu will directly use irq_desc[]. If CONFIG_SPARSE_IRQ is enabled, there is no
> irq_desc[]. So we need use irq_to_desc(irq) to get the descriptor for irq.
> 
> Signed-off-by: cxie4 <cxie4@marvell.com>
> ---
>  arch/arm/common/gic.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/common/gic.c b/arch/arm/common/gic.c
> index 7dfa9a8..6599acb 100644
> --- a/arch/arm/common/gic.c
> +++ b/arch/arm/common/gic.c
> @@ -160,9 +160,15 @@ static int gic_set_cpu(unsigned int irq, const struct cpumask *mask_val)
>  	unsigned int shift = (irq % 4) * 8;
>  	unsigned int cpu = cpumask_first(mask_val);
>  	u32 val;
> +	struct irq_desc *desc;
>  
>  	spin_lock(&irq_controller_lock);
> -	irq_desc[irq].node = cpu;
> +	desc = irq_to_desc(irq);
> +	if (desc == NULL) {
> +		spin_unlock(&irq_controller_lock);
> +		return -EINVAL;
> +	}

Hmm, NULL would be quite a problem, should we BUG() on this
or maybe WARN on it?

> +	desc->node = cpu;
>  	val = readl(reg) & ~(0xff << shift);
>  	val |= 1 << (cpu + shift);
>  	writel(val, reg);

  parent reply	other threads:[~2010-12-08  0:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02  6:17 [PATCH] ARM: GIC irq desciptor bug fix Chao at marvell.com
2010-12-02 11:50 ` Kyungmin Park
2010-12-03 20:54 ` Russell King - ARM Linux
2010-12-08  0:43 ` Ben Dooks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-12-03  1:12 Chao Xie

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=4CFED4AC.3040304@fluff.org \
    --to=ben-linux@fluff.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.