summaryrefslogtreecommitdiffstats
path: root/drivers/acpi/pci_root.c
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-11-22 21:54:52 +0100
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2013-11-22 21:54:52 +0100
commit1ceaba05b4afb4bd7b4b4801f2718c13f59321eb (patch)
treedae70cfea3386cc37b178283479e0bf1f2ee1256 /drivers/acpi/pci_root.c
parent202317a573b20d77a9abb7c16a3fd5b40cef3d9d (diff)
downloadop-kernel-dev-1ceaba05b4afb4bd7b4b4801f2718c13f59321eb.zip
op-kernel-dev-1ceaba05b4afb4bd7b4b4801f2718c13f59321eb.tar.gz
ACPI / hotplug: Do not fail bus and device checks for disabled hotplug
If the scan handler for the given device has hotplug.enabled unset, it doesn't really make sense to fail bus check and device check notifications. First, bus check may not have anything to do with the device it is signaled for, but it may concern another device on the bus below this one. For this reason, bus check notifications should not be failed if hotplug is disabled for the target device. Second, device check notifications are signaled only after a device has already appeared (or disappeared), so failing it can only prevent scan handlers and drivers from attaching to that (already existing) device, which is not very useful. Consequently, if device hotplug is disabled through the device's scan handler, fail eject request notifications only. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'drivers/acpi/pci_root.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud