From: "Madhusudhan Chikkature Rajashekar" <madhu.cr@ti.com>
To: linux-omap-open-source@linux.omap.com
Cc: linux-omap@vger.kernel.org
Subject: [RFC/PATCH 3/4] MMC/SD Controller driver for OMAP2430
Date: Fri, 7 Dec 2007 19:20:52 +0530 [thread overview]
Message-ID: <003b01c838d8$2e8bbba0$fe8818ac@ent.ti.com> (raw)
This patch registers the MMC device for OMAP2430/3430.
Signed-off-by: Madhusudhan Chikkature<madhu.cr@ti.com>
---
arch/arm/plat-omap/devices.c | 19 +++++++++++++------
1 files changed, 13 insertions(+), 6 deletions(-)
Index: linux-omap-2.6/arch/arm/plat-omap/devices.c
===================================================================
--- linux-omap-2.6.orig/arch/arm/plat-omap/devices.c 2007-12-06 16:04:39.000000000 +0530
+++ linux-omap-2.6/arch/arm/plat-omap/devices.c 2007-12-07 11:15:50.567693917 +0530
@@ -19,6 +19,7 @@
#include <asm/mach-types.h>
#include <asm/mach/map.h>
+#include <asm/arch/mmc.h>
#include <asm/arch/tc.h>
#include <asm/arch/board.h>
#include <asm/arch/mmc.h>
@@ -156,7 +157,7 @@
#if defined(CONFIG_MMC_OMAP) || defined(CONFIG_MMC_OMAP_MODULE)
-#ifdef CONFIG_ARCH_OMAP24XX
+#if defined(CONFIG_ARCH_OMAP24XX) || defined(CONFIG_ARCH_OMAP34XX)
#define OMAP_MMC1_BASE 0x4809c000
#define OMAP_MMC1_INT INT_24XX_MMC_IRQ
#else
@@ -228,10 +229,6 @@
const struct omap_mmc_config *mmc_conf;
const struct omap_mmc_conf *mmc;
- /* REVISIT: 2430 has HS MMC */
- if (cpu_is_omap2430() || cpu_is_omap34xx())
- return;
-
/* NOTE: assumes MMC was never (wrongly) enabled */
mmc_conf = omap_get_config(OMAP_TAG_MMC, struct omap_mmc_config);
if (!mmc_conf)
@@ -239,6 +236,15 @@
/* block 1 is always available and has just one pinout option */
mmc = &mmc_conf->mmc[0];
+
+#if defined(CONFIG_ARCH_OMAP2430) || defined(CONFIG_ARCH_OMAP3430)
+ if (cpu_is_omap2430() || cpu_is_omap34xx()) {
+ if (mmc->enabled)
+ (void) platform_device_register(&mmc_omap_device1);
+ return;
+ }
+#else
if (mmc->enabled) {
if (cpu_is_omap24xx()) {
omap_cfg_reg(H18_24XX_MMC_CMD);
@@ -289,7 +295,7 @@
mmc1_data.conf = *mmc;
(void) platform_device_register(&mmc_omap_device1);
}
-
+#endif
#ifdef CONFIG_ARCH_OMAP16XX
/* block 2 is on newer chips, and has many pinout options */
mmc = &mmc_conf->mmc[1];
@@ -339,6 +345,7 @@
}
#else
+void omap_set_mmc_info(int host, const struct omap_mmc_platform_data *info) {}
static inline void omap_init_mmc(void) {}
#endif
next reply other threads:[~2007-12-07 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 13:50 Madhusudhan Chikkature Rajashekar [this message]
2007-12-10 17:56 ` [RFC/PATCH 3/4] MMC/SD Controller driver for OMAP2430 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2007-12-11 6:48 Madhusudhan Chikkature Rajashekar
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='003b01c838d8$2e8bbba0$fe8818ac@ent.ti.com' \
--to=madhu.cr@ti.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@vger.kernel.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