From: Carlos Aguiar <carlos.aguiar@indt.org.br>
To: linux-omap-open-source@linux.omap.com,
Tony Lindgren <tony@atomide.com>,
Juha Yrjola <juha.yrjola@solidboot.com>
Subject: Add MMC_CAP_{MULTIWRITE,BYTEBLOCK} flags in omap.c
Date: Mon, 06 Nov 2006 15:22:29 -0400 [thread overview]
Message-ID: <454F8B75.5030401@indt.org.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
Hi Tony and folks,
Following previous comments from Juha and Pierre, this patch add
MMC_CAP_{MULTIWRITE,BYTEBLOCK} flags in omap.c
BR,
Carlos.
--
Carlos Eduardo
Nokia Institute of Technology - INdT
Embedded Linux Laboratory - 10LE
Phone: +55 92 2126-1079
Mobile: +55 92 8127-1797
E-mail: carlos.aguiar@indt.org.br
[-- Attachment #2: mmc_omap_caps.diff --]
[-- Type: text/plain, Size: 773 bytes --]
Add MMC_CAP_{MULTIWRITE,BYTEBLOCK} flags
Signed-off-by: Carlos Eduardo Aguiar <carlos.aguiar <at> indt.org.br>
Index: linux-omap-git/drivers/mmc/omap.c
===================================================================
--- linux-omap-git.orig/drivers/mmc/omap.c 2006-11-06 13:20:29.000000000 -0400
+++ linux-omap-git/drivers/mmc/omap.c 2006-11-06 13:50:28.000000000 -0400
@@ -1088,8 +1088,8 @@ static int __init mmc_omap_probe(struct
mmc->ops = &mmc_omap_ops;
mmc->f_min = 400000;
mmc->f_max = 24000000;
- mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34 | MMC_CAP_MULTIWRITE
- | MMC_CAP_BYTEBLOCK;
+ mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34;
+ mmc->caps = MMC_CAP_MULTIWRITE | MMC_CAP_BYTEBLOCK;
if (minfo->wire4)
mmc->caps |= MMC_CAP_4_BIT_DATA;
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2006-11-06 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 19:22 Carlos Aguiar [this message]
2006-11-10 0:36 ` Add MMC_CAP_{MULTIWRITE,BYTEBLOCK} flags in omap.c Tony Lindgren
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=454F8B75.5030401@indt.org.br \
--to=carlos.aguiar@indt.org.br \
--cc=juha.yrjola@solidboot.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