linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/2] sata_promise: issue ATAPI commands as normal packets
Date: Fri, 19 Jan 2007 19:13:16 -0500	[thread overview]
Message-ID: <45B15E9C.1070309@garzik.org> (raw)
In-Reply-To: <200701132031.l0DKV5Z7010283@harpo.it.uu.se>

Mikael Pettersson wrote:
> This patch (against libata #upstream + the ATAPI cleanup patch)
> reimplements sata_promise's ATAPI support to format ATAPI DMA
> commands as normal packets, and to issue them via the hardware's
> normal packet machinery.
> 
> It turns out that the only reason for issuing ATAPI DMA
> commands via the pdc_issue_atapi_pkt_cmd() procedure was to
> perform two interrupt-fiddling steps for ATA_DFLAG_CDB_INTR
> devices. But these steps aren't needed because sata_promise
> sets ATA_FLAG_PIO_POLLING, which disables DMA for those devices.
> The remaining steps can easily be done in ATA taskfile packets.
> 
> Concrete changes:
> - pdc_atapi_dma_pkt() is extended to program all packet setup
>   steps, and not just contain the CDB; the sequence of steps
>   exactly mirrors what pdc_issue_atapi_pkt_cmd() did
> - pdc_atapi_dma_pkt() needed more parameters: simplify it by
>   just passing 'qc' and having it extract the data it needs
> - pdc_issue_atai_pkt_cmd() and its two helper procedures
>   pdc_wait_for_drq() and pdc_wait_on_busy() are removed
> 
> Tested on first- and second-generation chips, SATAPI and PATAPI,
> with no observable regressions.
> 
> Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>

Applied patches 1-2.

ATAPI handling looks _so_ much better, now that you're using packets, 
doesn't it?  :)

	Jeff




      reply	other threads:[~2007-01-20  0:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13 20:31 [PATCH 1/2] sata_promise: issue ATAPI commands as normal packets Mikael Pettersson
2007-01-20  0:13 ` Jeff Garzik [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=45B15E9C.1070309@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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).