From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] irqchip: Add support for ARMv7-M's NVIC
Date: Thu, 18 Apr 2013 11:24:36 +0200 [thread overview]
Message-ID: <20130418092436.GB21099@pengutronix.de> (raw)
In-Reply-To: <201304181101.13644.arnd@arndb.de>
On Thu, Apr 18, 2013 at 11:01:13AM +0200, Arnd Bergmann wrote:
> On Thursday 18 April 2013, Uwe Kleine-K?nig wrote:
> > > > + * Each bank handles 32 irqs. Only the 16th (= last) bank handles only
> > > > + * 16 irqs.
> > > > + */
> > > > +#define NVIC_MAX_IRQ ((NVIC_MAX_BANKS - 1) * 32 + 16)
> > >
> > > Is this actually inherent to the hardware design, or is the number of irqs
> > > actually customizable? Also, why do you care about the maximum? You only
> > > use it to check against the device tree provided value, but I suppose
> > > you could just as well trust that property to be correct.
> > I don't provide a value for the number of irqs in the device tree. There
> > is only the value INTLINESNUM in the V7M_SCS_ICTR register that is used
> > to determine the number of interrupt banks.
>
> Ah, right. But do you have any reason to believe it could be wrong?
No it's just that the mapping isn't linear in the end.
INTLINESNUM | number of irqs
0 | 32
1 | 64
2 | 96
3 | 128
4 | 160
5 | 192
6 | 224
7 | 256
8 | 288
9 | 320
10 | 352
11 | 384
12 | 416
13 | 448
14 | 480
15 | 496
That is, there are (INTLINESNUM + 1) * 32 irqs for INTLINESNUM < 15. For
INTLINESNUM == 15 there are only 496 and not 16 * 32 == 512. That's the
same on the gic (just with bigger numbers).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-04-18 9:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 16:02 [PATCH v3] irqchip: Add support for ARMv7-M's NVIC Uwe Kleine-König
2013-04-17 20:23 ` Arnd Bergmann
2013-04-18 8:15 ` Uwe Kleine-König
2013-04-18 9:01 ` Arnd Bergmann
2013-04-18 9:24 ` Uwe Kleine-König [this message]
2013-04-18 9:38 ` Arnd Bergmann
2013-04-19 13:51 ` Uwe Kleine-König
2013-04-19 14:14 ` Arnd Bergmann
2013-04-18 9:35 ` Thomas Gleixner
2013-04-19 15:09 ` Uwe Kleine-König
2013-04-22 10:02 ` Uwe Kleine-König
2013-04-22 12:04 ` Arnd Bergmann
2013-04-22 13:50 ` Thomas Gleixner
2013-04-22 14:21 ` 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=20130418092436.GB21099@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).