From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/2] ARM: at91: fix system timer irq issue due to sparse irq support
Date: Thu, 23 Aug 2012 11:57:19 +0200 [thread overview]
Message-ID: <5035FE7F.3000406@atmel.com> (raw)
In-Reply-To: <1344935962-18871-2-git-send-email-ludovic.desroches@atmel.com>
On 08/14/2012 11:19 AM, ludovic.desroches at atmel.com :
> From: Ludovic Desroches <ludovic.desroches@atmel.com>
>
> AT91_ID_SYS as virq is incorrect because of spare irq support which
> introduces NR_IRQS_LEGACY offset.
>
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> Tested-by: Joachim Eastwood <joachim.eastwood@jotron.com>
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
And pushed in at91-fixes branch for 3.6.
Thanks,
> ---
> arch/arm/mach-at91/at91rm9200_time.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-at91/at91rm9200_time.c b/arch/arm/mach-at91/at91rm9200_time.c
> index 104ca40..aaa443b 100644
> --- a/arch/arm/mach-at91/at91rm9200_time.c
> +++ b/arch/arm/mach-at91/at91rm9200_time.c
> @@ -197,7 +197,7 @@ void __init at91rm9200_timer_init(void)
> at91_st_read(AT91_ST_SR);
>
> /* Make IRQs happen for the system timer */
> - setup_irq(AT91_ID_SYS, &at91rm9200_timer_irq);
> + setup_irq(NR_IRQS_LEGACY + AT91_ID_SYS, &at91rm9200_timer_irq);
>
> /* The 32KiHz "Slow Clock" (tick every 30517.58 nanoseconds) is used
> * directly for the clocksource and all clockevents, after adjusting
>
--
Nicolas Ferre
next prev parent reply other threads:[~2012-08-23 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:19 [PATCH v2 0/2] ARM: at91: fix drivers broken because of sparse irq support ludovic.desroches at atmel.com
2012-08-14 9:19 ` [PATCH v2 1/2] ARM: at91: fix system timer irq issue due to " ludovic.desroches at atmel.com
2012-08-23 9:57 ` Nicolas Ferre [this message]
2012-08-14 9:19 ` [PATCH v2 2/2] ARM: at91: fix rtc-at91sam9 " ludovic.desroches at atmel.com
2012-08-23 9:58 ` Nicolas Ferre
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=5035FE7F.3000406@atmel.com \
--to=nicolas.ferre@atmel.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 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.