linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: ide <linux-ide@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
	Mark Lord <liml@rtr.ca>
Subject: Re: [PATCH #upstream] sata_sil24: always set protocol override for non-ATAPI data commands
Date: Thu, 30 Jul 2009 16:53:34 -0400	[thread overview]
Message-ID: <4A72084E.1030508@garzik.org> (raw)
In-Reply-To: <4A71FE71.7040002@gmail.com>

Robert Hancock wrote:
> The sil24 hardware has a built-in list of commands and associated protocols
> that gets used by default to decide how to handle a given command. However,
> if the command is not known to the controller then it presumably assumes it to
> be a non-data command which then causes protocol mismatch errors if the device
> ends up requesting data transfer. The new DATA SET MANAGEMENT - Trim command
> causes this issue since it's a DMA data-out command.
> 
> Since we should always know best what protocol the command should be using,
> let's just set the override flag to inform the controller what protocol to use
> for all non-ATAPI commands with data transfer.
> 
> Signed-off-by: Robert Hancock <hancockrwd@gmail.com>
> Tested-by: Mark Lord <liml@rtr.ca>
> 
> diff --git a/drivers/ata/sata_sil24.c b/drivers/ata/sata_sil24.c
> index 77aa8d7..e6946fc 100644
> --- a/drivers/ata/sata_sil24.c
> +++ b/drivers/ata/sata_sil24.c
> @@ -846,6 +846,17 @@ static void sil24_qc_prep(struct ata_queued_cmd *qc)
>  	if (!ata_is_atapi(qc->tf.protocol)) {
>  		prb = &cb->ata.prb;
>  		sge = cb->ata.sge;
> +		if (ata_is_data(qc->tf.protocol)) {
> +			u16 prot = 0;
> +			ctrl = PRB_CTRL_PROTOCOL;
> +			if (ata_is_ncq(qc->tf.protocol))
> +				prot |= PRB_PROT_NCQ;
> +			if (qc->tf.flags & ATA_TFLAG_WRITE)
> +				prot |= PRB_PROT_WRITE;
> +			else
> +				prot |= PRB_PROT_READ;
> +			prb->prot = cpu_to_le16(prot);
> +		}

I'm trying to remember why we did not do this originally -- Tejun, do 
you recall?

I do not see any prohibition in the docs, so I am inclined to apply this.

	Jeff




  parent reply	other threads:[~2009-07-30 20:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 20:11 [PATCH #upstream] sata_sil24: always set protocol override for non-ATAPI data commands Robert Hancock
2009-07-30 20:18 ` Mark Lord
2009-07-30 20:53 ` Jeff Garzik [this message]
2009-07-31  1:20   ` Tejun Heo
2009-08-22  5:57 ` Robert Hancock
2009-08-22 14:03   ` Mark Lord
2009-08-22 14:11     ` Jeff Garzik
2009-08-22 15:25       ` Mark Lord
2009-08-22 15:28         ` Mark Lord
2009-08-22 16:10           ` Jeff Garzik
2009-08-22 16:27             ` Robert Hancock
2009-08-22 16:02         ` Jeff Garzik
2009-08-22 16:30       ` Robert Hancock

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=4A72084E.1030508@garzik.org \
    --to=jeff@garzik.org \
    --cc=hancockrwd@gmail.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=tj@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 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).