Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp889794ybp; Wed, 9 Oct 2019 05:55:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqz7jsg2RcMLrg1pWjmSVDAKbJvLChXZ70elzUjD5XZSKzSGBEnXM8eloabn5LnJLAJtwPCB X-Received: by 2002:a17:906:a442:: with SMTP id cb2mr2679843ejb.163.1570625720925; Wed, 09 Oct 2019 05:55:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570625720; cv=none; d=google.com; s=arc-20160816; b=Pu+N1WwWxtZrcPiy0uuv8AYH0MaCcXTC2q06frnBJynTVIS+jPfdkARt7CSQJcKTd2 yJgcoxTjnly/cj5sGtEZHW7R58DMJLqUtMrsuduTiHU2R+GZfNmK2rBHrtITD0mzqNoG 7E5QmyN1tVdn8tIaC38EsOyC1qB/Eca4VN2eQnfsCsXDOMoOltXxvEXnFEfB0dsF5vZH l08iKnPe3P6mnOg0cQ40zFhWGa/RaVaX3wnmyrrXkLJB6aBNnpmP9GuhC0RnIahCtttd G5rmDfgIHNlO7fhs1cWEgHFEg3VNNt7dzlnHktjeZrA+ejw3ic2oKGQusLEMwip5UtTw KBwQ== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:dkim-signature; bh=TgY7kPmBZqnecD8fmdALLpGAi+Y1sBS44TN0W3OZTbI=; b=iql+sYu+p9+CIfEm1ybv3kZ9+tBmfDHL52SH7oIjHMDMWWko9u6xOxlbdGF6exjMBf 6jFXn99+P071ifvMHcJ8N6peh2/wo0zGV9EDRb2gEnW0CNfZIi+fUXIZMxwb1XwdkvPO ZrKvy7I37OlmecuWq8SdPBrTTkMM58BeSVHLlPUCaRRAZ3zdaM+QVTKaRtqH42NOHDlY fAbeTek/9tg6+2pbUeZ+sOJczY5FMKyoPpsrID7C3B0A7zxxXroVbSxGAecHzoCFLeER /nmVbpp8TZIDeZKjfalaeiu/UGUggvFL6LLySRhlhZx4iiRvvHxrhtM+1eJ1NMDPPQgc yWqw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ieth1LzW; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b11si1056619eja.38.2019.10.09.05.54.57; Wed, 09 Oct 2019 05:55:20 -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; dkim=pass header.i=@linaro.org header.s=google header.b=Ieth1LzW; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731224AbfJIMyk (ORCPT + 99 others); Wed, 9 Oct 2019 08:54:40 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:35839 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731215AbfJIMyk (ORCPT ); Wed, 9 Oct 2019 08:54:40 -0400 Received: by mail-qt1-f196.google.com with SMTP id m15so3249587qtq.2 for ; Wed, 09 Oct 2019 05:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=TgY7kPmBZqnecD8fmdALLpGAi+Y1sBS44TN0W3OZTbI=; b=Ieth1LzWB3tqDdxRYS6TrTDImdY44X93i3yUuyswKh9NjwTJ9MG4I2p3ASCGRBbhIi EN685xkM080/OSbNL3HVipQhMTiUC3wCskwGs71Fi0G583KGpAhgDjb9VZTSwNOizajq KjMDn74QgrW5rjxwCxpxgHrztK5XKLYGw7Ptb6Dzw2Um68uQEEtb9QD58DgmCL+djw5x hvj6SPb+jQ8H91BafRWYx9bXKeCGoUZ3pYmo9zaWEqj9Hbxyx5PkknrLQpIrt+b6pPv2 UWqyEnjMQk6gtxIgsg+zv6Xm7CfObViLTHWCh+F8QEAs8uzXv+iWzUnHp4NYkK8A+eno 2GbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=TgY7kPmBZqnecD8fmdALLpGAi+Y1sBS44TN0W3OZTbI=; b=CFRZypudoZOcrdsM+Bk1l2aDXpsRAVfwXlo/rtwSplu7t8b/UpujX8r80WrznCBMqn ipbnLM7FQ3Hs0INdQfNfADHyVtBkkkVZAe1NJKmDOJP+zsuCFG3TTg1Fa3urRriN6app pDKqvM4c3SpF8GZuxZ4M63B7iyiszjTrPZF2eJr4SNthGscnoygcBYAwzPpHDDIutXtz lA7nqkuh8txIAcigONcHw2UpBN7zFr2F4YLjttQRZ8K9m7j0WnN9LhvzzVZpONN+R6O6 ydTWZ/I6KkpLKs7NqLf1+XXNJ+TALuRrUkxLFXhXCXxUbW9oO2C2CEz1kVfvQiwP/82C qnag== X-Gm-Message-State: APjAAAUHPUvd9hH5YfLjS/L5NIcMQsKNBvHF4HEhkCQ8lLlU/5aeTGiL tq1KjNX+vb58lKyi1agV15hiDhunGu9GNg== X-Received: by 2002:a0c:ef85:: with SMTP id w5mr3460733qvr.159.1570625678531; Wed, 09 Oct 2019 05:54:38 -0700 (PDT) Received: from [192.168.1.169] (pool-71-255-246-27.washdc.fios.verizon.net. [71.255.246.27]) by smtp.gmail.com with ESMTPSA id c201sm890854qke.128.2019.10.09.05.54.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Oct 2019 05:54:37 -0700 (PDT) Subject: Re: [PATCH 1/4] dt-bindings: thermal: Introduce monitor-falling parameter to thermal trip point binding To: Rob Herring References: <1568859503-19725-1-git-send-email-thara.gopinath@linaro.org> <1568859503-19725-2-git-send-email-thara.gopinath@linaro.org> <5d93ce86.1c69fb81.70b0d.ba56@mx.google.com> Cc: rui.zhang@intel.com, edubezval@gmail.com, daniel.lezcano@linaro.org, vincent.guittot@linaro.org, bjorn.andersson@linaro.org, amit.kucheria@verdurent.com, mark.rutland@arm.com, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org From: Thara Gopinath Message-ID: <5D9DD88C.7090804@linaro.org> Date: Wed, 9 Oct 2019 08:54:36 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <5d93ce86.1c69fb81.70b0d.ba56@mx.google.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, Thanks for the review. On 10/01/2019 06:09 PM, Rob Herring wrote: > On Wed, Sep 18, 2019 at 10:18:20PM -0400, Thara Gopinath wrote: >> Introduce a new binding parameter to thermal trip point description >> to indicate whether the temperature level specified by the trip point >> is monitored for a rise or fall in temperature. > > What if it is both? > > When do you need this? Seems like you'd always want to monitor both > directions to undo any action done on rising temp. Unless you want a > hysteresis, but this doesn't seem like the best way to implement that. > The thermal framework is designed in such a manner that I cannot think of a use case for both. The framework takes care of removing the warming/cooling action when the trip point is crossed in the opposite direction. It only needs an indication on when to start implementing the action. For eg. When the temperature crosses/increases above 90 degree, the framework will start the cooling action and will continue monitoring till the temperature falls below 90 and the cooling action is removed. Vice versa when the temperature decreases below say 5 degree, the framework should initiate the warming action and monitor till the temperature rises above and remove the warming action. So the trip point is really an indication of the temperature crossing a threshold in the specified direction. Now this parameter is needed to indicate whether the thermal framework has to start implementing the warming/cooling action when the temperature rises above the trip point or falls below the trip point. Till now the framework was always assuming that the cooling action had to be implemented when temperature rises above the trip point. -- Warm Regards Thara