From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm: exynos4: add irq_domain support for wakeup interrupts
Date: Wed, 07 Dec 2011 10:24:36 -0600 [thread overview]
Message-ID: <4EDF9344.7040003@gmail.com> (raw)
In-Reply-To: <1323266392-28330-3-git-send-email-thomas.abraham@linaro.org>
Thomas,
On 12/07/2011 07:59 AM, Thomas Abraham wrote:
> Add irq_domain support for the 32 wakeup interrupt sources.
>
> Cc: Grant Likely <grant.likely@secretlab.ca>
> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> ---
> arch/arm/mach-exynos/include/mach/regs-gpio.h | 4 +-
> arch/arm/mach-exynos/irq-eint.c | 69 ++++++++++++++++---------
> 2 files changed, 46 insertions(+), 27 deletions(-)
>
[snip]
> @@ -193,22 +199,35 @@ static void exynos4_irq_eint0_15(unsigned int irq, struct irq_desc *desc)
>
> int __init exynos4_init_irq_eint(void)
> {
> - int irq;
> + int irq, hwirq;
> + struct irq_domain *domain = &exynos4_eint_irq_domain;
> +
> + domain->irq_base = irq_alloc_descs(IRQ_EINT(0), IRQ_EINT(0),
Can this be dynamic and remove any compile time knowledge of the irq base?
> + EXYNOS4_EINT_NR, 0);
> + if (domain->irq_base < 0) {
> + pr_err("exynos4_init_irq_eint: Failed to alloc irq descs\n");
> + return -EBUSY;
You will hit this error with sparse irq unless you set nr_irq in mach
desc to NR_IRQ_LEGACY (16).
> + }
> + domain->nr_irq = EXYNOS4_EINT_NR;
> + domain->ops = &irq_domain_simple_ops;
> + irq_domain_add(domain);
>
> - for (irq = 0 ; irq <= 31 ; irq++) {
> - irq_set_chip_and_handler(IRQ_EINT(irq), &exynos4_irq_eint,
> + irq_domain_for_each_irq(domain, hwirq, irq) {
> + irq_set_chip_and_handler(irq, &exynos4_irq_eint,
> handle_level_irq);
> - set_irq_flags(IRQ_EINT(irq), IRQF_VALID);
> + set_irq_flags(irq, IRQF_VALID);
> }
>
> irq_set_chained_handler(IRQ_EINT16_31, exynos4_irq_demux_eint16_31);
> + irq_set_handler_data(IRQ_EINT16_31, &domain->irq_base);
>
> - for (irq = 0 ; irq <= 15 ; irq++) {
> - eint0_15_data[irq] = IRQ_EINT(irq);
> + for (hwirq = 0 ; hwirq <= 15 ; hwirq++) {
> + irq = irq_domain_to_irq(domain, hwirq);
> + eint0_15_data[irq] = irq;
>
> - irq_set_handler_data(exynos4_irq_eint_to_gic_irq(irq),
> + irq_set_handler_data(exynos4_irq_eint_to_gic_irq(hwirq),
> &eint0_15_data[irq]);
> - irq_set_chained_handler(exynos4_irq_eint_to_gic_irq(irq),
> + irq_set_chained_handler(exynos4_irq_eint_to_gic_irq(hwirq),
> exynos4_irq_eint0_15);
> }
>
next prev parent reply other threads:[~2011-12-07 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 13:59 [PATCH 0/4] arm: exynos4: add irq domain and device tree support for wakeup interrupts Thomas Abraham
2011-12-07 13:59 ` [PATCH 1/4] arm: exynos4: simplify EINT number to linux irq number translation Thomas Abraham
2011-12-07 13:59 ` [PATCH 2/4] arm: exynos4: add irq_domain support for wakeup interrupts Thomas Abraham
2011-12-07 13:59 ` [PATCH 3/4] arm: exynos4: remove arch_initcall for wakeup interrupt source initialization Thomas Abraham
2011-12-07 13:59 ` [PATCH 4/4] arm: exynos4: add device tree support for external wakeup interrupt controller Thomas Abraham
2011-12-07 16:16 ` Rob Herring
2011-12-07 16:49 ` Thomas Abraham
2011-12-07 16:24 ` Rob Herring [this message]
2011-12-07 17:04 ` [PATCH 2/4] arm: exynos4: add irq_domain support for wakeup interrupts Thomas Abraham
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=4EDF9344.7040003@gmail.com \
--to=robherring2@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).