From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 04/11] ARM: shmobile: koelsch legacy: Add MSIOF support
Date: Tue, 25 Feb 2014 11:30:12 +0100 [thread overview]
Message-ID: <1393324219-3317-5-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1393324219-3317-1-git-send-email-geert@linux-m68k.org>
From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Add MSIOF resources, platform data, platform device, pinctrl, and SPI
child device.
- Only MSIOF0 is in use, and thus registered. Its bus contains a single
device (a Renesas R2A11302FT PMIC).
- Platform device numbering is 1-based for compatibility with the BSP,
as QSPI uses zero, so MSIOF0's device name is "spi_r8a7791_msiof.1".
Based on patches from Takashi Yoshii <takasi-y@ops.dti.ne.jp>
Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
---
v2:
- Removed resources for unused MSIOF channels.
arch/arm/mach-shmobile/board-koelsch.c | 46 +++++++++++++++++++++++++++-----
1 file changed, 40 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-shmobile/board-koelsch.c b/arch/arm/mach-shmobile/board-koelsch.c
index 5a034ff405d0..618b728cc180 100644
--- a/arch/arm/mach-shmobile/board-koelsch.c
+++ b/arch/arm/mach-shmobile/board-koelsch.c
@@ -44,6 +44,7 @@
#include <linux/sh_eth.h>
#include <linux/spi/flash.h>
#include <linux/spi/rspi.h>
+#include <linux/spi/sh_msiof.h>
#include <linux/spi/spi.h>
#include <mach/common.h>
#include <mach/irqs.h>
@@ -184,6 +185,17 @@ static const struct rspi_plat_data qspi_pdata __initconst = {
.num_chipselect = 1,
};
+/* MSIOF0 */
+static const struct resource sh_msiof0_resources[] __initconst = {
+ DEFINE_RES_MEM(0xe6e20000, 0x0064),
+ DEFINE_RES_IRQ(gic_spi(156)),
+};
+
+static const struct sh_msiof_spi_info sh_msiof_info __initconst = {
+ .rx_fifo_override = 256,
+ .num_chipselect = 1,
+};
+
/* SPI Flash memory (Spansion S25FL512SAGMFIG11 64 MiB) */
static struct mtd_partition spi_flash_part[] = {
{
@@ -214,12 +226,19 @@ static const struct flash_platform_data spi_flash_data = {
static const struct spi_board_info spi_info[] __initconst = {
{
- .modalias = "m25p80",
- .platform_data = &spi_flash_data,
- .mode = SPI_MODE_0,
- .max_speed_hz = 30000000,
- .bus_num = 0,
- .chip_select = 0,
+ .modalias = "m25p80",
+ .platform_data = &spi_flash_data,
+ .mode = SPI_MODE_0,
+ .max_speed_hz = 30000000,
+ .bus_num = 0,
+ .chip_select = 0,
+ }, {
+ .modalias = "r2a1130x",
+ .max_speed_hz = 6000000,
+ .chip_select = 0,
+ .bus_num = 1,
+ .mode = SPI_MODE_3,
+ .controller_data = (void *)-ENOENT, /* HW controlled CS */
},
};
@@ -384,6 +403,15 @@ static const struct pinctrl_map koelsch_pinctrl_map[] = {
"eth_rmii", "eth"),
PIN_MAP_MUX_GROUP_DEFAULT("r8a7791-ether", "pfc-r8a7791",
"intc_irq0", "intc"),
+ /* MSIOF0 */
+ PIN_MAP_MUX_GROUP_DEFAULT("spi_r8a7791_msiof.1", "pfc-r8a7791",
+ "msiof0_clk", "msiof0"),
+ PIN_MAP_MUX_GROUP_DEFAULT("spi_r8a7791_msiof.1", "pfc-r8a7791",
+ "msiof0_sync", "msiof0"),
+ PIN_MAP_MUX_GROUP_DEFAULT("spi_r8a7791_msiof.1", "pfc-r8a7791",
+ "msiof0_rx", "msiof0"),
+ PIN_MAP_MUX_GROUP_DEFAULT("spi_r8a7791_msiof.1", "pfc-r8a7791",
+ "msiof0_tx", "msiof0"),
/* QSPI */
PIN_MAP_MUX_GROUP_DEFAULT("qspi.0", "pfc-r8a7791",
"qspi_ctrl", "qspi"),
@@ -449,6 +477,12 @@ static void __init koelsch_add_standard_devices(void)
qspi_resources,
ARRAY_SIZE(qspi_resources),
&qspi_pdata, sizeof(qspi_pdata));
+ platform_device_register_resndata(&platform_bus, "spi_r8a7791_msiof",
+ 1 + 0, sh_msiof0_resources,
+ ARRAY_SIZE(sh_msiof0_resources),
+ &sh_msiof_info,
+ sizeof(struct sh_msiof_spi_info));
+
spi_register_board_info(spi_info, ARRAY_SIZE(spi_info));
koelsch_add_du_device();
--
1.7.9.5
next prev parent reply other threads:[~2014-02-25 10:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 10:30 [PATCH v2 00/11] ARM: shmobile: MSIOF integration on r8a7790/lager and r8a7791/koelsch Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 01/11] ARM: shmobile: r8a7790: Add MSIOF clocks Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 02/11] ARM: shmobile: r8a7791: " Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 03/11] ARM: shmobile: lager legacy: Add MSIOF support Geert Uytterhoeven
2014-02-25 10:30 ` Geert Uytterhoeven [this message]
2014-02-25 10:30 ` [PATCH v2 05/11] ARM: shmobile: r8a7790/lager dts: Rename label spi to qspi, add spi0 alias Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 06/11] ARM: shmobile: r8a7791/koelsch " Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 07/11] ARM: shmobile: r8a7790 dtsi: Add MSIOF nodes and aliases Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 08/11] ARM: shmobile: r8a7791 " Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 09/11] ARM: shmobile: lager dts: Add MSIOF nodes Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 10/11] ARM: shmobile: koelsch " Geert Uytterhoeven
2014-02-25 10:30 ` [PATCH v2 11/11] ARM: shmobile: koelsch/lager/multi defconfig: Enable MSIOF Geert Uytterhoeven
2014-03-07 0:24 ` Simon Horman
2014-03-05 8:31 ` [PATCH v2 00/11] ARM: shmobile: MSIOF integration on r8a7790/lager and r8a7791/koelsch Magnus Damm
2014-03-06 1:38 ` Simon Horman
2014-03-06 2:25 ` Magnus Damm
2014-03-06 15:28 ` Geert Uytterhoeven
2014-03-07 0:24 ` Simon Horman
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=1393324219-3317-5-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--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).