From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [question] NR_IRQS in genirq
Date: Wed, 24 Nov 2010 13:50:49 +0000 [thread overview]
Message-ID: <20101124135048.GC13507@sirena.org.uk> (raw)
In-Reply-To: <AANLkTik5N0d9wcaiS538UWQ83E_HhXoWC8nMxVY__1+k@mail.gmail.com>
On Wed, Nov 24, 2010 at 09:46:06PM +0800, Haojian Zhuang wrote:
> My hardware environment is ARM. Each machine description can specify
> nr_irqs. In my implementation of PXA, NR_IRQS is fixed for SoC
> internal IRQs. And there's some additional board IRQs, we arrange them
> between NR_IRQS and nr_irqs. So nr_irqs will be larger than NR_IRQS if
> board IRQs exists.
Most ARM platforms have come up with some Kconfig gunk to allow boards
to extend this for off-SoC GPIOs. It'd be really nice to get rid of
NR_IRQS and stop having to worry about this at all :(
next prev parent reply other threads:[~2010-11-24 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimoBdFyQ6GfS2DKiF0wdRox0x7MfM0_keD9Z1D0@mail.gmail.com>
[not found] ` <alpine.LFD.2.00.1011241416360.2900@localhost6.localdomain6>
2010-11-24 13:46 ` [question] NR_IRQS in genirq Haojian Zhuang
2010-11-24 13:50 ` Mark Brown [this message]
2010-11-24 13:54 ` Thomas Gleixner
2010-11-24 14:00 ` Mark Brown
2010-11-24 13:53 ` Thomas Gleixner
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=20101124135048.GC13507@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.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