Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp3148145img; Mon, 25 Mar 2019 04:53:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqzt0aozBt9V7dx83dCvZ/87b+hH/ZqIPz7+YUWtIR1y8djo8lKhA2fMS3vK7h5tr8eoMW+i X-Received: by 2002:a17:902:8a96:: with SMTP id p22mr24139678plo.113.1553514834856; Mon, 25 Mar 2019 04:53:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553514834; cv=none; d=google.com; s=arc-20160816; b=bIp9gq3T+Jd0nCDRAy9CYeIhDSJh/RvboYwjXcWaEGT5dq1g59rB+DIbpSsVUrSyXp JRTOtmA/CQBy4Io0xVlxgxJWsskxOvp3ME8pRsxxW41EKq/ggHfsI2xVC6GXdqGiyyUW P3DSSSYHfEj76nOfxmbOQPiPwpMBh3hJqs7TikC+4xZ/ufyV9O5OvFYr4H5Vd/5aho25 5p2l6MAs2yHI6KpGj1jw6UTuRdXlOcrcINBB6LwJfoVYx8y0pzG6pwAwnQg2VPcb2gC/ LBSsDbxbWTSdCsvg5zT45m0SC+ycdinAqgQDTxHOLnqo0NWdBJweD6E5P/i0EFHrYLD3 p5fA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=70qQ/CubgPmvjyZyI2dmh7EYKrmgSRvzC1cFMfmNvtw=; b=VW3sNOLzGiRAZ4gKcfQ+9JaB3XdhJeeoD23+cu3ApBUOLu3KD99/whz9HQuK99RI86 BWSZ5quB/AY+hTC/+D4wRk8V/5d5i8SbfVaSb0GIFvDMaLwltdkFy4oij5IPM92Ht4F3 94OwVMCWt5VWOmDn/NNVTPlnKFxRZ/euYP1eGK/sD7LTR88nFkF76OgV1p0W+NIGlJmp HfOwJd/lT8BUBwxdD44NB9RTb+nFm5sOLoIVJywrlTuyODoG5HtkRZKgms7lc/qGL7Tc qdcX88K/te1c1Ic4jHzob+57Jplw/7gf2MA/4QiI4QD9NpCjHWL5wYYAgYQRy+vtuqLf 8cvw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d34si14579991pld.314.2019.03.25.04.53.39; Mon, 25 Mar 2019 04:53:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731014AbfCYLvW (ORCPT + 99 others); Mon, 25 Mar 2019 07:51:22 -0400 Received: from mga01.intel.com ([192.55.52.88]:64326 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730831AbfCYLvV (ORCPT ); Mon, 25 Mar 2019 07:51:21 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Mar 2019 04:51:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,256,1549958400"; d="scan'208";a="330460711" Received: from smile.fi.intel.com (HELO smile) ([10.237.72.86]) by fmsmga006.fm.intel.com with ESMTP; 25 Mar 2019 04:51:19 -0700 Received: from andy by smile with local (Exim 4.92) (envelope-from ) id 1h8O8M-0005AY-A3; Mon, 25 Mar 2019 13:51:18 +0200 Date: Mon, 25 Mar 2019 13:51:18 +0200 From: Andy Shevchenko To: "Rafael J. Wysocki" Cc: Thomas Preston , Mika Westerberg , "Rafael J. Wysocki" , Len Brown , ACPI Devel Maling List , Linux Kernel Mailing List Subject: Re: [PATCH] Documentation: acpi: Add an example for PRP0001 Message-ID: <20190325115118.GP9224@smile.fi.intel.com> References: <20190322134705.27994-1-thomas.preston@codethink.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 25, 2019 at 10:31:13AM +0100, Rafael J. Wysocki wrote: > On Fri, Mar 22, 2019 at 2:47 PM Thomas Preston > wrote: > > > > Add an example for the magic PRP0001 device ID which allows matching > > ACPI devices against drivers using OF Device Tree compatible property. > > It wasn't clear to me that PRP0001 could be used in _CID. > > Mika, Andy, can you have a look at this, please? Good to me, Reviewed-by: Andy Shevchenko Though one thing I would like to add (not directly related to the patch per se), i.e. it would be nice to keep such examples under meta-acpi [1] umbrella as a database for such excerpts. Thomas, can you do that? [1]: https://github.com/westeri/meta-acpi > > Signed-off-by: Thomas Preston > > --- > > Documentation/acpi/enumeration.txt | 27 +++++++++++++++++++++++++++ > > 1 file changed, 27 insertions(+) > > > > diff --git a/Documentation/acpi/enumeration.txt b/Documentation/acpi/enumeration.txt > > index 7bcf9c3d9fbe..391db643065a 100644 > > --- a/Documentation/acpi/enumeration.txt > > +++ b/Documentation/acpi/enumeration.txt > > @@ -410,6 +410,33 @@ Specifically, the device IDs returned by _HID and preceding PRP0001 in the _CID > > return package will be checked first. Also in that case the bus type the device > > will be enumerated to depends on the device ID returned by _HID. > > > > +For example, the following ACPI sample might be used to enumerate an lm75-type > > +I2C temperature sensor and match it to the driver using the Device Tree > > +namespace link: > > + > > + Device (TMP0) > > + { > > + Name (_HID, "TITMP75") /* _HID will appear in sysfs */ > > + Name (_CID, "PRP0001") > > + Name (_DSD, Package() { > > + ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), > > + Package () { > > + Package (2) { "compatible", "ti,tmp75" }, > > + } > > + }) > > + Method (_CRS, 0, Serialized) > > + { > > + Name (SBUF, ResourceTemplate () > > + { > > + I2cSerialBusV2 (0x48, ControllerInitiated, > > + 400000, AddressingMode7Bit, > > + "\\_SB.PCI0.I2C1", 0x00, > > + ResourceConsumer, , Exclusive,) > > + }) > > + Return (SBUF) > > + } > > + } > > + > > It is valid to define device objects with a _HID returning PRP0001 and without > > the "compatible" property in the _DSD or a _CID as long as one of their > > ancestors provides a _DSD with a valid "compatible" property. Such device > > -- > > 2.11.0 > > -- With Best Regards, Andy Shevchenko