From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: linux-spi@vger.kernel.org, linux-sh@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: [PATCH v2 11/11] ARM: shmobile: lager legacy: Switch QSPI to named IRQs
Date: Tue, 4 Feb 2014 16:24:05 +0100 [thread overview]
Message-ID: <1391527445-14881-12-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1391527445-14881-1-git-send-email-geert@linux-m68k.org>
From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
---
v2:
- s/DEFINE_RES_IRQ/DEFINE_RES_IRQ_NAMED/
- Rebased on top of renesas-devel-v3.14-rc1-20140204
arch/arm/mach-shmobile/board-lager.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-shmobile/board-lager.c b/arch/arm/mach-shmobile/board-lager.c
index fdcc868de1fa..3fe982b5ca87 100644
--- a/arch/arm/mach-shmobile/board-lager.c
+++ b/arch/arm/mach-shmobile/board-lager.c
@@ -293,7 +293,7 @@ static const struct spi_board_info spi_info[] __initconst = {
/* QSPI resource */
static const struct resource qspi_resources[] __initconst = {
DEFINE_RES_MEM(0xe6b10000, 0x1000),
- DEFINE_RES_IRQ(gic_spi(184)),
+ DEFINE_RES_IRQ_NAMED(gic_spi(184), "mux"),
};
/* VIN */
--
1.7.9.5
prev parent reply other threads:[~2014-02-04 15:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 15:23 [PATCH 00/11] ARM: shmobile: RSPI RZ and QSPI SoC and board integration Geert Uytterhoeven
2014-02-04 15:23 ` [PATCH v3 03/11] ARM: shmobile: genmai defconfig: Enable RSPI Geert Uytterhoeven
2014-02-04 15:23 ` [PATCH v3 04/11] ARM: shmobile: r7s72100 clock: Add RSPI clocks for DT Geert Uytterhoeven
[not found] ` <1391527445-14881-1-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2014-02-04 15:23 ` [PATCH v5 01/11] ARM: shmobile: r7s72100 clock: Add RSPI clocks Geert Uytterhoeven
2014-02-04 15:23 ` [PATCH v5 02/11] ARM: shmobile: genmai legacy: Add RSPI support Geert Uytterhoeven
2014-02-04 15:23 ` [PATCH v5 05/11] ARM: shmobile: r7s72100 dtsi: Add RSPI nodes Geert Uytterhoeven
2014-02-04 15:24 ` [PATCH v4 07/11] ARM: shmobile: koelsch legacy: Add QSPI support Geert Uytterhoeven
2014-02-04 17:37 ` [PATCH 00/11] ARM: shmobile: RSPI RZ and QSPI SoC and board integration Mark Brown
[not found] ` <20140204173733.GI22609-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-02-04 18:54 ` Geert Uytterhoeven
2014-02-05 0:56 ` Simon Horman
2014-02-06 10:36 ` Magnus Damm
2014-02-06 11:43 ` Simon Horman
2014-02-04 15:24 ` [PATCH v4 06/11] ARM: shmobile: r8a7791 clock: add QSPI clocks Geert Uytterhoeven
2014-02-04 15:24 ` [PATCH v4 08/11] ARM: shmobile: koelsch defconfig: Enable RSPI and MTD_M25P80 Geert Uytterhoeven
2014-02-04 15:24 ` [PATCH v3 09/11] ARM: shmobile: r8a7791 dtsi: Add QSPI node Geert Uytterhoeven
2014-02-04 15:24 ` [PATCH v3 10/11] ARM: shmobile: koelsch dts: Add QSPI nodes Geert Uytterhoeven
2014-02-04 15:24 ` Geert Uytterhoeven [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=1391527445-14881-12-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=geert+renesas@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).