From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] arm: mvebu: move irq controller driver to drivers/irqchip
Date: Mon, 29 Oct 2012 10:18:24 +0100 [thread overview]
Message-ID: <508E49E0.8050606@gmail.com> (raw)
In-Reply-To: <1351462748-5224-4-git-send-email-thomas.petazzoni@free-electrons.com>
On 10/28/2012 11:19 PM, Thomas Petazzoni wrote:
> Now that the drivers/irqchip/ directory has a minimal infrastructure
> to support the addition of irq controller driver, we move the irq
> controller driver for Armada 370 and Armada XP ARM SoCs from the
> arch/arm/mach-mvebu/ directory to the drivers/irqchip/ directory and
> update the irqchip infrastructure to take into account this new
> driver.
>
> [...]
> diff --git a/drivers/irqchip/Makefile b/drivers/irqchip/Makefile
> index 6b5a6e0..5148ffd 100644
> --- a/drivers/irqchip/Makefile
> +++ b/drivers/irqchip/Makefile
> @@ -1,2 +1,3 @@
> obj-$(CONFIG_IRQCHIP) += irqchip.o
> obj-$(CONFIG_ARCH_BCM2835) += irq-bcm2835.o
> +obj-$(CONFIG_ARCH_MVEBU) += irq-armada-370-xp.o
Thomas,
using ARCH_MVEBU for enabling irq-armada-370-xp here will lead to
incompatibilities with Orion SoCs when they move over to ARCH_MVEBU.
Although, it is ok for the moment please choose either a CONFIG_
common for both Armada 370 and XP.
With a Kconfig within drivers/irqchip you could define a
ARMADA_370_XP_IRQ and select that in MACH_ARMADA_370 and MACH_ARMADA_XP
or MACH_ARMADA_370_XP, which all already exist.
As soon as the patch is through, I can provide (and use) a irq-orion
based on irqchip. I can provide it earlier but to actually use it there
are still some other patches required on Dove. Other Orions could
switch now, I guess.
Sebastian
next prev parent reply other threads:[~2012-10-29 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 22:19 [PATCH v3] Introduce minimal irqchip infrastructure Thomas Petazzoni
2012-10-28 22:19 ` [PATCH v3 1/4] irqchip: add basic infrastructure Thomas Petazzoni
2012-10-28 22:19 ` [PATCH v3 2/4] arm: bcm2835: convert to the irqchip infrastructure Thomas Petazzoni
2012-11-06 16:56 ` Josh Cartwright
2012-11-06 17:54 ` Josh Cartwright
2012-11-07 7:09 ` Thomas Petazzoni
2012-10-28 22:19 ` [PATCH v3 3/4] arm: mvebu: move irq controller driver to drivers/irqchip Thomas Petazzoni
2012-10-29 9:18 ` Sebastian Hesselbarth [this message]
2012-10-29 9:24 ` Thomas Petazzoni
2012-10-29 9:38 ` Sebastian Hesselbarth
2012-10-29 9:50 ` Thomas Petazzoni
2012-10-29 10:03 ` Andrew Lunn
2012-10-28 22:19 ` [PATCH v3 4/4] irqchip: add to the directories part of the IRQ subsystem in MAINTAINERS Thomas Petazzoni
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=508E49E0.8050606@gmail.com \
--to=sebastian.hesselbarth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.