From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Andrew Baumann <Andrew.Baumann@microsoft.com>
Subject: [Qemu-devel] [PULL 09/10] sdhci: don't raise a command index error for an unexpected response
Date: Tue, 22 Dec 2015 16:54:19 +0800 [thread overview]
Message-ID: <1450774460-17259-10-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1450774460-17259-1-git-send-email-stefanha@redhat.com>
From: Andrew Baumann <Andrew.Baumann@microsoft.com>
This deletes a block of code that raised a command index error if a
command returned response data, but the guest did not set the
appropriate bits in the response register to handle such a response. I
cannot find any documentation that suggests the controller should
behave in this way, the error code doesn't make sense (command index
error is defined for the case where the index in a response does not
match that of the issued command), and in at least one case (CMD23
issued by UEFI on Raspberry Pi 2), actual hardware does not do this.
Signed-off-by: Andrew Baumann <Andrew.Baumann@microsoft.com>
Reviewed-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
Message-id: 1450738069-18664-3-git-send-email-Andrew.Baumann@microsoft.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
hw/sd/sdhci.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/hw/sd/sdhci.c b/hw/sd/sdhci.c
index bc39d48..dd83e89 100644
--- a/hw/sd/sdhci.c
+++ b/hw/sd/sdhci.c
@@ -243,9 +243,6 @@ static void sdhci_send_command(SDHCIState *s)
(s->cmdreg & SDHC_CMD_RESPONSE) == SDHC_CMD_RSP_WITH_BUSY) {
s->norintsts |= SDHC_NIS_TRSCMP;
}
- } else if (rlen != 0 && (s->errintstsen & SDHC_EISEN_CMDIDX)) {
- s->errintsts |= SDHC_EIS_CMDIDX;
- s->norintsts |= SDHC_NIS_ERR;
}
if (s->norintstsen & SDHC_NISEN_CMDCMP) {
--
2.5.0
next prev parent reply other threads:[~2015-12-22 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 8:54 [Qemu-devel] [PULL 00/10] Block patches Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 01/10] virtio-blk: trivial code optimization Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 02/10] block: add BlockLimits.max_iov field Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 03/10] block-backend: add blk_get_max_iov() Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 04/10] block: replace IOV_MAX with BlockLimits.max_iov Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 05/10] block/mirror: replace IOV_MAX with blk_get_max_iov() Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 06/10] parallels: add format spec Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 07/10] scripts/gdb: Fix a python exception in mtree.py Stefan Hajnoczi
2015-12-22 8:54 ` [Qemu-devel] [PULL 08/10] sd: sdhci: Delete over-zealous power check Stefan Hajnoczi
2015-12-22 8:54 ` Stefan Hajnoczi [this message]
2015-12-22 8:54 ` [Qemu-devel] [PULL 10/10] sdhci: add optional quirk property to disable card insertion/removal interrupts Stefan Hajnoczi
2015-12-22 14:47 ` [Qemu-devel] [PULL 00/10] Block patches Peter Maydell
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=1450774460-17259-10-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).