Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp1852431imm; Tue, 22 May 2018 10:20:12 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoqS1GYKeOccK4en08WC/Z5faI5SWyxpguo3KSnkzu5lolO+hGyDR/4cio7VewpOYEYU7re X-Received: by 2002:a17:902:7209:: with SMTP id ba9-v6mr26155825plb.119.1527009612631; Tue, 22 May 2018 10:20:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527009612; cv=none; d=google.com; s=arc-20160816; b=OwCKHD1GqIfRrMGdBmD/T7yvLTfCc4WrmKz8ZuHpLEtc8Nl3uUuB5G4avlfr2BBT3j XKWaS/26kna2++DqVi5iyfqCfQURR0NeYsMZgjAnM81ehPS5nvA0dFblNEaXTeVqitRp 4h3+pj2ufU8dmM4JldKx0FumX7bIIsdFwwXrh0ADlmAbi8wzA1DNHBXrjjuXxaWP/mYU xN3CkKs8YnnIgCXMtzjXqli/FNZjxcQpWGoK8CtThH4tFtnE2W/1OPxsiAd7q7pvbjng mh53niXT43ltDjisRQwjpAwnSK5NFpv2R8IP1r7Rr1aZYe8B+e4pRmo84Qfos+IfSGNA V8Gg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=4Sr6pUuDJwbykTj7rsKtaP7RPeO6cAEAwYfhE3W8dTw=; b=YZZqQoH/L8lRZjhErnqzJjeL40MiMg+emoQ9mywAtsJVOH7QTZyUxCZ+5ddsZUm+kX jYiPYcP/qRsU4Zeg9mQyeO9iPWI1/hWhW79lXlrWdqYsVnDnB81XlInq+YGDNucejtEM 4QmmuaSKZ/Xglpw2YzyNSrvdnBPUjPyIf+QEshiAx5Fn8rz420TYLAhInnyPnTH2KBa8 k/11QKyyPfwpiasV/rENrxn1dmZw8Y4MpaWbkFLPV+P1s/J2vpDga1NJDdr1+Z6iWZ6S h4YUFpqqmE1+8LBBSyH5Xh4NNzHVKFWspwct+P/CWwaTsvMF5XN8oRx2Vsi8jSgCdBwY M0DQ== 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 p12-v6si4457800pgu.358.2018.05.22.10.19.57; Tue, 22 May 2018 10:20:12 -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 S1752525AbeEVRSb (ORCPT + 99 others); Tue, 22 May 2018 13:18:31 -0400 Received: from mga06.intel.com ([134.134.136.31]:39175 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752453AbeEVRS3 (ORCPT ); Tue, 22 May 2018 13:18:29 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 May 2018 10:18:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,430,1520924400"; d="scan'208";a="201534841" Received: from yoojae-mobl1.amr.corp.intel.com (HELO [10.7.153.143]) ([10.7.153.143]) by orsmga004.jf.intel.com with ESMTP; 22 May 2018 10:18:28 -0700 Subject: Re: [v4 07/11] dt-bindings: hwmon: Add documents for PECI hwmon client drivers To: Rob Herring Cc: Mark Rutland , Haiyue Wang , Vernon Mauery , James Feist , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Jeffery , Arnd Bergmann , Jason M Biils , Joel Stanley References: <20180521195905.27983-1-jae.hyun.yoo@linux.intel.com> <20180522164230.GA11707@rob-hp-laptop> From: Jae Hyun Yoo Message-ID: Date: Tue, 22 May 2018 10:18:28 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180522164230.GA11707@rob-hp-laptop> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/22/2018 9:42 AM, Rob Herring wrote: > On Mon, May 21, 2018 at 12:59:05PM -0700, Jae Hyun Yoo wrote: >> This commit adds dt-bindings documents for PECI hwmon client drivers. >> >> Signed-off-by: Jae Hyun Yoo >> Reviewed-by: Haiyue Wang >> Reviewed-by: James Feist >> Reviewed-by: Vernon Mauery >> Cc: Andrew Jeffery >> Cc: Arnd Bergmann >> Cc: Jason M Biils >> Cc: Joel Stanley >> --- >> .../bindings/hwmon/peci-cputemp.txt | 23 ++++++++++++++++++ >> .../bindings/hwmon/peci-dimmtemp.txt | 24 +++++++++++++++++++ >> 2 files changed, 47 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/hwmon/peci-cputemp.txt >> create mode 100644 Documentation/devicetree/bindings/hwmon/peci-dimmtemp.txt >> >> diff --git a/Documentation/devicetree/bindings/hwmon/peci-cputemp.txt b/Documentation/devicetree/bindings/hwmon/peci-cputemp.txt >> new file mode 100644 >> index 000000000000..2f59aee12d9e >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/hwmon/peci-cputemp.txt >> @@ -0,0 +1,23 @@ >> +Bindings for Intel PECI (Platform Environment Control Interface) cputemp driver. >> + >> +Required properties: >> +- compatible : Should be "intel,peci-cputemp". >> +- reg : Should contain address of a client CPU. Address range of CPU >> + clients is starting from 0x30 based on PECI specification. >> + >> +Example: >> + peci-bus@0 { >> + #address-cells = <1>; >> + #size-cells = <0>; >> + < more properties > >> + >> + peci-cputemp@30 { >> + compatible = "intel,peci-cputemp"; >> + reg = <0x30>; >> + }; > > [...] > >> + peci-dimmtemp@30 { >> + compatible = "intel,peci-dimmtemp"; >> + reg = <0x30>; >> + }; > > As I said in the prior version, 2 nodes at the same address is wrong. > > Rob > In PECI bus, there is one and only bus host (adapter) and multiple clients on a PECI bus, and PECI spec doesn't allow multiple originators so only the host device can originate message. In this implementation, all message transactions on a bus from client driver modules and user space will be serialized well in the PECI core bus driver so bus occupation and traffic arbitration will be managed well in the PECI core bus driver even in case of a bus has 2 client drivers at the same address. I'm sure that this implementation doesn't make that kind of problem to OS. Thanks, -Jae