From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 01/11] ACPI: Introduce acpi_bus_power_manageable function
Date: Mon, 7 Jul 2008 09:03:30 +0200 [thread overview]
Message-ID: <20080707070330.GB5643@ucw.cz> (raw)
In-Reply-To: <200806231945.19574.rjw@sisk.pl>
On Mon 2008-06-23 19:45:18, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> ACPI: Introduce acpi_bus_power_manageable function
>
> Introduce function acpi_bus_power_manageable() allowing other
> (dependent) subsystems to check if ACPI is able to power manage given
> device. This may be useful, for example, for PCI device power
> management.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
ACK.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-07-07 7:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806231934.08565.rjw@sisk.pl>
2008-06-23 17:44 ` [PATCH 10/11] PCI PM: Introduce pci_prepare_to_sleep and pci_back_from_sleep Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 01/11] ACPI: Introduce acpi_bus_power_manageable function Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 02/11] PCI: Introduce platform_pci_power_manageable function Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 03/11] PCI: Rework pci_set_power_state function (rev. 3) Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 04/11] ACPI: Introduce acpi_device_sleep_wake function Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 05/11] ACPI: Introduce new device wakeup flag 'prepared' Rafael J. Wysocki
2008-06-23 17:45 ` [PATCH 06/11] PCI ACPI: Introduce acpi_pm_device_sleep_wake function Rafael J. Wysocki
2008-06-23 17:46 ` [PATCH 07/11] PCI ACPI: Introduce can_wakeup platform callback Rafael J. Wysocki
2008-06-23 17:46 ` [PATCH 08/11] PCI PM: Rework device PM initialization (rev. 3) Rafael J. Wysocki
2008-06-23 17:46 ` [PATCH 09/11] ACPI: Make ACPI update wake-up capability flag for devices that can wake up Rafael J. Wysocki
2008-06-23 17:49 ` [PATCH 11/11] PCI: Simplify PCI device PM code Rafael J. Wysocki
2008-06-25 22:05 ` [PATCH 0/11] PCI PM: Handling of PCI devices wake-up functionality Jesse Barnes
2008-06-25 22:24 ` Rafael J. Wysocki
[not found] ` <200806231945.00404.rjw@sisk.pl>
2008-07-07 7:02 ` [PATCH 10/11] PCI PM: Introduce pci_prepare_to_sleep and pci_back_from_sleep Pavel Machek
[not found] ` <200806231945.19574.rjw@sisk.pl>
2008-07-07 7:03 ` Pavel Machek [this message]
[not found] ` <200806231945.26068.rjw@sisk.pl>
2008-07-07 7:05 ` [PATCH 02/11] PCI: Introduce platform_pci_power_manageable function Pavel Machek
[not found] ` <200806231945.32682.rjw@sisk.pl>
2008-07-07 7:15 ` [PATCH 03/11] PCI: Rework pci_set_power_state function (rev. 3) Pavel Machek
[not found] ` <200806231945.39951.rjw@sisk.pl>
2008-07-07 7:18 ` [PATCH 04/11] ACPI: Introduce acpi_device_sleep_wake function Pavel Machek
[not found] ` <200806231945.47937.rjw@sisk.pl>
2008-07-07 7:20 ` [PATCH 05/11] ACPI: Introduce new device wakeup flag 'prepared' Pavel Machek
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=20080707070330.GB5643@ucw.cz \
--to=pavel@suse.cz \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/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