From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, pmhahn@titan.lahn.de,
flyboy@gmail.com
Subject: Re: [PATCH] libata: always use polling SETXFER
Date: Wed, 14 Mar 2007 15:09:45 +0100 [thread overview]
Message-ID: <200703141509.45652.bzolnier@gmail.com> (raw)
In-Reply-To: <20070314053338.GA15600@htj.dyndns.org>
On Wednesday 14 March 2007, Tejun Heo wrote:
> Several people have reported LITE-ON LTR-48246S detection failed
> because SETXFER fails. It seems the device raises IRQ too early after
> SETXFER. This is controller independent. The same problem has been
> reported for different controllers.
>
> So, now we have pata_via where the controller raises IRQ before it's
> ready after SETXFER and a device which does similar thing. This patch
> makes libata always execute SETXFER via polling. As this only happens
> during EH, performance impact is nil. Setting ATA_TFLAG_POLLING is
> also moved from issue hot path to ata_dev_set_xfermode() - the only
> place where SETXFER can be issued.
>
> Jeff Garzik suggests that, in the long term, it might be better to
> modify libata HSM implementation such that we're more tolerant of
> erratic ATAPI IRQ behavior - e.g. default to IRQ but falling back to
> polling if the device doesn't seem ready at the point of interrupt.
> Such change might be necessary to support ancient/weird ATAPI devices.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
Acked-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
next prev parent reply other threads:[~2007-03-14 14:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 5:33 [PATCH] libata: always use polling SETXFER Tejun Heo
2007-03-14 14:09 ` Bartlomiej Zolnierkiewicz [this message]
2007-04-30 0:45 ` Tejun Heo
2007-05-25 10:58 ` Jeff Garzik
2007-05-25 11:58 ` Tejun Heo
2007-05-25 12:26 ` Jeff Garzik
2007-05-25 12:52 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-05-27 13:10 Tejun Heo
2007-06-03 16:00 ` Jeff Garzik
2007-06-03 17:24 ` Bartlomiej Zolnierkiewicz
2007-06-03 18:45 ` Linus Torvalds
2007-06-03 18:17 ` Andrew Morton
2007-06-03 19:40 ` Linus Torvalds
2007-06-04 14:42 ` Alan Cox
2007-06-04 20:34 ` Linus Torvalds
2007-06-04 20:38 ` 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=200703141509.45652.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=flyboy@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=pmhahn@titan.lahn.de \
/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.