From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: siva <sivakumar.subramani-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: ACPI support for add-on devices driver
Date: Thu, 6 Feb 2003 11:44:36 +0000 [thread overview]
Message-ID: <20030206114436.G32277@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3E41EFA3.8060406-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org>; from sivakumar.subramani-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org on Thu, Feb 06, 2003 at 10:46:19AM +0530
On Thu, Feb 06, 2003 at 10:46:19AM +0530, siva wrote:
> I like know what I need to do if I want to have ACPI power management
> support in my driver for an add-on device. When I am browsing APM
> implementation, I found that Linux kernel have general PM Interfaces
> like pm_regsiter and pm_unregsiter. In APM driver, pm_send is being
> called to send notification to all registered add-on devices.
Presumably you're talking about a PCI device? If so, you should implement the
`new-style' PCI driver interface (Documentation/pci.txt), and provide
implementations for ->suspend, ->resume and ->save_state. Also see
Documentation/power/pci.txt.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-02-06 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 5:16 ACPI support for add-on devices driver siva
[not found] ` <3E41EFA3.8060406-uxC5H9eHYlcAvxtiuMwx3w@public.gmane.org>
2003-02-06 10:36 ` Ducrot Bruno
2003-02-06 11:44 ` Matthew Wilcox [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=20030206114436.G32277@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=sivakumar.subramani-uxC5H9eHYlcAvxtiuMwx3w@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