From: Dean Jenkins <djenkins@mvista.co.uk>
To: Pierre Ossman <drzeus-mmc@drzeus.cx>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: MMC/SDIO sub-system: block mode versus byte mode
Date: Thu, 22 Nov 2007 10:41:43 +0000 [thread overview]
Message-ID: <1195728103.20691.125.camel@libdev3.libertesoft.co.uk> (raw)
Hi Pierre,
I've been checking my SDIO CMD53 data transfers and I notice the
following:
block size = 256 bytes for my SDIO card.
transfers of 256 bytes uses byte mode ( I expected block mode )
transfers of 512 bytes uses block mode ( because blocks = 2 )
>From the SD spec a single block transfer seems to be valid.
I notice the function mmc_io_rw_extended() in sdio_ops.c seems to select
byte mode when the transfer size is 512 or less when the blocks
parameter variable is 1. In fact blocks is never 0.
Therefore is this a feature or a bug that prevents 256 bytes being sent
in block mode when it is a single complete 1 block of data ?
If it is a bug then I suggest the sdio_io_rw_ext_helper() in sdio_io.c
be able to select byte mode by setting blocks to 0 and then blocks can
be set to 1 to select block mode for a single block.
Have I missed something ?
Technically, there is a bug in sdio_io_rw_ext_helper() in sdio_io.c
211 while (remainder > func->cur_blksize) {
should be, = missing
211 while (remainder >= func->cur_blksize) {
however the resulting call to mmc_io_rw_extended() is the same as blocks
= 1 for both the "block mode" while loop (with the "fix") and the "byte
mode" while loop (without the "fix"). The "byte mode" while loop has a
hard coded value of 1 for the blocks parameter. So the bug is masked. As
I said above, I think the "byte mode" should use a value of 0 for the
blocks parameter.
What do you think ?
Regards,
Dean.
--
Dean Jenkins
Embedded Software Engineer
MontaVista Software (UK)
Professional Services Division
next reply other threads:[~2007-11-22 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 10:41 Dean Jenkins [this message]
2007-11-22 11:42 ` Pierre Ossman
2007-11-22 12:15 ` Dean Jenkins
2007-11-22 19:24 ` Pierre Ossman
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=1195728103.20691.125.camel@libdev3.libertesoft.co.uk \
--to=djenkins@mvista.co.uk \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®