diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2012-12-23 00:02:13 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2013-01-03 13:09:40 +0100 |
commit | 11909ca1cf614f9396b17d366f9e3cfcba7b4a99 (patch) | |
tree | 64ac9e3885d22043acd7a29169104126d602ce31 /drivers/acpi/device_pm.c | |
parent | 0cd6ac52b333f66ee64e50ed216ec99231092dcd (diff) | |
download | op-kernel-dev-11909ca1cf614f9396b17d366f9e3cfcba7b4a99.zip op-kernel-dev-11909ca1cf614f9396b17d366f9e3cfcba7b4a99.tar.gz |
ACPI: Add .setup() and .cleanup() callbacks to struct acpi_bus_type
Add two new callbacks,.setup() and .cleanup(), struct acpi_bus_type
and modify acpi_platform_notify() to call .setup() after executing
acpi_bind_one() successfully and acpi_platform_notify_remove() to
call .cleanup() before running acpi_unbind_one(). This will allow
the users of struct acpi_bus_type, PCI in particular, to specify
operations to be executed right after the given device has been
associated with a companion struct acpi_device and right before
it's going to be detached from that companion, respectively.
The main motivation is to be able to get rid of acpi_pci_bind()
and acpi_pci_unbind(), which are horrible horrible stuff. [In short,
there are three problems with them: The way they populate the .bind()
and .unbind() callbacks of ACPI devices is rather less than
straightforward, they require special hotplug-specific paths to be
present in the ACPI namespace scanning code and by the time
acpi_pci_unbind() is called the PCI device object in question may
not exist any more.]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Acked-by: Toshi Kani <toshi.kani@hp.com>
Diffstat (limited to 'drivers/acpi/device_pm.c')
0 files changed, 0 insertions, 0 deletions