From: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
To: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
acpi-dev
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: IDE _GTM/_STM support
Date: Mon, 23 May 2005 12:08:05 +0100 [thread overview]
Message-ID: <1116846484.5743.34.camel@localhost.localdomain> (raw)
In-Reply-To: <1116814023.3852.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
On Llu, 2005-05-23 at 03:07, Shaohua Li wrote:
> > Its waiting for the I/O to finish. The IDE layer needs the request
> > queues to be running so you probably need to defer the taskfile calls.
> The ACPI spec the _GTF task should be invoked very early. Eg. before
> other commands. Deferring the taskfile call possibly can't meet the
> requirement, can it? Sorry, I don't understand Linux IDE. The generic
> ide resume routine invokes a 'PM_RESUME' request, could _GTF commands be
> invoked before the PM_RESUME request?
Linux IDE is entirely request queue driven (almost anyway). If you
wanted to run a taskfile early you'd really need to go around the IDE
layer and perform the task file operations directly. For almost all of
the controllers that should not be a big problem as the register
addresses, operations and related information are in the IDE hwif
structure and issuing a polled taskfile is relatively trivial and
standardised code.
ie you can go
ACPI -> PCI device
PCI device -> IDE hwif
IDE hwif -> register addresses, ops
Directly issue polled taskfile
Poll for completion
and you can do that even before interrupts are enabled.
In the SATA world it gets more complicated but Jeff Garzik's SATA layer
seems to have the right functions exposed to issue taskfiles directly.
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
prev parent reply other threads:[~2005-05-23 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 22:35 IDE _GTM/_STM support Matthew Garrett
2005-05-22 22:50 ` Alan Cox
[not found] ` <1116802237.5730.29.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-05-23 2:07 ` Shaohua Li
[not found] ` <1116814023.3852.6.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-05-23 11:08 ` Alan Cox [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=1116846484.5743.34.camel@localhost.localdomain \
--to=alan-qbu/x9rampvanceybjwyrvxrex20p6io@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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