All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Hannes Reinecke <hare@suse.de>,
	James Bottomley <jbottomley@parallels.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 05/10] esp_scsi: read status registers
Date: Fri, 21 Nov 2014 10:43:33 +0100	[thread overview]
Message-ID: <546F0945.1030503@redhat.com> (raw)
In-Reply-To: <1416562077-105715-6-git-send-email-hare@suse.de>



On 21/11/2014 10:27, Hannes Reinecke wrote:
> A read to ESP_INTRPT will clear ESP_STATUS and ESP_SSTEP. So read
> all status registers in one go to avoid losing information.

(ESP_STAT_TCNT is actually kept in the status register, it is cleared by
writing TCLO/MID/HI).

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

> Signed-off-by: Hannes Reinecke <hare@suse.de>
> ---
>  drivers/scsi/esp_scsi.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/scsi/esp_scsi.c b/drivers/scsi/esp_scsi.c
> index fe3278e..92ab921 100644
> --- a/drivers/scsi/esp_scsi.c
> +++ b/drivers/scsi/esp_scsi.c
> @@ -982,7 +982,6 @@ static int esp_check_spur_intr(struct esp *esp)
>  
>  	default:
>  		if (!(esp->sreg & ESP_STAT_INTR)) {
> -			esp->ireg = esp_read8(ESP_INTRPT);
>  			if (esp->ireg & ESP_INTR_SR)
>  				return 1;
>  
> @@ -2056,7 +2055,12 @@ static void __esp_interrupt(struct esp *esp)
>  	int finish_reset, intr_done;
>  	u8 phase;
>  
> +       /*
> +	* Once INTRPT is read STATUS and SSTEP are cleared.
> +	*/
>  	esp->sreg = esp_read8(ESP_STATUS);
> +	esp->seqreg = esp_read8(ESP_SSTEP);
> +	esp->ireg = esp_read8(ESP_INTRPT);
>  
>  	if (esp->flags & ESP_FLAG_RESETTING) {
>  		finish_reset = 1;
> @@ -2069,8 +2073,6 @@ static void __esp_interrupt(struct esp *esp)
>  			return;
>  	}
>  
> -	esp->ireg = esp_read8(ESP_INTRPT);
> -
>  	if (esp->ireg & ESP_INTR_SR)
>  		finish_reset = 1;
>  
> 

  reply	other threads:[~2014-11-21  9:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  9:27 [PATCH 00/10] Re-implement am53c974 driver Hannes Reinecke
2014-11-21  9:27 ` [PATCH 01/10] esp_scsi: spellcheck 'driver' Hannes Reinecke
2014-11-21  9:35   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 02/10] esp_scsi: make number of tags configurable Hannes Reinecke
2014-11-21  9:37   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 03/10] esp_scsi: convert to dev_printk Hannes Reinecke
2014-11-21  9:37   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 04/10] esp_scsi: debug event and command Hannes Reinecke
2014-11-21  9:38   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 05/10] esp_scsi: read status registers Hannes Reinecke
2014-11-21  9:43   ` Paolo Bonzini [this message]
2014-11-21  9:27 ` [PATCH 06/10] scsi: add 'am53c974' driver Hannes Reinecke
2014-11-21 10:14   ` Paolo Bonzini
2014-11-21 10:34     ` Hannes Reinecke
2014-11-21 10:20   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 07/10] esp: Use FIFO for command submission Hannes Reinecke
2014-11-21 10:04   ` Paolo Bonzini
2014-11-21 10:38     ` Hannes Reinecke
2014-11-21 10:50       ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 08/10] am53c974: BLAST residual handling Hannes Reinecke
2014-11-21 10:10   ` Paolo Bonzini
2014-11-21 10:29     ` Hannes Reinecke
2014-11-21  9:27 ` [PATCH 09/10] esp: correctly detect am53c974 Hannes Reinecke
2014-11-21 10:11   ` Paolo Bonzini
2014-11-21  9:27 ` [PATCH 10/10] esp: enable CONFIG2_FENAB for am53c974 Hannes Reinecke
2014-11-21 10:08   ` Paolo Bonzini
2014-11-21 10:22     ` Hannes Reinecke
2014-11-21 10:52       ` Paolo Bonzini
2014-11-21 10:26 ` [PATCH 00/10] Re-implement am53c974 driver Christoph Hellwig
2014-11-21 10:33   ` Hannes Reinecke
2014-11-21 10:47     ` Guennadi Liakhovetski

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=546F0945.1030503@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.