Received: by 10.192.165.148 with SMTP id m20csp102586imm; Wed, 9 May 2018 09:26:43 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrxAx5kCDoZ7rF2cvbyCkgoObmA0Ykut/W944YN7QAj0ubCAUZnGQ6+3FQbGgfQkREhSxxs X-Received: by 2002:a17:902:8b89:: with SMTP id ay9-v6mr46403536plb.100.1525883203796; Wed, 09 May 2018 09:26:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525883203; cv=none; d=google.com; s=arc-20160816; b=1KkMLYp+WYoSdF9+HXjA+VXFfmoxBbKrSpu+IlPeePBIJ7zISsQgw4K/NfcCYLAphG ZeKZgNjD7Zd7ZPid2UZlamOvXzBfCNks0JMTm9v3r8TSmuhlQYSBedSebmurAEs/FmMD UsTtIjpTyVcmzqMtjkrAVa+bI+ht9XVhT1oRJlIVYnohpVRYUePrYeqRcqeNJJH84yXU fhRp4OMzJ/ZiT2n8lhbvM6ALR3oAT/oe/ihS32lCzEE/CgQUYD+cWcvZfNqDlpD7+XOf BBr48k5ML7tzF6jvsWvkNJWfK1ZwUgbumGuluFg372UpxdaA1g6E7kwHvngWntCnWWgk pw5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dmarc-filter:dkim-signature:dkim-signature :arc-authentication-results; bh=Bp2bu8xliy7UGmf71bp9iKw+tSQkZmhnKp8z7XaKxxQ=; b=UV9UmZc2c1yIyP9WTcE/4DvKhGAO/rLCSyjGk3p11165fQhnYd8oDQJMhuRWAvxWRE VfZXYyb3//98L09kduLMK7AyBKhUzkaBHwOMoWjgzL0YViWLNk4Kh3IazeHls3r0CpZt Y6IaQpYkByzezOYUIFsqwqUbtwXhEcRVBbdWaWgg+QuOHVRI7lw8wNJTkcMJoU/Hhz6m bRZa/i0cKvLYGPbv1mppOuMVMNvLYoZvkGTec8jq/9fk/CAwBiDoRJI6Fovgito7mW0N MyutjCtHD3Ffk4GL+3vvX8uE16CEI5OGCCgrFjFqtrPlEb7OtUBs3szELOQqOmg2Z23g 6qOg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=QMxfIn7D; dkim=pass header.i=@codeaurora.org header.s=default header.b=QMxfIn7D; 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 c86si27071879pfl.319.2018.05.09.09.26.17; Wed, 09 May 2018 09:26:43 -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=@codeaurora.org header.s=default header.b=QMxfIn7D; dkim=pass header.i=@codeaurora.org header.s=default header.b=QMxfIn7D; 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 S965506AbeEIQZ4 (ORCPT + 99 others); Wed, 9 May 2018 12:25:56 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:40630 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965339AbeEIQZy (ORCPT ); Wed, 9 May 2018 12:25:54 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id BEF0C6081B; Wed, 9 May 2018 16:25:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525883153; bh=Bp2bu8xliy7UGmf71bp9iKw+tSQkZmhnKp8z7XaKxxQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QMxfIn7D4Mmx8DlRpsIJyO+RX0fEt96BCA5dRSti+rdF4niq1BmxbNWLZiQWOZKAV 5gw9XX1Jm89entWyyqPD6fy+ueOeSG8FHCBck/xyKm4u9KnXVmYjlI1fJrwrGUxklO xp+Y1xe/e8QoxPikjOVhL5tnpmlTkWRzuoaaZ+OA= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from localhost (i-global254.qualcomm.com [199.106.103.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: ilina@smtp.codeaurora.org) by smtp.codeaurora.org (Postfix) with ESMTPSA id 074D8605A2; Wed, 9 May 2018 16:25:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525883153; bh=Bp2bu8xliy7UGmf71bp9iKw+tSQkZmhnKp8z7XaKxxQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QMxfIn7D4Mmx8DlRpsIJyO+RX0fEt96BCA5dRSti+rdF4niq1BmxbNWLZiQWOZKAV 5gw9XX1Jm89entWyyqPD6fy+ueOeSG8FHCBck/xyKm4u9KnXVmYjlI1fJrwrGUxklO xp+Y1xe/e8QoxPikjOVhL5tnpmlTkWRzuoaaZ+OA= DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 074D8605A2 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=ilina@codeaurora.org Date: Wed, 9 May 2018 10:25:52 -0600 From: Lina Iyer To: Daniel Lezcano Cc: edubezval@gmail.com, rui.zhang@intel.com, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, Ram Chandrasekar Subject: Re: [PATCH] drivers: thermal: step_wise: add support for hysteresis Message-ID: <20180509162552.GE4698@codeaurora.org> References: <20180507175408.2154-1-ilina@codeaurora.org> <20180508020453.GH19313@mai> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20180508020453.GH19313@mai> User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On Tue, May 08 2018 at 20:04 -0600, Daniel Lezcano wrote: >On Mon, May 07, 2018 at 11:54:08AM -0600, Lina Iyer wrote: >> From: Ram Chandrasekar >> >> From: Ram Chandrasekar >> >> Step wise governor increases the mitigation level when the temperature >> goes above a threshold and will decrease the mitigation when the >> temperature falls below the threshold. If it were a case, where the >> temperature hovers around a threshold, the mitigation will be applied >> and removed at every iteration. This reaction to the temperature is >> inefficient for performance. >> >> The use of hysteresis temperature could avoid this ping-pong of >> mitigation by relaxing the mitigation to happen only when the >> temperature goes below this lower hysteresis value. > >I don't disagree with this but the ping-pong around a temperature is usually >avoided with a P-I-D computation which is implemented with the IPA governor. >Wouldn't be more interesting to add the power numbers like some other >platforms, so the IPA could be used? > Possibly. But we have had better thermal performance for our hardware, with stepwise and custom governor. Much of the mitigation happens through the firmware and hardware. The stepwise governor works well for us. >You will probably have better results with the IPA than changing the step-wise >governor behavior (which may potentially impact other users). > This should not impact others who have not implemented the ->get_trip_hyst method. Thanks, Lina