From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-spi@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: [PATCH V3 4/5] [RFC] ARM: shmobile: genmai: Add preliminary RSPI pinmux setup
Date: Sun, 12 Jan 2014 11:48:42 +0100 [thread overview]
Message-ID: <1389523723-2288-5-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1389523723-2288-1-git-send-email-geert@linux-m68k.org>
From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
This does not work as there's no pinmux configuration in setup-r7s72100.c
yet.
Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
---
V2:
- New
V3:
- No changes
arch/arm/mach-shmobile/board-genmai.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/arch/arm/mach-shmobile/board-genmai.c b/arch/arm/mach-shmobile/board-genmai.c
index f85628e24de4..c8d07d3d81e9 100644
--- a/arch/arm/mach-shmobile/board-genmai.c
+++ b/arch/arm/mach-shmobile/board-genmai.c
@@ -19,6 +19,7 @@
*/
#include <linux/kernel.h>
+#include <linux/pinctrl/machine.h>
#include <linux/platform_device.h>
#include <linux/sh_eth.h>
#include <linux/spi/rspi.h>
@@ -80,9 +81,25 @@ static const struct spi_board_info spi_info[] __initconst = {
},
};
+static const struct pinctrl_map genmai_pinctrl_map[] = {
+ /* RSPI4 */
+ PIN_MAP_MUX_GROUP_DEFAULT("rspi.4", "pfc-r7s72100",
+ "rspi4_rspck_p4_0", "rspi4"),
+ PIN_MAP_MUX_GROUP_DEFAULT("rspi.4", "pfc-r7s72100",
+ "rspi4_ssl0_p4_1", "rspi4"),
+ PIN_MAP_MUX_GROUP_DEFAULT("rspi.4", "pfc-r7s72100",
+ "rspi4_mosi_p4_2", "rspi4"),
+ PIN_MAP_MUX_GROUP_DEFAULT("rspi.4", "pfc-r7s72100",
+ "rspi4_miso_p4_3", "rspi4"),
+};
+
static void __init genmai_add_standard_devices(void)
{
r7s72100_clock_init();
+ pinctrl_register_mappings(genmai_pinctrl_map,
+ ARRAY_SIZE(genmai_pinctrl_map));
+ /* FIXME there's no pinmux configuration in setup-r7s72100.c yet */
+ /* r7s72100_pinmux_init(); */
r7s72100_add_dt_devices();
r7s72100_register_rspi(0);
--
1.7.9.5
next prev parent reply other threads:[~2014-01-12 10:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 10:48 [PATCH V3 0/5] SoC and board integration for RSPI on r7s72100/genmai Geert Uytterhoeven
[not found] ` <1389523723-2288-1-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2014-01-12 10:48 ` [PATCH V3 1/5] pinctrl: sh-pfc: r7s72100: Add RSPI support Geert Uytterhoeven
[not found] ` <1389523723-2288-2-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2014-01-15 9:14 ` Linus Walleij
2014-01-15 19:25 ` Laurent Pinchart
2014-01-12 10:48 ` [PATCH V3 2/5] ARM: shmobile: r7s72100: Add RSPI clocks Geert Uytterhoeven
2014-01-12 10:48 ` [PATCH V3 5/5] ARM: shmobile: genmai: Enable RSPI in defconfig Geert Uytterhoeven
2014-01-12 10:48 ` [PATCH V3 3/5] ARM: shmobile: genmai: Add RSPI support Geert Uytterhoeven
2014-01-12 10:48 ` Geert Uytterhoeven [this message]
2014-01-12 21:32 ` [PATCH V3 0/5] SoC and board integration for RSPI on r7s72100/genmai Laurent Pinchart
2014-01-13 0:33 ` 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=1389523723-2288-5-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=geert+renesas@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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).