From: Jason Cooper <jason@lakedaemon.net>
To: Alban Bedel <albeu@free.fr>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
Alexander Couzens <lynxis@fe80.eu>,
Joel Porquet <joel@porquet.org>,
Andrew Bresticker <abrestic@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] MIPS: ath79: irq: Move the MISC driver to drivers/irqchip
Date: Tue, 17 Nov 2015 20:03:27 +0000 [thread overview]
Message-ID: <20151117200327.GA6520@io.lakedaemon.net> (raw)
In-Reply-To: <1447788896-15553-5-git-send-email-albeu@free.fr>
Hi Alban,
On Tue, Nov 17, 2015 at 08:34:54PM +0100, Alban Bedel wrote:
> The driver stays the same but the initialization changes a bit.
> For OF boards we now get the memory map from the OF node and use
> a linear mapping instead of the legacy mapping. For legacy boards
> we still use a legacy mapping and just pass down all the parameters
> from the board init code.
>
> Signed-off-by: Alban Bedel <albeu@free.fr>
> ---
> arch/mips/ath79/irq.c | 163 +++------------------------
> arch/mips/include/asm/mach-ath79/ath79.h | 3 +
> drivers/irqchip/Makefile | 1 +
> drivers/irqchip/irq-ath79-misc.c | 182 +++++++++++++++++++++++++++++++
> 4 files changed, 201 insertions(+), 148 deletions(-)
> create mode 100644 drivers/irqchip/irq-ath79-misc.c
...
> diff --git a/drivers/irqchip/Makefile b/drivers/irqchip/Makefile
> index 177f78f..a8f9075 100644
> --- a/drivers/irqchip/Makefile
> +++ b/drivers/irqchip/Makefile
> @@ -1,5 +1,6 @@
> obj-$(CONFIG_IRQCHIP) += irqchip.o
>
> +obj-$(CONFIG_ATH79) += irq-ath79-misc.o
> obj-$(CONFIG_ARCH_BCM2835) += irq-bcm2835.o
> obj-$(CONFIG_ARCH_BCM2835) += irq-bcm2836.o
> obj-$(CONFIG_ARCH_EXYNOS) += exynos-combiner.o
CONFIG_ARCH_ATH79 ?
Same for the last patch in the series (cpu driver).
thx,
Jason.
next prev parent reply other threads:[~2015-11-18 17:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:34 [PATCH 0/6] MIPS: ath79: Move the IRQ drivers to drivers/irqchip Alban Bedel
2015-11-17 19:34 ` [PATCH 1/6] MIPS: ath79: Fix the size of the MISC INTC registers in ar9132.dtsi Alban Bedel
2015-11-17 19:34 ` [PATCH 2/6] MIPS: ath79: irq: Remove useless #ifdef CONFIG_IRQCHIP Alban Bedel
2015-11-17 19:34 ` [PATCH 3/6] MIPS: ath79: irq: Prepare moving the MISC driver to drivers/irqchip Alban Bedel
2015-11-17 19:34 ` [PATCH 4/6] MIPS: ath79: irq: Move " Alban Bedel
2015-11-17 20:03 ` Jason Cooper [this message]
2015-11-17 20:06 ` Thomas Gleixner
2015-11-17 20:09 ` Jason Cooper
2015-12-30 13:53 ` Alban
2015-12-30 13:53 ` Alban
2016-01-20 8:15 ` Alban
2016-01-20 8:15 ` Alban
2016-01-20 12:38 ` Marc Zyngier
2016-01-20 12:38 ` Marc Zyngier
2016-01-20 19:51 ` Alban
2016-01-20 19:51 ` Alban
2015-11-17 19:34 ` [PATCH 5/6] MIPS: ath79: Allow using ath79_ddr_wb_flush() from drivers Alban Bedel
2015-11-17 19:34 ` [PATCH 6/6] MIPS: ath79: irq: Move the CPU IRQ driver to drivers/irqchip Alban Bedel
2016-01-20 12:49 ` Marc Zyngier
2016-01-20 12:49 ` Marc Zyngier
2016-01-20 19:46 ` Alban
2016-01-20 19:46 ` Alban
2016-01-21 8:52 ` Marc Zyngier
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=20151117200327.GA6520@io.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=abrestic@chromium.org \
--cc=albeu@free.fr \
--cc=joel@porquet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=lynxis@fe80.eu \
--cc=marc.zyngier@arm.com \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
/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