On 04/20/2017 12:12 PM, David Daney wrote: > > Steven and Jan: Can we get around this requirement by: > > - Always set MIO_EMM_DMA[MULTI] = 1; This way by SECTOR mode may be unimportant. > > - Always set MIO_EMM_DMA[SECTOR] = SUITABLE_CONSTANT. > No, this does not work. The 1.88GB card plugged into my 78xx board gives the output below. We cannot just blindly set the MULTI bit for all cards. These results are identical for all four combinations of SECTOR and MULTI values hardcoded. mmc0: host does not support reading read-only switch, assuming write-enable mmc0: new high speed SD card at address d15e mmcblk0: mmc0:d15e SD02G 1.88 GiB mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout blk_update_request: I/O error, dev mmcblk0, sector 0 Buffer I/O error on dev mmcblk0, logical block 0, async page read mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x400900 mmcblk0: command error, retrying timeout mmcblk0: timed out sending r/w cmd command, card status 0x40090 -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
