From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yinghai@kernel.org>, Toshi Kani <toshi.kani@hp.com>,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug
Date: Wed, 20 Feb 2013 14:27:30 +0100 [thread overview]
Message-ID: <1502998.UgYRH5gaN4@vostro.rjw.lan> (raw)
In-Reply-To: <51232557.2050302@jp.fujitsu.com>
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@intel.com>
> >>
> >> 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@intel.com>
> >> ---
> >> 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.
next prev parent reply other threads:[~2013-02-20 13:20 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 15:18 [PATCH 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Rafael J. Wysocki
2013-02-17 15:20 ` [PATCH 1/7] ACPI / scan: Introduce acpi_scan_match_handler() Rafael J. Wysocki
2013-02-19 6:48 ` Yasuaki Ishimatsu
2013-02-17 15:21 ` [PATCH 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug Rafael J. Wysocki
2013-02-19 6:43 ` Yasuaki Ishimatsu
2013-02-19 7:10 ` Yasuaki Ishimatsu
2013-02-20 13:27 ` Rafael J. Wysocki [this message]
2013-02-20 13:23 ` Rafael J. Wysocki
2013-02-20 20:23 ` Toshi Kani
2013-02-20 21:17 ` Rafael J. Wysocki
2013-02-20 22:49 ` [Update][PATCH " Rafael J. Wysocki
2013-02-21 1:17 ` Toshi Kani
2013-02-21 15:44 ` Rafael J. Wysocki
2013-02-21 15:52 ` [Update 2][PATCH " Rafael J. Wysocki
2013-02-21 17:39 ` Toshi Kani
2013-02-21 22:57 ` Rafael J. Wysocki
2013-02-21 23:06 ` [Update 3][PATCH " Rafael J. Wysocki
2013-02-22 1:12 ` Toshi Kani
2013-02-22 1:50 ` Rafael J. Wysocki
2013-02-22 8:51 ` Yasuaki Ishimatsu
2013-02-22 12:37 ` Rafael J. Wysocki
2013-02-22 15:54 ` Toshi Kani
2013-02-22 20:59 ` Rafael J. Wysocki
2013-02-23 22:38 ` [Update 4][PATCH " Rafael J. Wysocki
2013-02-25 18:07 ` Toshi Kani
2013-02-25 23:39 ` Rafael J. Wysocki
2013-02-25 23:32 ` Toshi Kani
2013-02-26 0:40 ` Yasuaki Ishimatsu
2013-02-26 1:09 ` Toshi Kani
2013-02-26 2:02 ` Yasuaki Ishimatsu
2013-02-26 3:11 ` Rafael J. Wysocki
2013-02-26 3:40 ` Yasuaki Ishimatsu
2013-02-26 3:50 ` Rafael J. Wysocki
2013-03-04 13:10 ` Vasilis Liaskovitis
2013-03-14 17:16 ` Rafael J. Wysocki
2013-03-15 10:47 ` Vasilis Liaskovitis
2013-03-25 20:45 ` Toshi Kani
2013-03-25 22:29 ` Rafael J. Wysocki
2013-03-25 22:57 ` Toshi Kani
2013-03-26 12:22 ` Rafael J. Wysocki
2013-03-26 20:10 ` Toshi Kani
2013-02-17 15:22 ` [PATCH 3/7] ACPI / container: Use common hotplug code Rafael J. Wysocki
2013-02-17 15:23 ` [PATCH 4/7] ACPI / scan: Introduce acpi_scan_handler_matching() Rafael J. Wysocki
2013-02-19 8:05 ` Yasuaki Ishimatsu
2013-02-17 15:24 ` [PATCH 5/7] ACPI / hotplug: Introduce user space interface for hotplug profiles Rafael J. Wysocki
2013-02-25 18:13 ` Toshi Kani
2013-02-25 23:25 ` Rafael J. Wysocki
2013-02-17 15:25 ` [PATCH 6/7] ACPI / container: Use hotplug profile user space interface Rafael J. Wysocki
2013-02-17 15:27 ` [PATCH 7/7] ACPI / scan: Make memory hotplug driver use struct acpi_scan_handler Rafael J. Wysocki
2013-02-19 18:11 ` Vasilis Liaskovitis
2013-02-20 3:35 ` Yasuaki Ishimatsu
2013-02-20 10:42 ` Vasilis Liaskovitis
2013-02-20 21:50 ` Toshi Kani
2013-02-20 22:29 ` Rafael J. Wysocki
2013-02-20 22:39 ` Toshi Kani
2013-02-21 6:58 ` Yasuaki Ishimatsu
2013-02-26 22:41 ` [PATCH v2, 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Rafael J. Wysocki
2013-02-26 22:44 ` [PATCH v2, 1/7] ACPI / scan: Introduce acpi_scan_match_handler() Rafael J. Wysocki
2013-02-26 22:46 ` [PATCH v2, 2/7] ACPI / scan: Introduce common code for ACPI-based device hotplug Rafael J. Wysocki
2013-02-26 22:46 ` [PATCH v2, 3/7] ACPI / container: Use common hotplug code Rafael J. Wysocki
2013-02-26 23:13 ` Toshi Kani
2013-02-27 0:06 ` Rafael J. Wysocki
2013-02-27 0:09 ` [Update][PATCH " Rafael J. Wysocki
2013-02-26 22:47 ` [PATCH v2, 4/7] ACPI / scan: Introduce acpi_scan_handler_matching() Rafael J. Wysocki
2013-02-26 22:48 ` [PATCH v2, 5/7] ACPI / hotplug: Introduce user space interface for hotplug profiles Rafael J. Wysocki
2013-02-26 22:49 ` [PATCH v2, 6/7] ACPI / container: Use hotplug profile user space interface Rafael J. Wysocki
2013-02-26 22:50 ` [PATCH v2, 7/7] ACPI / scan: Make memory hotplug driver use struct acpi_scan_handler Rafael J. Wysocki
2013-02-27 0:51 ` [PATCH v2, 0/7] ACPI / hotplug: Common code for ACPI-based hotplug Toshi Kani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1502998.UgYRH5gaN4@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=toshi.kani@hp.com \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®