Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp554029ybb; Wed, 1 Apr 2020 05:27:34 -0700 (PDT) X-Google-Smtp-Source: ADFU+vvsZ2viDskPnjSnY9k2f5cNYf//ILj5JLradUzwl5P5GsSIS2rZvHGQHwmRU/4JX0xDKuwV X-Received: by 2002:a9d:7f05:: with SMTP id j5mr17104753otq.312.1585744054782; Wed, 01 Apr 2020 05:27:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585744054; cv=none; d=google.com; s=arc-20160816; b=URfuIHKjoehesEij82aTB4c3QziLBPKK7YL24agAmewk42v4lOYq5MbMN7e9wvFOzg XEjcW7oyJWb4ZEny64OgRM9t05Olwq/EJOT0z+/s8Nx3THHqtpOzxEHf3iNaORS2UYfz iNx9PEms/ee5BlGfo5JSfL4sZDvbAdVZh5hXHjZtb8dYwk4cZv11cTpmOjneJrn/ABVp xXTmqk68xibL+htGaMLCuESfOt/GzAp27gD2rZNM27ed7rtnjWGnB5ZD40yJbjbdwZn+ UmShdQTLcR9TKKV6QrRdl72IN7D+3xIezRmcSsI9UNKSrVmi9M74yUiFoQOw7zqjhJ+E x9Gw== 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; bh=uv6FHAaNjsdjKCcCxvo/QpeWcDSIfoG6fTWzomrXccE=; b=IQ6P329VuI11ZZUzDif8G7J1bGy/P/dg64CV2rBGJw2cGEDwMBqymEMWxo2JOji22z j+0aXu34YUXzonwVG+R6NWbrktIvS+vgjOj6Jwi9suONIo0cfEqBaIPmOpllWr468u94 YA0GMbdneOur8mt+Wxlyjut5MW86ds/DOHlB5xjev7GSxtyZcIcWpqMYaeXnzQ9L0BYD vQLCrSh0d47R6WPTJnI1ialcMTGI4E2oj/jVbZ8iBRmLAZC05m4BAIVCCduKPDrQArhY xY8z/qaAUvtRLmo8bnYe0/C3+axLkybW+xe4rnqgZ5g3cuiJIORN4vnKg6g3gh1j+8Ke FM6w== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q11si698082oti.46.2020.04.01.05.27.22; Wed, 01 Apr 2020 05:27:34 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732488AbgDAM1D (ORCPT + 99 others); Wed, 1 Apr 2020 08:27:03 -0400 Received: from foss.arm.com ([217.140.110.172]:50510 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726804AbgDAM1D (ORCPT ); Wed, 1 Apr 2020 08:27:03 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 2A7B730E; Wed, 1 Apr 2020 05:27:03 -0700 (PDT) Received: from [10.37.12.63] (unknown [10.37.12.63]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A85E53F68F; Wed, 1 Apr 2020 05:27:00 -0700 (PDT) Subject: Re: [PATCH v4 3/3] dt-bindings: thermal: Add yaml bindings for thermal zones To: Amit Kucheria , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, swboyd@chromium.org, mka@chromium.org, daniel.lezcano@linaro.org, Amit Kucheria , Zhang Rui Cc: Rob Herring , linux-pm@vger.kernel.org, devicetree@vger.kernel.org References: From: Lukasz Luba Message-ID: Date: Wed, 1 Apr 2020 13:26:58 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: 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 Hi Amit, Apart from small mistake during probably copy-paste (please check below), looks good. On 4/1/20 12:15 PM, Amit Kucheria wrote: > As part of moving the thermal bindings to YAML, split it up into 3 > bindings: thermal sensors, cooling devices and thermal zones. > > The thermal-zone binding is a software abstraction to capture the > properties of each zone - how often they should be checked, the > temperature thresholds (trips) at which mitigation actions need to be > taken and the level of mitigation needed at those thresholds. > > Signed-off-by: Amit Kucheria > Reviewed-by: Rob Herring > --- > Changes since v3: > - Clarify example by using cooling state numbers and a comment > - Restrict thermal-sensors to a single reference to reflect actual code > where there is a one-to-one mapping between sensors and thermal zones > - Add two optional properties that were missed in earlier submissions: > coefficients and sustainable-power > - Improve description of hysteresis and contribution properties > > .../bindings/thermal/thermal-zones.yaml | 341 ++++++++++++++++++ > 1 file changed, 341 insertions(+) > create mode 100644 Documentation/devicetree/bindings/thermal/thermal-zones.yaml > [snip] > + cooling-maps { > + map0 { > + trip = <&cpu0_alert0>; > + /* Corresponds to 1400MHz in OPP table */ > + cooling-device = <&CPU0 3 3>, <&CPU1 3 3>, > + <&CPU2 3 3>, <&CPU3 3 3>; > + }; > + > + map1 { > + trip = <&cpu0_alert1>; > + /* Corresponds to 1400MHz in OPP table */ s/1400MHz/1000MHz/ 1400MHZ is used in map0 as <&CPUx 3 3>, here we have '5 5'. > + cooling-device = <&CPU0 5 5>, <&CPU1 5 5>, > + <&CPU2 5 5>, <&CPU3 5 5>; > + }; > + }; > + }; Apart from that, looks good: Reviewed-by: Lukasz Luba Regards, Lukasz