On Wednesday, October 30, 2013 03:04:16 PM Mika Westerberg wrote: > On Wed, Oct 30, 2013 at 02:01:40PM +0100, Rafael J. Wysocki wrote: > > On Wednesday, October 30, 2013 02:40:36 PM Mika Westerberg wrote: > > > Commit 2dc4128 (ACPI / hotplug / PCI: Avoid doing too much for spurious > > > notifies) changed the enable_slot() to check return value of pci_scan_slot() > > > and if it is zero return early from the function. It means that there were > > > no new devices in this particular slot. > > > > > > However, if a device appeared deeper in the hierarchy the code now ignores > > > it causing things like Thunderbolt chaining fail to recognize new devices. > > > > > > The problem with Alex Williamson's machine was solved with commit > > > a47d8c8 (ACPI / hotplug / PCI: Avoid parent bus rescans on spurious device > > > checks) and hence we should be able to restore the original functionality > > > that we always rescan on bus check notification. > > > > > > On a device check notification we still check what acpiphp_rescan_slot() > > > returns and on zero bail out early. > > > > > > Signed-off-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> > > > > So, this is a revert of commit a47d8c8, correct? > > Correct. > > Plain revert didn't work because the code has changed after that commit. Yeah. Well, it would be good to know if it affects the Alex' system, but anyway I added it to the 3.13 queue for now. We may be able to get it into 3.12 if Alex confirms that it works for him shortly, but if that doesn't happen we can just ask stable to pick it up later. Thanks! -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
