From: "Steven J. Hill" <Steven.Hill@cavium.com>
To: David Daney <ddaney@caviumnetworks.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Jan Glauber <jan.glauber@caviumnetworks.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MMC block addressing mode.
Date: Thu, 20 Apr 2017 16:24:28 -0500 [thread overview]
Message-ID: <ebc19d7d-c6a2-0886-a17a-e1b4d82f957e@cavium.com> (raw)
In-Reply-To: <c503aae1-4162-4398-1645-9e2acab5d002@caviumnetworks.com>
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
next prev parent reply other threads:[~2017-04-20 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 19:49 MMC block addressing mode Steven J. Hill
2017-04-20 14:18 ` Ulf Hansson
2017-04-20 16:17 ` Steven J. Hill
2017-04-20 17:12 ` David Daney
2017-04-20 21:24 ` Steven J. Hill [this message]
2017-04-20 21:28 ` Steven J. Hill
2017-04-21 8:23 ` Ulf Hansson
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=ebc19d7d-c6a2-0886-a17a-e1b4d82f957e@cavium.com \
--to=steven.hill@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=jan.glauber@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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