Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1069246ybl; Thu, 12 Dec 2019 09:10:21 -0800 (PST) X-Google-Smtp-Source: APXvYqz6+T+9VXDNJOTU0nBBiBl8BAG630kfnqAaKxDi/xXMEYAPVkARAHid8iabh6tBiadVkytT X-Received: by 2002:aca:75d7:: with SMTP id q206mr5821695oic.9.1576170621246; Thu, 12 Dec 2019 09:10:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576170621; cv=none; d=google.com; s=arc-20160816; b=xKgLuxjlm8XQ0/dLlfhWxsaplfepy59TwgK44aQDEXjrUXeWnzcHZsW+NkgegcErpm FW8BOQNZBVd3tEYnq5ZJiBCH2jt597Ohr0OSqRi19aaylwBO8nNNCzc0jIhVGdL4Oz2O YyC4D0hlLxGlVYPrTOoKOEyfdIey18ANtgJanaVUWm+2uVQ+AgWhGgy0blup0CXvtjkz XVKrhoNZOyaIEZgazv547CbOsM9UW3AuYf1INIKSZDUrCi0Dw5hjnDSLfbDHZFJJbfoQ jxZwhZjwf/kQ+yZBwYb/8pFgcIoJEqwW8nLmaubHhtz+Vz8AK+JZiYPxRPE9uto/lAWW MPjw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=gtV1kMMZOt9BBy7gC33kLI2d+FIAWgyItD6+NoqJfrk=; b=JMTGJQ/oqsPvKKIIOsgGp4OtL1sFWKhwBIUddIFE5tCjCYAV6vvI470AbvGRNtj7qn wLlWNW1JPms1PX1kpf0cmwY6NNbql68kZlgzTvfOOxMwi1Vw1ACR/YkqUICU0UqkCMds snVs2huItEsqFH6w9mEZgkLMPyM7sfg0Ep5jRHEqoBiQneOsYMqB31B+/cPjvIl26MSJ SgrL3shmNhxcPHV645iqlFNj4alPy2gbxoB47B7P1Nl0ChVBaSoI9B1+EOq9agJYdE7Y kCbJfVc4mAtkvl0wYkByoAVKRX+L6MWicRriyRrgSoHpuKYqi58PJvJ1CGzcfsjjHUMY hD7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=dTe1qHDg; 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 t138si3546671oif.189.2019.12.12.09.09.49; Thu, 12 Dec 2019 09:10:21 -0800 (PST) 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; dkim=pass header.i=@verdurent-com.20150623.gappssmtp.com header.s=20150623 header.b=dTe1qHDg; 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 S1730062AbfLLRH5 (ORCPT + 99 others); Thu, 12 Dec 2019 12:07:57 -0500 Received: from mail-vs1-f66.google.com ([209.85.217.66]:33607 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729804AbfLLRH5 (ORCPT ); Thu, 12 Dec 2019 12:07:57 -0500 Received: by mail-vs1-f66.google.com with SMTP id n27so2109058vsa.0 for ; Thu, 12 Dec 2019 09:07:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verdurent-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gtV1kMMZOt9BBy7gC33kLI2d+FIAWgyItD6+NoqJfrk=; b=dTe1qHDgLCR3hFu1EHejH8zrr86ot3OrTdrb4hX3GDCDalgvGAI0D0IdxMebsmoh4i ybVXyOHUfPN5oscxefXKWtPPpITIZy2Mxgwm8jJygqwur2QCeIE0ueL9g2M2QpxOW/r4 uG5ZStInuYc7aa4Z6E/UvUu4VHBpyz5Oau0YBWQ4RnrLWrqtLVLB2Vl/7OCq4+v+6pjF 7T2kSPkjFQsnSLk4BMIvf91+LclznDss+7GprVZK/xaBpsz2klJac3LXn0eMXBwlDf4z DuDr4WsbXrXD9vSHjR2u4U8OY5BQkmclsGTb8ZC78Dyruc6uJG9tzm5OySn/VpgBT3oE rKQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gtV1kMMZOt9BBy7gC33kLI2d+FIAWgyItD6+NoqJfrk=; b=GOzXdeAP8dwuSo44h+5GGF4OrdKFUKgIWMBhiPXfFQ0jskORVkr4XoB8M3BSLisTYV J94lJGTNSMS56zl8SYlmA/9iS+XFabT3pRrtLJXE32NTnPkjHdJUjoD++65YciZ6Pie0 zuZyWoRZabLHPVTGSzjFm68Cj0x96CYB4g39GItPIMkoz4N0jbgEiM/CJTf38gBGkVA2 ojxLqAa7CcEJnBBjK2rUApu9UTCZa9Wrp9d41oZ6ZRbasOZ4se1FWJ5nQeeqvArERqK0 0unOuYnAaFKOVExHlwgqbySG1eO3yzT1V21tbYY7H7xCyTzR1AKEXzIOqzqc5zi1XMka 98Ow== X-Gm-Message-State: APjAAAUbDhZ9ljSI9WllcoS3aYSKPjmwVedOt4E35GLxOAmQpqKL1ulz kdmtAWA5M94uekPHhoCd6l3gd1yFBZuJ1Kc8aGVkcQ== X-Received: by 2002:a67:fb41:: with SMTP id e1mr7474596vsr.159.1576170476104; Thu, 12 Dec 2019 09:07:56 -0800 (PST) MIME-Version: 1.0 References: <1574934847-30372-1-git-send-email-rkambl@codeaurora.org> <1574934847-30372-2-git-send-email-rkambl@codeaurora.org> In-Reply-To: From: Amit Kucheria Date: Thu, 12 Dec 2019 22:37:45 +0530 Message-ID: Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: sc7180: Add device node support for TSENS in SC7180 To: Doug Anderson Cc: Rajeshwari , Andy Gross , Bjorn Andersson , Rob Herring , Mark Rutland , linux-arm-msm , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML , sivaa@codeaurora.org, sanm@codeaurora.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 12, 2019 at 10:30 PM Doug Anderson wrote: > > Hi, > > On Thu, Dec 12, 2019 at 8:56 AM Amit Kucheria > wrote: > > > > On Thu, Dec 12, 2019 at 9:39 PM Doug Anderson wrote: > > > > > > Hi, > > > > > > On Thu, Dec 12, 2019 at 3:00 AM Amit Kucheria > > > wrote: > > > > > > > > Hi Rajeshwari, > > > > > > > > On Thu, Nov 28, 2019 at 3:25 PM Rajeshwari wrote: > > > > > > > > > > Add TSENS node and user thermal zone for TSENS sensors in SC7180. > > > > > > > > > > Signed-off-by: Rajeshwari > > > > > --- > > > > > arch/arm64/boot/dts/qcom/sc7180.dtsi | 527 +++++++++++++++++++++++++++++++++++ > > > > > 1 file changed, 527 insertions(+) > > > > > > > > > > diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > index 666e9b9..6656ffc 100644 > > > > > --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi > > > > > @@ -911,6 +911,26 @@ > > > > > status = "disabled"; > > > > > }; > > > > > > > > > > + tsens0: thermal-sensor@c263000 { > > > > > + compatible = "qcom,sc7180-tsens","qcom,tsens-v2"; > > > > > + reg = <0 0x0c263000 0 0x1ff>, /* TM */ > > > > > + <0 0x0c222000 0 0x1ff>; /* SROT */ > > > > > + #qcom,sensors = <15>; > > > > > + interrupts = ; > > > > > + interrupt-names = "uplow"; > > > > > + #thermal-sensor-cells = <1>; > > > > > + }; > > > > > + > > > > > + tsens1: thermal-sensor@c265000 { > > > > > + compatible = "qcom,sc7180-tsens","qcom,tsens-v2"; > > > > > + reg = <0 0x0c265000 0 0x1ff>, /* TM */ > > > > > + <0 0x0c223000 0 0x1ff>; /* SROT */ > > > > > + #qcom,sensors = <10>; > > > > > + interrupts = ; > > > > > + interrupt-names = "uplow"; > > > > > + #thermal-sensor-cells = <1>; > > > > > + }; > > > > > + > > > > > spmi_bus: spmi@c440000 { > > > > > compatible = "qcom,spmi-pmic-arb"; > > > > > reg = <0 0x0c440000 0 0x1100>, > > > > > @@ -1121,6 +1141,513 @@ > > > > > }; > > > > > }; > > > > > > > > > > + thermal-zones { > > > > > + cpu0-thermal { > > > > > + polling-delay-passive = <250>; > > > > > + polling-delay = <1000>; > > > > > + > > > > > + thermal-sensors = <&tsens0 1>; > > > > > + > > > > > + trips { > > > > > + cpu0_alert0: trip-point0 { > > > > > + temperature = <90000>; > > > > > + hysteresis = <2000>; > > > > > + type = "passive"; > > > > > + }; > > > > > + > > > > > + cpu0_alert1: trip-point1 { > > > > > + temperature = <95000>; > > > > > + hysteresis = <2000>; > > > > > + type = "passive"; > > > > > + }; > > > > > + > > > > > + cpu0_crit: cpu_crit { > > > > > + temperature = <110000>; > > > > > + hysteresis = <1000>; > > > > > + type = "critical"; > > > > > + }; > > > > > > > > Where are the cooling maps for all the cpu thermal zones? A passive > > > > trip point w/o a cooling map is not of much use. If you are waiting > > > > for cpufreq support to land before adding them, then remove the > > > > passive trip points for now and add them along with the cooling maps > > > > when you have cooling devices. > > > > > > I will note that cpufreq support has landed in the qcom tree:: > > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=86899d8235ea0d3d7c293404fb43a6fabff866e6 > > > > > > ...so I guess the right thing is to send a patch adding the cooling > > > maps for the cpu thermal zones? > > > > Great, then the cooling maps should be added to this patch itself. > > Well, except that this patch itself has also landed: > > https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=82bdc93972bf293c3407cb7fdac163aadfbb2c12 > > ...so I think my advice is still correct: the right thing is to send a > patch adding the cooling maps for the cpu thermal zones In that case, yes.