* Steve Sakoman <[email protected]> [111005 10:46]: > On Wed, Oct 5, 2011 at 9:26 AM, Tony Lindgren <[email protected]> wrote: > > * Dave Hylands <[email protected]> [111004 23:41]: > > >> I then also had to modify drivers/mmc/card/block.c and initializing > >> disable_multi to 1 in the mmc_blk_issue_rw_rq function to get rid of > >> the following messages for every I/O request. > >> > >> mmcblk0: retrying using single block read > >> mmcblk0: retrying using single block read > >> mmcblk0: retrying using single block read > >> mmcblk0: retrying using single block read > >> > >> (since this revision of the silicon doesn't support multi-block MMC reads). > > > > ..but this one is usually a problem muxing the MMC data lines. > > > > Are you sure this revision only supports one data line? > > No, I think you misunderstood the issue! > > The issue is that multi-block mmc reads are broken and the code falls > back to single block reads but prints a warning each time. > > Looking for a definitive source for this errata with Google I find: > > "According to the TI docs, multiple block read transfer > does not work correctly in CPU revisions 2.1 and earlier (TI advisory > 2.1.1.128)."
OK, thanks for correcting me. > So the correct fix is probably to use multi-block reads only on > revisions post 2.1. Or just permanently switch to single-block reads if the multi-block reads fail? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
