Received: by 2002:a05:6358:45e:b0:b5:b6eb:e1f9 with SMTP id 30csp524445rwe; Thu, 1 Sep 2022 03:47:34 -0700 (PDT) X-Google-Smtp-Source: AA6agR5ltyyTztkrQsnTQtfh3f0QE0ZeEr2J3WTxmkD7xB6L1E+bMNlTCZdWhLk8TdOsegjJXxEc X-Received: by 2002:a17:90b:1810:b0:1fd:b639:fd99 with SMTP id lw16-20020a17090b181000b001fdb639fd99mr8214275pjb.78.1662029254249; Thu, 01 Sep 2022 03:47:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662029254; cv=none; d=google.com; s=arc-20160816; b=OtWWjrSd98QwGJU6H0ZrA10mZLXeejl+EeFRgc6D4hqSKmP4QExL5/zZ+D0i7SzPsi PcoJQHzfaEcu8Wjsk9PREfq6aexq/SUXZsEZT1HSUeEbRjOFN6MfwQT0a+WxLYkoYh5J htFgXBGxMrBrx8HHz0PXakP/yPYqrAN4ZuigYUWMdUsOvxviTaFG4kluLOVsn0BXJT5n daQ++k4y362ADAkkB6zN9Vgd6EaJW3fu441aeLNdRq5zsyzGQdV2VPP5RyScTf9/xhnJ eLmebISuYd6/z4bwXqZWLJgMg+euRHnSEz3i8o7wgK0P576S6Ibl37nNesu6/dJYiLGz 642w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=YgPjD6MSjghO0JcDONrTyByupxn3RtV2IwkzsjXHv6o=; b=pMUdo/nbmGjpB9BwIkuQlNngr7v+iupGuFU1IYxnsfpy8oOCGVrmSKafN69DIWLOkj Fs+yGfcDr3ruDIVR2Laim7DT8vkoNvo2JaEzaqc6w8ioNfxNoeZkCbhDWGpwhSBW0RtN 2/Ep0QqObTxuIGMxjF+2bEmgsbwrQ313UUvGaXKVKDcqAWr8yCYfvhVCHB3yEQeQOtD8 pPuG1ZBondmjr2J44x8WaIpYQ7bFuqHrwiHEM6+VqZTGOW4XizUQ2KB9lpmPgTdefTGV KlW/4JRtIpxKQcM2svqX2BBFZszY1FUZRhrQz2Z+fYFaGjNNFD9mwSi7nJ3uGvXvKwxx yC/w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id r22-20020a170902be1600b00170d3ae4678si15955842pls.216.2022.09.01.03.47.22; Thu, 01 Sep 2022 03:47:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233319AbiIAKOJ (ORCPT + 99 others); Thu, 1 Sep 2022 06:14:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57646 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231343AbiIAKOI (ORCPT ); Thu, 1 Sep 2022 06:14:08 -0400 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1CBF8130A29; Thu, 1 Sep 2022 03:14:07 -0700 (PDT) Received: from fraeml740-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4MJH1c0PmLz67mqV; Thu, 1 Sep 2022 18:13:24 +0800 (CST) Received: from lhrpeml500005.china.huawei.com (7.191.163.240) by fraeml740-chm.china.huawei.com (10.206.15.221) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 1 Sep 2022 12:14:05 +0200 Received: from localhost (10.202.226.42) by lhrpeml500005.china.huawei.com (7.191.163.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Thu, 1 Sep 2022 11:14:04 +0100 Date: Thu, 1 Sep 2022 11:14:03 +0100 From: Jonathan Cameron To: Robert Richter CC: Alison Schofield , Vishal Verma , Ira Weiny , Ben Widawsky , Dan Williams , , , Bjorn Helgaas , "Rafael J. Wysocki" , Len Brown Subject: Re: [PATCH 07/15] cxl/acpi: Check RCH's PCIe Host Bridge ACPI ID Message-ID: <20220901111403.00003bff@huawei.com> In-Reply-To: References: <20220831081603.3415-1-rrichter@amd.com> <20220831081603.3415-8-rrichter@amd.com> <20220831112028.00002566@huawei.com> X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.29; i686-w64-mingw32) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.202.226.42] X-ClientProxiedBy: lhrpeml500006.china.huawei.com (7.191.161.198) To lhrpeml500005.china.huawei.com (7.191.163.240) X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 1 Sep 2022 08:16:52 +0200 Robert Richter wrote: > On 31.08.22 11:20:28, Jonathan Cameron wrote: > > Robert Richter wrote: > > > > +static const struct acpi_device_id cxl_host_ids[] = { > > > + { "ACPI0016", 0 }, > > > + { "PNP0A08", 0 }, > > > + { }, > > > > Trivial but no comma after a null terminator. Always good to make > > it harder for people to add things where they really shouldn't! > > Can do this. > > > pci_root.c avoids using an acpi_device_id table for similar matching. > > I think the point being to separate probe type use of this table > > from cases where we aren't using a normal device probe. > > So to remain consistent with that, I would just grab the hid > > and match it directly in this code. > > Grabbing the hid only is actually a violation of the acpi spec as a > cid could be used interchangeable. It must also work then. > > It is also not possible to use something like probe or a handler > matching the ids because the hosts must be enabled with the already > existing drivers and handlers. Suppose there are multiple handlers for > the same ids, the first handler wins and all other never get called. > > To me it looks sane and simple to use acpi_match_device_ids() here. Ok. One for the ACPI maintainers to comment on if they wish - I'm fine with this Reviewed-by: Jonathan Cameron > > -Robert > > > > > I don't feel that strongly about this if the ACPI maintainers are > > fine with reusing this infrastructure as you have it here.