From: Carlos Aguiar <carlos.aguiar@indt.org.br>
To: Pierre Ossman <drzeus-list@drzeus.cx>,
"linux >> omap-linux" <linux-omap-open-source@linux.omap.com>,
"Anderson F. Briglia" <anderson.briglia@indt.org.br>
Subject: [PATCH 2/3] MMC: OMAP: Fix omap to use MMC_POWER_ON
Date: Tue, 24 Apr 2007 16:37:13 -0400 [thread overview]
Message-ID: <462E6A79.4080409@indt.org.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: 002-MMC-OMAP-Fix-omap-to-use-MMC_POWER_ON.diff --]
[-- Type: text/plain, Size: 1041 bytes --]
As discussed earlier on LKML:
http://lkml.org/lkml/2006/5/4/44
Signed-off-by: Tony Lindgren <tony@atomide.com>
Index: linux-2.6.20/drivers/mmc/omap.c
===================================================================
--- linux-2.6.20.orig/drivers/mmc/omap.c 2007-04-24 15:22:12.000000000 -0400
+++ linux-2.6.20/drivers/mmc/omap.c 2007-04-24 15:22:15.000000000 -0400
@@ -970,8 +970,10 @@ static void mmc_omap_set_ios(struct mmc_
mmc_omap_power(host, 0);
break;
case MMC_POWER_UP:
- case MMC_POWER_ON:
+ /* Cannot touch dsor yet, just power up MMC */
mmc_omap_power(host, 1);
+ return;
+ case MMC_POWER_ON:
dsor |= 1 << 11;
break;
}
@@ -987,7 +989,7 @@ static void mmc_omap_set_ios(struct mmc_
* Writing to the CON register twice seems to do the trick. */
for (i = 0; i < 2; i++)
OMAP_MMC_WRITE(host, CON, dsor);
- if (ios->power_mode == MMC_POWER_UP) {
+ if (ios->power_mode == MMC_POWER_ON) {
/* Send clock cycles, poll completion */
OMAP_MMC_WRITE(host, IE, 0);
OMAP_MMC_WRITE(host, STAT, 0xffff);
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2007-04-24 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 20:37 Carlos Aguiar [this message]
2007-04-24 20:49 ` [PATCH 2/3] MMC: OMAP: Fix omap to use MMC_POWER_ON Carlos Aguiar
-- strict thread matches above, loose matches on Subject: below --
2007-04-24 20:39 Carlos Aguiar
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=462E6A79.4080409@indt.org.br \
--to=carlos.aguiar@indt.org.br \
--cc=anderson.briglia@indt.org.br \
--cc=drzeus-list@drzeus.cx \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.