summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorBjorn Helgaas <bjorn.helgaas@hp.com>2009-04-30 09:35:37 -0600
committerLen Brown <len.brown@intel.com>2009-06-18 00:13:14 -0400
commit6d2781310036a8d3fa2b590a6f83a298010fd64a (patch)
treeb10f1e9b275aed0a666786421f636f6fae5cb661 /drivers
parent07a2039b8eb0af4ff464efd3dfd95de5c02648c6 (diff)
downloadlinux-6d2781310036a8d3fa2b590a6f83a298010fd64a.tar.gz
linux-6d2781310036a8d3fa2b590a6f83a298010fd64a.tar.bz2
linux-6d2781310036a8d3fa2b590a6f83a298010fd64a.zip
ACPI: allow drivers to request both device and system notify events
System notify events (0x00-0x7f) are common across all device types and should be handled in Linux/ACPI, not in drivers. However, some BIOSes use system notify events in device-specific ways that require the driver to be involved. This patch adds a ACPI_DRIVER_ALL_NOTIFY_EVENTS driver flag. When a driver sets this flag and supplies a .notify method, Linux/ACPI calls the .notify method for ALL notify events on the device, not just the device-specific (0x80-0xff) events. Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/acpi/bus.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
index ae862f1798dc..cdfecc0a2ac6 100644
--- a/drivers/acpi/bus.c
+++ b/drivers/acpi/bus.c
@@ -549,6 +549,7 @@ static void acpi_bus_notify(acpi_handle handle, u32 type, void *data)
{
int result = 0;
struct acpi_device *device = NULL;
+ struct acpi_driver *driver;
blocking_notifier_call_chain(&acpi_bus_notify_list,
type, (void *)handle);
@@ -629,7 +630,10 @@ static void acpi_bus_notify(acpi_handle handle, u32 type, void *data)
break;
}
- return;
+ driver = device->driver;
+ if (driver && driver->ops.notify &&
+ (driver->flags & ACPI_DRIVER_ALL_NOTIFY_EVENTS))
+ driver->ops.notify(device, type);
}
/* --------------------------------------------------------------------------