From: Dean Jenkins <djenkins@mvista.co.uk>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: MMC sub-system: SDIO block-mode with increment address issue
Date: Mon, 19 Nov 2007 11:44:54 +0000 [thread overview]
Message-ID: <1195472694.18869.57.camel@libdev3.libertesoft.co.uk> (raw)
This E-mail is for the attention of Pierre Ossman (MMC sub-system
maintainer)
Hi Pierre,
I've being trying to get SDIO block-mode with incrementing address to
work on an OMAP2430 based reference board with an SDIO card.
Looking at the latest code ( as of 19/11/2007 ) on the mmc-git tree (I'm
not a git expert so I'm not sure how to reference the codebase). I have
a comment to make concerning the following code snippet...
In drivers/mmc/core/sdio_io.c
Function: sdio_io_rw_ext_helper()
<snip>
219 ret = mmc_io_rw_extended(func->card, write,
220 func->num, addr, incr_addr, buf,
221 blocks, func->cur_blksize);
222 if (ret)
223 return ret;
224
225 remainder -= size;
226 buf += size;
227 if (incr_addr)
228 addr += size;
229 }
</snip>
I think the lines
227 if (incr_addr)
228 addr += size;
are incorrect and should be removed. I think the SDIO increment address
parameter relates to the internal operation of the SDIO card and NOT to
the external register address of the FIFO. In other words, I think with
incrementing address enabled in block mode, the register address of the
FIFO in the SDIO function register space will be erroneously changed on
the next block write and will fail (it seems to fail on my card). It
seems strange to change the register address ?
This also relates to byte mode.
What do you think ?
Also, do you have a bug reporting procedure for mmc-git tree ?
Regards,
Dean.
--
Dean Jenkins
Embedded Software Engineer
MontaVista Software (UK)
Professional Services Division
next reply other threads:[~2007-11-19 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 11:44 Dean Jenkins [this message]
2007-11-20 10:58 ` MMC sub-system: SDIO block-mode with increment address issue Pierre Ossman
2007-11-20 12:26 ` Dean Jenkins
2007-11-20 14:10 ` Pierre Ossman
2007-11-21 11:57 ` Dean Jenkins
2007-11-21 13:08 ` Pierre Ossman
2007-11-21 13:32 ` Dean Jenkins
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=1195472694.18869.57.camel@libdev3.libertesoft.co.uk \
--to=djenkins@mvista.co.uk \
--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