From: "Sameer" <x0081444@ti.com>
To: linux-omap-open-source@linux.omap.com,
'Tony Lindgren' <tony@atomide.com>
Subject: [PATCH: Resending] - onenand - OMAP3 support - Kconfig update
Date: Tue, 27 Nov 2007 16:51:24 +0530 [thread overview]
Message-ID: <008b01c830e7$a650a220$ec8818ac@ent.ti.com> (raw)
In-Reply-To: <20071123212831.GJ559@atomide.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 redeclaring the omap2_sleep_block(),
omap2_allow_sleep() according to CONFIG_PM defination in pm.h according to Tony's recommendation.
Regards,
-Sameer
Signed-off-by: Nishant Kamat <nskamat@ti.com>
Signed-off-by: Sameer <sameersu@ti.com>
---
---
arch/arm/configs/omap_3430sdp_defconfig | 3 +++
drivers/mtd/onenand/Kconfig | 6 +++---
include/asm-arm/arch-omap/pm.h | 8 +++++++-
3 files changed, 13 insertions(+), 4 deletions(-)
Index: linux-omap-git/arch/arm/configs/omap_3430sdp_defconfig
===================================================================
--- linux-omap-git.orig/arch/arm/configs/omap_3430sdp_defconfig
+++ linux-omap-git/arch/arm/configs/omap_3430sdp_defconfig
@@ -461,7 +461,10 @@ CONFIG_MTD_OMAP_NOR=y
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/drivers/mtd/onenand/Kconfig
===================================================================
--- linux-omap-git.orig/drivers/mtd/onenand/Kconfig
+++ linux-omap-git/drivers/mtd/onenand/Kconfig
@@ -28,10 +28,10 @@ config MTD_ONENAND_GENERIC
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/include/asm-arm/arch-omap/pm.h
===================================================================
--- linux-omap-git.orig/include/asm-arm/arch-omap/pm.h
+++ linux-omap-git/include/asm-arm/arch-omap/pm.h
@@ -107,7 +107,8 @@
#if !defined(CONFIG_ARCH_OMAP730) && \
!defined(CONFIG_ARCH_OMAP15XX) && \
!defined(CONFIG_ARCH_OMAP16XX) && \
- !defined(CONFIG_ARCH_OMAP24XX)
+ !defined(CONFIG_ARCH_OMAP24XX) && \
+ !defined(CONFIG_ARCH_OMAP34XX)
#error "Power management for this processor not implemented yet"
#endif
@@ -134,8 +135,13 @@ void clk_deny_idle(struct clk *clk);
extern void omap_pm_idle(void);
extern void omap_pm_suspend(void);
+#ifdef CONFIG_PM
extern void omap2_block_sleep(void);
extern void omap2_allow_sleep(void);
+#else
+#define omap2_block_sleep() /* NULL */
+#define omap2_allow_sleep() /* NULL */
+#endif
extern void omap730_cpu_suspend(unsigned short, unsigned short);
extern void omap1510_cpu_suspend(unsigned short, unsigned short);
extern void omap1611_cpu_suspend(unsigned short, unsigned short);
next prev parent reply other threads:[~2007-11-27 11:21 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 ` [PATCH: Resending] " Sameer
2007-11-20 7:47 ` Kyungmin Park
2007-11-22 4:59 ` Sameer
2007-11-23 21:28 ` Tony Lindgren
2007-11-27 11:21 ` Sameer [this message]
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='008b01c830e7$a650a220$ec8818ac@ent.ti.com' \
--to=x0081444@ti.com \
--cc=linux-omap-open-source@linux.omap.com \
--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