From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/6] irqchip: s3c24xx: add s3c2450 interrupt definitions
Date: Mon, 18 Mar 2013 23:21:26 +0100 [thread overview]
Message-ID: <2341349.u4eE8qA54r@wuerfel> (raw)
In-Reply-To: <514791DC.9070600@gmail.com>
On Monday 18 March 2013 17:14:52 Rob Herring wrote:
>
> > + s3c24xx,irqlist = <2 0 /* 2D */
> > + 2 0 /* IIC1 */
> > + 0 0 /* reserved */
> > + 0 0 /* reserved */
> > + 2 0 /* PCM0 */
> > + 2 0 /* PCM1 */
> > + 2 0 /* I2S0 */
> > + 2 0>; /* I2S1 */
>
> My first thought here is this information should not be centralized in
> the controller node, but placed with each source node (2D, I2C1, etc).
Seconded. Let's do this the same way we have it for all other irq chips
and put it all into the irq descriptor referring to the controller, not
the controller.
Arnd
next prev parent reply other threads:[~2013-03-18 22:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 13:04 [PATCH v3 0/6] move s3c24xx-irq to drivers/irqchip and add dt support Heiko Stübner
2013-03-17 13:04 ` [PATCH v3 1/6] ARM: S3C24XX: move irq driver to drivers/irqchip Heiko Stübner
2013-03-17 13:05 ` [PATCH v3 2/6] irqchip: s3c24xx: fix comments on some camera interrupts Heiko Stübner
2013-03-17 13:06 ` [PATCH v3 3/6] irqchip: s3c24xx: fix irqlist of second s3c2416 controller Heiko Stübner
2013-03-17 13:07 ` [PATCH v3 4/6] irqchip: s3c24xx: use irq_create_mapping for parent irqs Heiko Stübner
2013-03-17 13:07 ` [PATCH v3 5/6] irqchip: s3c24xx: add devicetree support Heiko Stübner
2013-03-17 22:37 ` Heiko Stübner
2013-03-18 18:59 ` Rob Herring
2013-03-17 13:09 ` [PATCH v3 6/6] irqchip: s3c24xx: add s3c2450 interrupt definitions Heiko Stübner
2013-03-18 15:54 ` Rob Herring
2013-03-18 16:53 ` Heiko Stübner
2013-03-18 22:14 ` Rob Herring
2013-03-18 22:21 ` Arnd Bergmann [this message]
2013-03-18 23:34 ` Heiko Stübner
2013-03-19 2:28 ` Rob Herring
2013-03-19 18:38 ` Heiko Stübner
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=2341349.u4eE8qA54r@wuerfel \
--to=arnd@arndb.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