From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] gpio: pl061: enable interrupts with DT style binding
Date: Tue, 31 Jan 2012 17:07:02 -0700 [thread overview]
Message-ID: <20120201000702.GL22611@ponder.secretlab.ca> (raw)
In-Reply-To: <4F27FE43.7090503@gmail.com>
On Tue, Jan 31, 2012 at 08:44:19AM -0600, Rob Herring wrote:
> On 01/31/2012 08:36 AM, Shawn Guo wrote:
> > On Mon, Jan 30, 2012 at 11:31:39AM -0600, Rob Herring wrote:
> > ...
> >> -static void __init pl061_init_gc(struct pl061_gpio *chip, int irq_base)
> >> +static void __init pl061_init_gc(struct pl061_gpio *chip,
> >> + struct device_node *node, int irq_base)
> >> {
> >> struct irq_chip_type *ct;
> >>
> >> @@ -212,15 +212,17 @@ static void __init pl061_init_gc(struct pl061_gpio *chip, int irq_base)
> >> ct->chip.irq_set_wake = irq_gc_set_wake;
> >> ct->regs.mask = GPIOIE;
> >>
> >> - irq_setup_generic_chip(chip->irq_gc, IRQ_MSK(PL061_GPIO_NR),
> >> - IRQ_GC_INIT_NESTED_LOCK, IRQ_NOREQUEST, 0);
> >> + irq_setup_generic_chip_domain(chip->irq_gc, node,
> >> + IRQ_MSK(PL061_GPIO_NR),
> >> + IRQ_GC_INIT_NESTED_LOCK,
> >> + IRQ_NOREQUEST, 0);
> >> }
> >
> > The function irq_setup_generic_chip_domain() is wrapped by
> > #ifdef CONFIG_IRQ_DOMAIN in patch #1. Is it true that pl061 driver
> > will never work with !IRQ_DOMAIN case?
>
> You're right unless Grant thinks IRQ_DOMAIN should always be enabled for
> ARM? Otherwise, I'll add something like this for !IRQ_DOMAIN:
I think always having IRQ_DOMAIN on are is where we want to get to; or at least
have platforms that use it depend on it or select it. I don't want to see
interrupt controllers both use irq_domain and also their own open-coded
translation mechanism. That's just a fail.
If irq_domain isn't acceptable to be enabled all the time, then it needs to be
refactored until it is.
g.
prev parent reply other threads:[~2012-02-01 0:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 17:31 [PATCH v3 0/2] generic irq chip and pl061 domain support Rob Herring
2012-01-30 17:31 ` [PATCH v3 1/2] irq: add irq_domain support to generic-chip Rob Herring
2012-01-31 14:13 ` Shawn Guo
2012-01-31 14:32 ` Rob Herring
2012-01-31 15:06 ` Shawn Guo
2012-01-31 15:37 ` Rob Herring
2012-02-01 0:02 ` Grant Likely
2012-01-30 17:31 ` [PATCH v3 2/2] gpio: pl061: enable interrupts with DT style binding Rob Herring
2012-01-31 14:36 ` Shawn Guo
2012-01-31 14:44 ` Rob Herring
2012-02-01 0:07 ` Grant Likely [this message]
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=20120201000702.GL22611@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--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).