From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Cc: tony@atomide.com, Magnus Damm <magnus.damm@gmail.com>,
kyungmin.park@samsung.com, lethal@linux-sh.org,
linux-mtd@lists.infradead.org, akpm@linux-foundation.org,
dwmw2@infradead.org
Subject: [PATCH] sh: kfr2r09 board support - NAND flash
Date: Thu, 06 Aug 2009 14:58:43 +0000 [thread overview]
Message-ID: <20090806145843.4475.33947.sendpatchset@rx1.opensource.se> (raw)
From: Magnus Damm <damm@igel.co.jp>
This patch adds support for the NAND flash chip
attached to CS4 on the KFR2R09 board. The device is
driven by the platform device driver "onenand-flash".
Signed-off-by: Magnus Damm <damm@igel.co.jp>
---
No merge/build time dependencies, but needs the following patch
to start working on the actual hardware:
"[PATCH] mtd: make onenand/generic.c more generic"
arch/sh/boards/mach-kfr2r09/setup.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
--- 0003/arch/sh/boards/mach-kfr2r09/setup.c
+++ work/arch/sh/boards/mach-kfr2r09/setup.c 2009-08-06 21:37:18.000000000 +0900
@@ -11,6 +11,7 @@
#include <linux/platform_device.h>
#include <linux/interrupt.h>
#include <linux/mtd/physmap.h>
+#include <linux/mtd/onenand.h>
#include <linux/delay.h>
#include <linux/clk.h>
#include <linux/gpio.h>
@@ -62,6 +63,21 @@ static struct platform_device kfr2r09_no
},
};
+static struct resource kfr2r09_nand_flash_resources[] = {
+ [0] = {
+ .name = "NAND Flash",
+ .start = 0x10000000,
+ .end = 0x1001ffff,
+ .flags = IORESOURCE_MEM,
+ }
+};
+
+static struct platform_device kfr2r09_nand_flash_device = {
+ .name = "onenand-flash",
+ .resource = kfr2r09_nand_flash_resources,
+ .num_resources = ARRAY_SIZE(kfr2r09_nand_flash_resources),
+};
+
static struct sh_keysc_info kfr2r09_sh_keysc_info = {
.mode = SH_KEYSC_MODE_1, /* KEYOUT0->4, KEYIN0->4 */
.scan_timing = 3,
@@ -161,12 +177,15 @@ static struct platform_device kfr2r09_sh
static struct platform_device *kfr2r09_devices[] __initdata = {
&kfr2r09_nor_flash_device,
+ &kfr2r09_nand_flash_device,
&kfr2r09_sh_keysc_device,
&kfr2r09_sh_lcdc_device,
};
#define BSC_CS0BCR 0xfec10004
#define BSC_CS0WCR 0xfec10024
+#define BSC_CS4BCR 0xfec10010
+#define BSC_CS4WCR 0xfec10030
static int __init kfr2r09_devices_setup(void)
{
@@ -178,6 +197,10 @@ static int __init kfr2r09_devices_setup(
ctrl_outl(0x36db0400, BSC_CS0BCR);
ctrl_outl(0x00000500, BSC_CS0WCR);
+ /* setup NAND flash at CS4 */
+ ctrl_outl(0x36db0400, BSC_CS4BCR);
+ ctrl_outl(0x00000500, BSC_CS4WCR);
+
/* setup KEYSC pins */
gpio_request(GPIO_FN_KEYOUT0, NULL);
gpio_request(GPIO_FN_KEYOUT1, NULL);
next prev reply other threads:[~2009-08-06 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 15:16 [PATCH] sh: clean up Migo-R header file Magnus Damm
2009-08-06 15:12 ` [PATCH] sh: fix romImage mach dir usage Magnus Damm
2009-08-06 15:03 ` [PATCH] sh: LED9, LED10 and LED11 support for Solution Engine 7724 Magnus Damm
2009-08-06 14:58 ` Magnus Damm [this message]
2009-08-06 14:51 ` [PATCH] sh: kfr2r09 board support - LCDC panel Magnus Damm
2009-08-06 14:34 ` [PATCH] sh: 18-bit SYS panel fix for SuperH Mobile LCDC Magnus Damm
2009-08-06 14:28 ` [PATCH] sh: LCDC SYS bus access wait fix Magnus Damm
2009-08-13 3:03 ` Paul Mundt
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=20090806145843.4475.33947.sendpatchset@rx1.opensource.se \
--to=magnus.damm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=kyungmin.park@samsung.com \
--cc=lethal@linux-sh.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=tony@atomide.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