linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: albertl@mail.com
Cc: IDE Linux <linux-ide@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>, Doug Maxey <dwm@maxeymade.com>
Subject: Re: [PATCH 1/1] libata-dev: ata_check_atapi_dma() fix for ATA_FLAG_PIO_POLLING LLDDs
Date: Mon, 13 Mar 2006 03:09:33 -0500	[thread overview]
Message-ID: <441528BD.8070708@pobox.com> (raw)
In-Reply-To: <441525DB.40905@tw.ibm.com>

Albert Lee wrote:
> ata_check_atapi_dma() fix for LLDDs with the ATA_FLAG_PIO_POLLING flag.
> 
> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
> ---
> 
> We don't support polling DMA.
> If the LLDD handles only interrupts in the HSM_ST_LAST state 
> (indicated by the ATA_FLAG_PIO_POLLING flag) and the ATAPI device
> generates CDB interrupts, we have to use the polling PIO protocol.
> (Otherwise, the CDB interrupts might confuse the LLDD.)
> 
> We just set the protocol to PIO here in ata_check_atapi_dma().
> Later in ata_qc_issue_prot(), the PIO protocol will be set as "polling"
> for those LLDDs.
> 
> Patch against the irq-pio branch +
> (1) irq-pio minor fixes (respin) +
> (2) integrate polling pio with irq-pio (respin)

Applied, though I think its an open question what happens with 
CDB-interrupt ATAPI devices want to do DMA.  Perhaps we just get an 
interrupt event that we clear, then life proceeds as normal.

Does anybody actually have such a device anywhere?  :)

	Jeff




  reply	other threads:[~2006-03-13  8:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  7:57 [PATCH 1/1] libata-dev: ata_check_atapi_dma() fix for ATA_FLAG_PIO_POLLING LLDDs Albert Lee
2006-03-13  8:09 ` Jeff Garzik [this message]
2006-03-14  4:52   ` Albert Lee
2006-03-15 15:54     ` Mark Lord
2006-03-15 16:12       ` Mark Lord
2006-03-15 16:24         ` Mark Lord
2006-03-16  7:22           ` Albert Lee
2006-03-17  5:51             ` Mark Lord
2006-03-15 16:49         ` Mark Lord
2006-04-01 13:24           ` Albert Lee

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=441528BD.8070708@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=albertl@mail.com \
    --cc=dwm@maxeymade.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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 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).