From: magnus.damm@gmail.com (Magnus Damm)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add support for 10 hardirq bits
Date: Fri, 30 Apr 2010 13:02:04 +0900 [thread overview]
Message-ID: <u2yaec7e5c31004292102rd561d7detc73e9fd2a5570ab0@mail.gmail.com> (raw)
In-Reply-To: <20100310111749.18521.9002.sendpatchset@t400s>
On Wed, Mar 10, 2010 at 8:17 PM, Magnus Damm <magnus.damm@gmail.com> wrote:
> From: Magnus Damm <damm@opensource.se>
>
> This patch adds support for 10 hardirq bits to
> the ARM architecture. Needed by the SH-Mobile
> ARM processor sh7372 that has more than 512 IRQs.
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
> ---
>
> ?arch/arm/include/asm/hardirq.h | ? ?4 +++-
> ?1 file changed, 3 insertions(+), 1 deletion(-)
>
> --- 0001/arch/arm/include/asm/hardirq.h
> +++ work/arch/arm/include/asm/hardirq.h 2010-03-09 21:08:10.000000000 +0900
> @@ -12,7 +12,9 @@ typedef struct {
>
> ?#include <linux/irq_cpustat.h> /* Standard mappings for irq_cpustat_t above */
>
> -#if NR_IRQS > 256
> +#if NR_IRQS > 512
> +#define HARDIRQ_BITS ? 10
> +#elif NR_IRQS > 256
> ?#define HARDIRQ_BITS ? 9
> ?#else
> ?#define HARDIRQ_BITS ? 8
>
Hi Russell,
Good to hear that you are back online. Do you want me to rework this
patch somehow, or is it ready to be queued for upstream merge? I'm
asking because I have a pile of patches that depend on this one.
Cheers,
/ magnus
next prev parent reply other threads:[~2010-04-30 4:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 11:17 [PATCH] ARM: Add support for 10 hardirq bits Magnus Damm
2010-04-30 4:02 ` Magnus Damm [this message]
2010-05-01 9:44 ` Russell King - ARM Linux
2010-05-13 7:30 ` Magnus Damm
2010-05-19 7:16 ` Eric Miao
2010-05-19 8:37 ` Russell King - ARM Linux
2010-05-19 9:05 ` Magnus Damm
2010-05-19 10:02 ` Eric Miao
2010-05-19 8:51 ` Magnus Damm
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=u2yaec7e5c31004292102rd561d7detc73e9fd2a5570ab0@mail.gmail.com \
--to=magnus.damm@gmail.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 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).