Re: [PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug

From: Rafael J. Wysocki
Date: Wed Feb 20 2013 - 08:20:59 EST


On Tuesday, February 19, 2013 04:10:15 PM Yasuaki Ishimatsu wrote:
> 2013/02/19 15:43, Yasuaki Ishimatsu wrote:
> > Hi Rafael,
> >
> > I have comments. Please see below.
> >
> > 2013/02/18 0:21, Rafael J. Wysocki wrote:
> >> From: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
> >>
> >> Multiple drivers handling hotplug-capable ACPI device nodes install
> >> notify handlers covering the same types of events in a very similar
> >> way. Moreover, those handlers are installed in separate namespace
> >> walks, although that really should be done during namespace scans
> >> carried out by acpi_bus_scan(). This leads to substantial code
> >> duplication, unnecessary overhead and behavior that is hard to
> >> follow.
> >>
> >> For this reason, introduce common code in drivers/acpi/scan.c for
> >> handling hotplug-related notification and carrying out device
> >> insertion and eject operations in a generic fashion, such that it
> >> may be used by all of the relevant drivers in the future. To cover
> >> the existing differences between those drivers introduce struct
> >> acpi_hotplug_profile for representing collections of hotplug
> >> settings associated with different ACPI scan handlers that can be
> >> used by the drivers to make the common code reflect their current
> >> behavior.
> >>
> >> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@xxxxxxxxx>
> >> ---
> >> drivers/acpi/scan.c | 271 +++++++++++++++++++++++++++++++++++++-----------
> >> include/acpi/acpi_bus.h | 7 +
> >> 2 files changed, 220 insertions(+), 58 deletions(-)
> >>
[...]
>
> >> +static void acpi_scan_bus_device_check(acpi_handle handle, u32 ost_source)
> >> +{
> >> + struct acpi_device *device = NULL;
> >> + u32 ost_code = ACPI_OST_SC_NON_SPECIFIC_FAILURE;
> >> + int error;
> >> +
> >> + mutex_lock(&acpi_scan_lock);
> >> +
> >> + acpi_bus_get_device(handle, &device);
> >> + if (device) {
> >> + dev_warn(&device->dev, "Attempt to re-insert\n");
> >> + goto out;
> >> + }
> >> + acpi_evaluate_hotplug_ost(handle, ost_source,
> >> + ACPI_OST_SC_INSERT_IN_PROGRESS, NULL);
> >> + ost_source = ACPI_OST_EC_OSPM_INSERTION;
> >> + error = acpi_bus_scan(handle);
> >> + if (error) {
> >> + acpi_handle_warn(handle, "Namespace scan failure\n");
> >> + goto out;
> >> + }
> >> + error = acpi_bus_get_device(handle, &device);
> >> + if (error) {
> >> + acpi_handle_warn(handle, "Missing device node object\n");
> >> + goto out;
> >> + }
> >> + ost_code = ACPI_OST_SC_SUCCESS;
> >> + if (device->handler && device->handler->hotplug.uevents)
> >> + kobject_uevent(&device->dev.kobj, KOBJ_ONLINE);
> >>
> >> out:
> >> + acpi_evaluate_hotplug_ost(handle, ost_source, ost_code, NULL);
> >> + mutex_unlock(&acpi_scan_lock);
> >> +}
>
> Why don't you check _STA method in acpi_scan_bus_device_check()?
> When hot adding new device, we must check _STA method of the device.

Yes, which is going to happen in acpi_bus_scan().

Thanks,
Rafael


--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/