linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [git-patches] EH, irq-pio merge and NCQ patches
Date: Mon, 15 May 2006 11:39:20 -0400	[thread overview]
Message-ID: <4468A0A8.2070300@pobox.com> (raw)
In-Reply-To: <20060515120808.GA23124@htj.dyndns.org>

Tejun Heo wrote:
> I didn't add DMA engine stopping to ata_bmdma_freeze() in this series.
> When BMDMA engine is turned off, all status bits go too.  However, the
> status is used by BMDMA EH to report and to recognize host bus error
> reprsented as timeout.
> 
> To make all of them work, the BMDMA status needs to be stored in
> ata_bmdma_freeze() and used in EH, which is currently a bit difficult
> to implement for generic BMDMA.  I think we can resolve this later.

Agree re storing BMDMA status.  The very next operation needs to be 
DMA-stop, though.  Otherwise shadow register block isn't accessible. 
And you must still check BMDMA status -after- stopping DMA, too (that 
doesn't invalidate your logic quoted above, of course).


> The series can be browsed at the following URL.
> 
> 	http://htj.dyndns.org/git/?p=libata-tj.git;a=shortlog;h=for-jeff
> 
> If you're satisfied with the updates, please pull from.
> 
> 	git://htj.dyndns.org/libata-tj for-jeff

Pulled into #upstream and other branches, and pushed to kernel.org. 
Please check and make sure everything looks OK, after kernel.org 
finishes mirroring to the outside world.

Thanks.

BTW, it would be nice if you would start with branch #sii-irq when you 
are updating the sata_sil interrupt handling path.  And eventually we 
want to push #sii-lbt too.

	Jeff



  parent reply	other threads:[~2006-05-15 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 12:08 [git-patches] EH, irq-pio merge and NCQ patches Tejun Heo
2006-05-15 12:11 ` Tejun Heo
2006-05-15 15:39 ` Jeff Garzik [this message]
2006-05-16  2:11   ` Tejun Heo
2006-05-16  2:25     ` Jeff Garzik

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=4468A0A8.2070300@pobox.com \
    --to=jgarzik@pobox.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).