diff options
| author | Kristen Carlson Accardi <kristen.c.accardi@intel.com> | 2007-05-23 14:12:29 -0700 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2007-06-02 00:37:54 -0400 |
| commit | 3f8698d4d3f72252980575fb8d7b4cafeb5dd0a2 (patch) | |
| tree | 5d7e3d7be6c4306026172a5cd7e7f8d82b828361 | |
| parent | 1f9767df1346c9ce09d6e51b9f34b851e3d94fad (diff) | |
ACPI: bay: send envp with uevent
Make the bay driver send env information on bay events.
Upon any bay event, we will send the string "BAY_EVENT=%d" along with the
KOBJ_CHANGE, and report the event number. What the event number means will
be platform specific. Event 3 is always an eject request, but an insert
may be either event 1, or it may be event 0. Event 1 may also be a
remove request. It would be best if you check the number of your event
with udevmonitor before writing any udev scripts for inserting and
removing drive bays.
Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Stephan Berberig <s.berberig@arcor.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
| -rw-r--r-- | drivers/acpi/bay.c | 14 |
1 files changed, 4 insertions, 10 deletions
diff --git a/drivers/acpi/bay.c b/drivers/acpi/bay.c index 00d3f3f17a2..56a5b3fffeb 100644 --- a/drivers/acpi/bay.c +++ b/drivers/acpi/bay.c @@ -333,18 +333,12 @@ static void bay_notify(acpi_handle handle, u32 event, void *data) { struct bay *bay_dev = (struct bay *)data; struct device *dev = &bay_dev->pdev->dev; + char event_string[12]; + char *envp[] = { event_string, NULL }; bay_dprintk(handle, "Bay event"); - - switch(event) { - case ACPI_NOTIFY_BUS_CHECK: - case ACPI_NOTIFY_DEVICE_CHECK: - case ACPI_NOTIFY_EJECT_REQUEST: - kobject_uevent(&dev->kobj, KOBJ_CHANGE); - break; - default: - printk(KERN_ERR PREFIX "Bay: unknown event %d\n", event); - } + sprintf(event_string, "BAY_EVENT=%d\n", event); + kobject_uevent_env(&dev->kobj, KOBJ_CHANGE, envp); } static acpi_status |