From: Jeff Garzik <jeff@garzik•org>
To: Alan Cox <alan@lxorguk•ukuu.org.uk>
Cc: linux-ide@vger•kernel.org, linuxppc-embedded@ozlabs•org
Subject: Re: IDE driver in polling mode
Date: Tue, 10 Apr 2007 12:18:15 -0400 [thread overview]
Message-ID: <461BB8C7.9050900@garzik.org> (raw)
In-Reply-To: <20070410171125.3aeed29d@the-village.bc.nu>
Alan Cox wrote:
>> Ah, no interrupts at all...
>> The old IDE core in drivers/ide/ certainly doesn't support polling mode
>> and IRQ-less devices. AFAICS, libata also doesn't support the latter...
>
> libata has much of the framework to do this as it originally did all of
> its PIO work much this way. That is probably the most productive place to
> start hacking.
Yep.
The only real restriction in libata is in ata_device_add(), which
unconditionally registers an irq handler. Make a few changes there, add
a few flags, and the existing polling code will kick in.
Once we have higher priority stuff sorted, I would like to look into
things like activating the polling code when it becomes obvious that the
system is not delivering interrupts.
Jeff
next prev parent reply other threads:[~2007-04-10 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 13:35 IDE driver in polling mode Michael
2007-04-10 14:19 ` Sergei Shtylyov
2007-04-10 14:44 ` Mark Lord
2007-04-10 15:31 ` Michael
2007-04-10 16:11 ` Alan Cox
2007-04-10 16:18 ` Jeff Garzik [this message]
2007-04-10 16:29 ` Alan Cox
2007-04-11 8:39 ` Michael
2007-04-11 8:47 ` Alan Cox
2007-04-11 15:10 ` Michael
2007-04-11 15:23 ` Alan Cox
2007-04-12 13:39 ` Mark Lord
2007-04-12 13:40 ` Mark Lord
2007-04-12 13:43 ` Mark Lord
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=461BB8C7.9050900@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=linux-ide@vger$(echo .)kernel.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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