On Monday 28 August 2006 08:12, Yasunori Goto wrote:
> > Am Fr 25.08.2006 13:59 schrieb Yasunori Goto <y-goto@xxxxxxxxxxxxxx>:
> Ok. Followings are current my understanding of sequence
> with your patch.
>
> At boot time, acpi_memory_device_init() is called.
>
> acpi_memory_device_init()
> |
> +---> acpi_bus_register_driver()
> |
> +---> acpi_driver_attach()
> |
> +---> acpi_bus_driver_init()
> |
> +---> acpi_memory_device_add()
> |
> +---> acpi_install_notify_handler().
>
>
> The problem is in acpi_driver_attach(). This function is using
> "acpi_device_list" to call acpi_bus_driver_init().
>
> This list is registered by acpi_device_register() which is called by
> acpi_add_single_object().
> However, acpi_add_single_object() skips calling it if _STA is not on.
>
> 1015 switch (type) {
> 1016 case ACPI_BUS_TYPE_PROCESSOR:
> 1017 case ACPI_BUS_TYPE_DEVICE:
> 1018 result = acpi_bus_get_status(device);
> 1019 if (ACPI_FAILURE(result) || !device->status.present) {
> 1020 result = -ENOENT;
> 1021 goto end;
> 1022 }
> 1023 break;
>
> So, notify handler is registered just for memory device which is enable
> at boot time.
> If notify event occurs for new memory device, there is no notify handler
> for it....
I looked at this over a year ago, and my feeble recollection is
that if _STA says "not present", we don't do the device_add. Later,
when _STA changes to "present", we get an ACPI notification. I
expected that we would just do the device_add() at that time, and
there are even comments in acpi_bus_check_device() that suggest that,
but it just looks unfinished.
It seemed like it would be much cleaner to finish that up, and then
the driver's .add method would automatically get called, and the
memory driver wouldn't have to bother with all the notification stuff.
Bjorn
-
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
