Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759063Ab2KBMTc (ORCPT ); Fri, 2 Nov 2012 08:19:32 -0400 Received: from ogre.sisk.pl ([193.178.161.156]:52094 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752550Ab2KBMTa (ORCPT ); Fri, 2 Nov 2012 08:19:30 -0400 From: "Rafael J. Wysocki" To: Yinghai Lu Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Jacob Shin , Tejun Heo , Stefano Stabellini , linux-kernel@vger.kernel.org, Tang Chen , Len Brown , linux-acpi@vger.kernel.org Subject: Re: [PATCH 1/3] ACPI: Introduce a new acpi handle to determine HID match. Date: Fri, 02 Nov 2012 13:23:36 +0100 Message-ID: <1952961.jiv6kKxT5N@vostro.rjw.lan> User-Agent: KMail/4.8.5 (Linux/3.7.0-rc3; KDE/4.8.5; x86_64; ; ) In-Reply-To: <1350593430-24470-2-git-send-email-yinghai@kernel.org> References: <1350593430-24470-1-git-send-email-yinghai@kernel.org> <1350593430-24470-2-git-send-email-yinghai@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3208 Lines: 98 On Thursday, October 18, 2012 01:50:09 PM Yinghai Lu wrote: > From: Tang Chen > > We need to find out if one handle is for root bridge, and install notify > handler for it to handle pci root bus hot add. > At that time, root bridge acpi device is not created yet. > > So acpi_match_device_ids() will not work. > > This patch add a function to check if new acpi handle's HID matches a list > of IDs. The new api use acpi_device_info instead acpi_device. > > -v2: updated changelog, also check length for string info... > change checking sequence by moving string comaring close to for loop. > - Yinghai > > Signed-off-by: Tang Chen > Signed-off-by: Yinghai Lu > Cc: Len Brown > Cc: linux-acpi@vger.kernel.org > --- > drivers/acpi/scan.c | 33 +++++++++++++++++++++++++++++++++ > include/acpi/acpi_bus.h | 2 ++ > 2 files changed, 35 insertions(+), 0 deletions(-) > > diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c > index 5dfec09..33ca993 100644 > --- a/drivers/acpi/scan.c > +++ b/drivers/acpi/scan.c > @@ -312,6 +312,39 @@ int acpi_match_device_ids(struct acpi_device *device, > } > EXPORT_SYMBOL(acpi_match_device_ids); > > +int acpi_match_object_info_ids(struct acpi_device_info *info, > + const struct acpi_device_id *ids) > +{ > + const struct acpi_device_id *id; > + char *str; > + u32 len; > + int i; > + > + len = info->hardware_id.length; > + if (len) { > + str = info->hardware_id.string; > + if (str) > + for (id = ids; id->id[0]; id++) > + if (!strcmp((char *)id->id, str)) > + return 0; > + } > + > + for (i = 0; i < info->compatible_id_list.count; i++) { > + len = info->compatible_id_list.ids[i].length; > + if (!len) > + continue; > + str = info->compatible_id_list.ids[i].string; > + if (!str) > + continue; > + for (id = ids; id->id[0]; id++) > + if (!strcmp((char *)id->id, str)) > + return 0; > + } > + > + return -ENOENT; > +} > +EXPORT_SYMBOL(acpi_match_object_info_ids); EXPORT_SYMBOL_GPL, please? > + > static void acpi_free_ids(struct acpi_device *device) > { > struct acpi_hardware_id *id, *tmp; > diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h > index 608f92f..6ac415c 100644 > --- a/include/acpi/acpi_bus.h > +++ b/include/acpi/acpi_bus.h > @@ -374,6 +374,8 @@ int acpi_bus_start(struct acpi_device *device); > acpi_status acpi_bus_get_ejd(acpi_handle handle, acpi_handle * ejd); > int acpi_match_device_ids(struct acpi_device *device, > const struct acpi_device_id *ids); > +int acpi_match_object_info_ids(struct acpi_device_info *info, > + const struct acpi_device_id *ids); > int acpi_create_dir(struct acpi_device *); > void acpi_remove_dir(struct acpi_device *); I wonder which code path(s) is(are) going to use the new routine? 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/