From: Paolo Bonzini <pbonzini@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] esp-pci: Fix status register write erase control
Date: Thu, 29 Nov 2018 10:58:51 +0100 [thread overview]
Message-ID: <6a6b51f9-f24b-7cac-8804-a3feeefd40d7@redhat.com> (raw)
In-Reply-To: <1543442171-24863-1-git-send-email-linux@roeck-us.net>
On 28/11/18 22:56, Guenter Roeck wrote:
> Per AM53C974 datasheet, definition of "SCSI Bus and Control (SBAC)"
> register:
>
> Bit 24 – STATUS – Write Erase Control
>
> This bit controls the Write Erase feature on bits 3:1 and bit 6 of the DMA
> Status Register ((B)+54h). When this bit is programmed to ‘1’, the state
> of bits 3:1 are preserved when read. Bits 3:1 are only cleared when a ‘1’
> is written to the corresponding bit location. For example, to clear bit 1,
> the value of ‘0000_0010b’ should be written to the register. When the DMA
> Status Preserve bit is ‘0’, bits 3:1 are cleared when read.
>
> The status register is currently defined to bit 12, not bit 24.
> Also, its implementation is reversed: The status is auto-cleared if
> the bit is set to 1, and must be cleared explicitly when the bit is
> set to 0. This results in spurious interrupts reported by the Linux
> kernel, and in some cases even results in stalled SCSI operations.
>
> Set SBAC_STATUS to bit 24 and reverse the logic to fix the problem.
>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> hw/scsi/esp-pci.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/scsi/esp-pci.c b/hw/scsi/esp-pci.c
> index 419fc66..d956909 100644
> --- a/hw/scsi/esp-pci.c
> +++ b/hw/scsi/esp-pci.c
> @@ -59,7 +59,7 @@
> #define DMA_STAT_SCSIINT 0x10
> #define DMA_STAT_BCMBLT 0x20
>
> -#define SBAC_STATUS 0x1000
> +#define SBAC_STATUS (1 << 24)
>
> typedef struct PCIESPState {
> /*< private >*/
> @@ -136,7 +136,7 @@ static void esp_pci_dma_write(PCIESPState *pci, uint32_t saddr, uint32_t val)
> pci->dma_regs[saddr] = val;
> break;
> case DMA_STAT:
> - if (!(pci->sbac & SBAC_STATUS)) {
> + if (pci->sbac & SBAC_STATUS) {
> /* clear some bits on write */
> uint32_t mask = DMA_STAT_ERROR | DMA_STAT_ABORT | DMA_STAT_DONE;
> pci->dma_regs[DMA_STAT] &= ~(val & mask);
> @@ -157,7 +157,7 @@ static uint32_t esp_pci_dma_read(PCIESPState *pci, uint32_t saddr)
> if (pci->esp.rregs[ESP_RSTAT] & STAT_INT) {
> val |= DMA_STAT_SCSIINT;
> }
> - if (pci->sbac & SBAC_STATUS) {
> + if (!(pci->sbac & SBAC_STATUS)) {
> pci->dma_regs[DMA_STAT] &= ~(DMA_STAT_ERROR | DMA_STAT_ABORT |
> DMA_STAT_DONE);
> }
>
Queued this one only, for now at least.
Paolo
prev parent reply other threads:[~2018-11-29 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 21:56 [Qemu-devel] [PATCH 1/2] esp-pci: Fix status register write erase control Guenter Roeck
2018-11-28 21:56 ` [Qemu-devel] [PATCH 2/2] scsi: esp: Improve consistency of RSTAT, RSEQ, and RINTR Guenter Roeck
2018-11-29 9:58 ` Paolo Bonzini
2018-11-29 11:56 ` Mark Cave-Ayland
2018-11-29 15:42 ` Guenter Roeck
2018-11-29 17:38 ` Guenter Roeck
2018-11-29 17:53 ` Paolo Bonzini
2018-11-29 18:07 ` Mark Cave-Ayland
2018-11-29 19:00 ` Guenter Roeck
2018-11-29 19:33 ` Mark Cave-Ayland
2018-11-29 21:26 ` Guenter Roeck
2018-11-29 18:34 ` Mark Cave-Ayland
2018-11-29 19:07 ` Guenter Roeck
2018-11-29 19:38 ` Mark Cave-Ayland
2018-11-29 14:18 ` Guenter Roeck
2018-11-29 9:58 ` Paolo Bonzini [this message]
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=6a6b51f9-f24b-7cac-8804-a3feeefd40d7@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=linux@roeck-us.net \
--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).