From: "Leo L. Schwab" <lschwab@tapwave.com>
To: linux-pm@lists.osdl.org
Subject: What's Left at Shutdown?
Date: Wed, 08 Jun 2005 15:09:59 -0700 [thread overview]
Message-ID: <42A76CB7.6080606@tapwave.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
. How much of the kernel is left standing by the time a driver's .shutdown()
vector is called?
We have some hardware we'd like to power off when the system shuts down,
but also during run time when the HW is not in use. During run time, we can
rely on interrupt handlers and the various wait_event*() calls working, but
during the various stages of a full shutdown, this is less clear.
The hardware in question is programmed by writing commands, then waiting
for a completion interrupt. We would prefer to use the same
(interrupt-driven) code path for both "normal" operation and system
shutdown. So what services are guaranteed to be available -- and which are
guaranteed to be unavailable -- when a driver's .shutdown() vector is called?
Thanks in advance.
Schwab
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2005-06-08 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42A76CB7.6080606@tapwave.com \
--to=lschwab@tapwave.com \
--cc=linux-pm@lists.osdl.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