From: Felipe Balbi <ext-felipe.lima@nokia.com>
To: "Lindgren Tony (EXT-Atomide/Helsinki)"
<ext-Tony.Lindgren@nokia.com>,
Linux OMAP Mailing List <linux-omap-open-source@linux.omap.com>
Subject: [PATCH]: Fixing blksz_bits calling inside drivers/mmc/mmc.c and drivers/mmc/omap.c
Date: Fri, 27 Oct 2006 11:13:13 -0400 [thread overview]
Message-ID: <45422209.3090602@nokia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
This small patch solves the problem ;-)
Here's the error dump:
drivers/mmc/omap.c: In function 'mmc_omap_prepare_dma':
drivers/mmc/omap.c:636: error: 'struct mmc_data' has no member named
'blksz_bits'
drivers/mmc/omap.c:639: error: 'struct mmc_data' has no member named
'blksz_bits'
drivers/mmc/omap.c: In function 'mmc_omap_prepare_data':
drivers/mmc/omap.c:828: error: 'struct mmc_data' has no member named
'blksz_bits'
Obs: The same occurs for drivers/mmc/mmc.c file
--
Regards,
Felipe Balbi
ext-felipe.lima@nokia.com
OSMRC
[-- Attachment #2: patch-mmc.c.diff --]
[-- Type: text/x-patch, Size: 1210 bytes --]
Index: linux-omap/drivers/mmc/omap.c
===================================================================
--- linux-omap.orig/drivers/mmc/omap.c 2006-10-27 09:18:34.000000000 -0400
+++ linux-omap/drivers/mmc/omap.c 2006-10-27 11:03:14.000000000 -0400
@@ -633,10 +633,10 @@ mmc_omap_prepare_dma(struct mmc_omap_hos
int sync_dev = 0;
data_addr = host->phys_base + OMAP_MMC_REG_DATA;
- frame = 1 << data->blksz_bits;
+ frame = 1 << data->blksz;
count = sg_dma_len(sg);
- if ((data->blocks == 1) && (count > (1 << data->blksz_bits)))
+ if ((data->blocks == 1) && (count > (1 << data->blksz)))
count = frame;
host->dma_len = count;
@@ -825,7 +825,7 @@ mmc_omap_prepare_data(struct mmc_omap_ho
}
- block_size = 1 << data->blksz_bits;
+ block_size = 1 << data->blksz;
OMAP_MMC_WRITE(host, NBLK, data->blocks - 1);
OMAP_MMC_WRITE(host, BLEN, block_size - 1);
--- linux-omap/drivers/mmc/mmc.c 2006-10-26 06:42:31.000000000 -0400
+++ linux-omap-dev/drivers/mmc/mmc.c 2006-10-26 09:53:24.000000000 -0400
@@ -996,7 +996,7 @@
mmc_set_data_timeout(&data, card, 0);
- data.blksz = 1 << 3;
+ data.blksz_bits = 1 << 3;
data.blocks = 1;
data.flags = MMC_DATA_READ;
data.sg = &sg;
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2006-10-27 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 15:13 Felipe Balbi [this message]
2006-10-27 16:02 ` [PATCH]: Fixing blksz_bits calling inside drivers/mmc/mmc.c and drivers/mmc/omap.c Dirk Behme
2006-10-27 16:20 ` Felipe Balbi
2006-10-27 16:30 ` Felipe Balbi
2006-10-27 16:45 ` Dirk Behme
2006-10-27 17:51 ` Felipe Balbi
2006-10-27 18:21 ` Dirk Behme
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=45422209.3090602@nokia.com \
--to=ext-felipe.lima@nokia.com \
--cc=ext-Tony.Lindgren@nokia.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 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.