Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965099AbbBJOoe (ORCPT ); Tue, 10 Feb 2015 09:44:34 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:49292 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756493AbbBJOob (ORCPT ); Tue, 10 Feb 2015 09:44:31 -0500 From: "Rafael J. Wysocki" To: Mika Westerberg Cc: "Suthikulpanit, Suravee" , Greg Kroah-Hartman , "lenb@kernel.org" , "hdegoede@redhat.com" , "tj@kernel.org" , "arnd@arndb.de" , "mjg59@srcf.ucam.org" , "grant.likely@linaro.org" , "hanjun.guo@linaro.org" , "al.stone@linaro.org" , "graeme.gregory@linaro.org" , "Duran, Leo" , "linux-ide@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linaro-acpi@lists.linaro.org" , Lv Zheng Subject: Re: [V3 PATCH 1/2] ACPI / scan: Add support for ACPI _CLS device matching Date: Tue, 10 Feb 2015 16:07:33 +0100 Message-ID: <2016200.TRfI2dfssZ@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20150210095932.GN1480@lahna.fi.intel.com> References: <20150209111538.GB1480@lahna.fi.intel.com> <20150210095932.GN1480@lahna.fi.intel.com> 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: 2322 Lines: 61 On Tuesday, February 10, 2015 11:59:32 AM Mika Westerberg wrote: > On Mon, Feb 09, 2015 at 09:02:11PM +0000, Suthikulpanit, Suravee wrote: > > On 2/9/15, 19:15, "Mika Westerberg" > > wrote: > > > > >On Mon, Feb 09, 2015 at 12:02:43AM +0100, Rafael J. Wysocki wrote: > > >> On Monday, February 09, 2015 12:20:03 AM Suravee Suthikulpanit wrote: > > >> > Device drivers typically use ACPI _HIDs/_CIDs listed in struct > > >>device_driver > > >> > acpi_match_table to match devices. However, for generic drivers, we do > > >> > not want to list _HID for all supported devices, and some device > > >>classes > > >> > do not have _CID (e.g. SATA, USB). Instead, we can leverage ACPI _CLS, > > >> > which specifies PCI-defined class code (i.e. base-class, subclass and > > >> > programming interface). > > >> > > > >> > This patch adds support for matching ACPI devices using the _CLS > > >>method. > > >> > > > >> > Signed-off-by: Suravee Suthikulpanit > > >> > > >> Greg, Mika, any problems with this? > > > > > >Is there some specific reason why this cannot be done in similar way > > >than PCI already does? > > > > > >In other words, stuff _CLS fields to struct acpi_device_id and make > > >match functions match against those if they are != 0. > > > > That was my original thought. Then I realized that the acpi_device_id is > > used > > to create the device matching table, in which could contain several > > _HID/_CID. > > However, most of the added _CLS field would likely ended up being unused > > and > > taking up space. > > Well, PCI is doing that already :) > > > In contrast to _HID/_CID, a driver is likely to match just a single _CLS. > > So, I think it is cleaner to have just a dedicate struct acpi_device_cls, > > and > > a matching function for it. > > IMHO cleaner version is the one following PCI. I agree. > Besides, how do you support modules with this? Or did I miss something? Good question. -- 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/