From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: "Jon Kåre Hellan" <hellan@acm.org>,
linux-ide@vger.kernel.org,
"Carlos Pardo" <Carlos.Pardo@siliconimage.com>
Subject: Re: sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE
Date: Wed, 22 Feb 2006 22:58:38 -0500 [thread overview]
Message-ID: <43FD32EE.5080302@pobox.com> (raw)
In-Reply-To: <43FD3181.5010702@gmail.com>
Tejun Heo wrote:
> We also need to delist some drives from m15w list according to SIMG's
> blacklist. Is there any reason why sata_sil wants irq-pio desparately
> compared to other drivers? Actually it seems that all sata_sil
I presume the root cause is that SiI hardware is more like sata_vsc,
hardware that _really_ wants to deliver an interrupt upon completion,
even if interrupts are ostensibly disabled.
There are many reports in the field of a "lockup" (really screaming
interrupts) that is solved by irq-pio or 'irqpoll' option.
> controllers seem to be capable of performing PIO using DMA which makes
> PIO support unncessary.
This isn't supported because its a pain in the ass. You must set up a
new DMA transfer for each DRQ block in the PIO transfer.
If you want to write the code the support this... great! That's
definitely the best way to go long-term.
Jeff
next prev parent reply other threads:[~2006-02-23 3:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 18:03 sata_sil.c, 3512 and SIL_QUIRK_MOD15WRITE Jon Kåre Hellan
2006-02-23 2:07 ` Tejun Heo
2006-02-23 3:35 ` Jeff Garzik
2006-02-23 3:52 ` Tejun Heo
2006-02-23 3:58 ` Jeff Garzik [this message]
2006-02-23 6:59 ` Jon K Hellan
2006-02-23 7:19 ` Tejun Heo
2006-02-24 7:08 ` Jon K Hellan
2006-02-24 7:21 ` Tejun Heo
2006-02-24 7:26 ` Tejun Heo
2006-02-24 8:33 ` Jon Kåre Hellan
2006-02-24 18:07 ` Jon K Hellan
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=43FD32EE.5080302@pobox.com \
--to=jgarzik@pobox.com \
--cc=Carlos.Pardo@siliconimage.com \
--cc=hellan@acm.org \
--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 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.