linux-kernel - [RFC][PATCH 0/4] PCI run-time Power Management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200910090051.50932.rjw@sisk.pl>
Date:	Fri, 9 Oct 2009 00:51:50 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linux PCI <linux-pci@...r.kernel.org>
Cc:	pm list <linux-pm@...ts.linux-foundation.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Shaohua Li <shaohua.li@...el.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>
Subject: [RFC][PATCH 0/4] PCI run-time Power Management

Hi,

The following four patches implement some features needed for PCI run-time PM.

[1/4] adds a function for checking and clearing the PME status of a device

[2/4] adds support for PCIe native PME signaling mechanism

[3/4] adds support for ACPI-based PME signaling at run time

[4/4] adds prototype run-time PM callbacks for the PCI bus type

Patches [1/4] - [3/4] are rather complete, unless I missed something,
but [4/4] still requires some work.  For example, there should be some sort of
synchronization between the run-time PM and system-wide sleep transitions
which is missing at the moment.  In addition, it would make sense to
"autosuspend" PCI devices without drivers which has not been implemented
yet.

Comments welcome.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/