This patchset enables sysfs eject for ACPI scan drivers and registers the ACPI container driver as an ACPI scan driver. This patchset is the one I mentioned in my following reply. Toshi Re: [PATCH 2/2] ACPI / scan: Simplify container driver On Mon, 2013-02-04 at 00:47 +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx> > > The only useful thing that the ACPI container driver does is to > install system notify handlers for all container and module device > objects it finds in the namespace. The driver structure, > acpi_container_driver, and the data structures created by its > .add() callback are in fact not used by the driver, so remove > them entirely. > > It also makes a little sense to build that driver as a module, > so make it non-modular and add its initialization to the > namespace scanning code. > > In addition to that, make the namespace walk callback used for > installing the notify handlers more straightforward. I think the container driver needs to be registered as an ACPI scan driver so that sysfs eject will continue to work for container devices, such as ACPI0004:XX/eject. Since the container driver does not support ACPI eject notification (and we have been discussing how system device hot-plug should work), this sysfs eject is the only way to eject a container device at this point. I will send an update patchset that applies on top of this patch. -- 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
