From: "Sameer" <x0081444@ti.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH: Resending] - onenand - OMAP3 support - Kconfig update
Date: Tue, 20 Nov 2007 13:02:01 +0530 [thread overview]
Message-ID: <010001c82b47$71eae130$ec8818ac@ent.ti.com> (raw)
In-Reply-To: <00c601c82aa7$faf8e620$ec8818ac@ent.ti.com>
Hi,
Please ignore the previous patch.
The following patch provides the onenand support for OMAP3.
The patch enables the onenand in def_config file, enable onenand Kconfig for OMAP3 and enables omap2_sleep_block() only if CONFIG_PM
is defined.
Regards,
-Sameer
---
Index: linux-omap-git-20071030/arch/arm/configs/omap_3430sdp_defconfig
===================================================================
--- linux-omap-git-20071030.orig/arch/arm/configs/omap_3430sdp_defconfig
2007-11-08 11:28:56.000000000 -0600
+++ linux-omap-git-20071030/arch/arm/configs/omap_3430sdp_defconfig
2007-11-08 11:29:23.000000000 -0600
@@ -461,7 +461,10 @@
CONFIG_MTD_ONENAND=y
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
# CONFIG_MTD_ONENAND_GENERIC is not set
+CONFIG_MTD_ONENAND_OMAP2=y
# CONFIG_MTD_ONENAND_OTP is not set
+# CONFIG_MTD_ONENAND_2X_PROGRAM is not set
+# CONFIG_MTD_ONENAND_SIM is not set
#
# UBI - Unsorted block images
Index: linux-omap-git-20071030/drivers/mtd/onenand/Kconfig
===================================================================
--- linux-omap-git-20071030.orig/drivers/mtd/onenand/Kconfig 2007-11-08
11:25:21.000000000 -0600
+++ linux-omap-git-20071030/drivers/mtd/onenand/Kconfig 2007-11-08
11:25:44.000000000 -0600
@@ -28,10 +28,10 @@
Support for OneNAND flash via platform device driver.
config MTD_ONENAND_OMAP2
- tristate "OneNAND on OMAP2 support"
- depends on MTD_ONENAND && ARCH_OMAP2
+ tristate "OneNAND on OMAP2/OMAP3 support"
+ depends on MTD_ONENAND && (ARCH_OMAP2 || ARCH_OMAP3)
help
- Support for a OneNAND flash device connected to an OMAP2 CPU
+ Support for a OneNAND flash device connected to an OMAP2/OMAP3 CPU
via the GPMC memory controller.
config MTD_ONENAND_OTP
Index: linux-omap-git-20071030/drivers/mtd/onenand/omap2.c
===================================================================
--- linux-omap-git-20071030.orig/drivers/mtd/onenand/omap2.c 2007-11-08
12:01:45.000000000 -0600
+++ linux-omap-git-20071030/drivers/mtd/onenand/omap2.c 2007-11-08
12:02:08.000000000 -0600
@@ -39,7 +39,6 @@
#include <asm/arch/onenand.h>
#include <asm/arch/gpio.h>
#include <asm/arch/gpmc.h>
-#include <asm/arch/pm.h>
#include <linux/dma-mapping.h>
#include <asm/dma-mapping.h>
@@ -47,6 +46,13 @@
#include <asm/arch/board.h>
+#ifdef CONFIG_PM
+#include <asm/arch/pm.h>
+#else
+#define omap2_block_sleep() /* NULL */
+#define omap2_allow_sleep() /* NULL */
+#endif
+
#define ONENAND_IO_SIZE SZ_128K
#define ONENAND_BUFRAM_SIZE (1024 * 5)
next prev parent reply other threads:[~2007-11-20 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 12:30 [PATCH] - onenand - OMAP3 support - Kconfig update Sameer
2007-11-19 12:39 ` Felipe Balbi
2007-11-20 7:32 ` Sameer [this message]
2007-11-20 7:47 ` [PATCH: Resending] " Kyungmin Park
2007-11-22 4:59 ` Sameer
2007-11-23 21:28 ` Tony Lindgren
2007-11-27 11:21 ` Sameer
2007-11-27 12:55 ` Felipe Balbi
2007-11-28 5:50 ` Sameer
2007-11-28 12:41 ` Felipe Balbi
2007-11-28 21:09 ` Tony Lindgren
2007-12-05 21:15 ` Kamat, Nishant
2007-12-05 23:08 ` Tony Lindgren
2007-12-05 23:14 ` Kamat, Nishant
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='010001c82b47$71eae130$ec8818ac@ent.ti.com' \
--to=x0081444@ti.com \
--cc=linux-omap-open-source@linux.omap.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