Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp3366833pxb; Fri, 5 Nov 2021 14:32:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz9TTFcBfr4JqtocC9lArSLT5fE2afDd16KCPI4iRDT+by+aKRAPMaQ0fMH4x3GxMpSoJ36 X-Received: by 2002:a02:b796:: with SMTP id f22mr11443429jam.112.1636147951304; Fri, 05 Nov 2021 14:32:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1636147951; cv=none; d=google.com; s=arc-20160816; b=lXyG3pfRv7wpWfbtT4CfpcLH+4h3E159PuxPhuBP4jvkropNxO6XumHqHMuMRfYUmj a6sGkF5iNN4DJUlW7S+LxaYwFFGUiWqWp2LfHQx5bUvceapWo0mN15c0TT4urHh5133N EvxLlFp+pZiKfecv6vG0w7auQrE/US40UKx95ogj2waul9LLERXuQ2xoHlBBZRMnHHMR GmW+XqTY6GGVCptjm/a+p+LVvNowyomcOtbnZb7PgFt1mmNJAtLcT4cn6HhLLb6vHn0E 5QpUN92sSJmiVSaPd+JdnDsMxKWijwvBUny3Z1dqc4IZLmWmpc+nreBj4AD5Bwpxmisx 3Q8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=Yw+xYYZxJY7aqJNmLJZqOSvkSUnGIUGzQbrZ89NrdYY=; b=P1/9VGAw63l5kE2cYYGYjyIUmHeY4y5pZ4qvl6AydhsVGSfQFiElQeRdmj4uqlMMdI DW+YQTJ5sMT5nN8jzasrh3hJyVHwjzhlKDUN8Bs38Cj+vCFdL4Tccvy92DZURYvoKBAy 8uSt0xIO7zMjaKrG6jEbXyeI/GhmecII0ZYCXVNBk97ioMIoeahPscmY5JILiJUR0cj0 IuFEPkQZ+kv/AhNFKC1KTSdG0+tCvUpoLcxpqWHMkZXRH1BXJIzt48hknLJBc0YRO+oF 2+TNZgk5UniTs0GBY2pWKjWCI4KuV/36Raqddc37KVs1wCWLt298L5s2cV6U74TttL2V 0aGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=IUvwPhlH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id h5si13462242ilq.93.2021.11.05.14.32.19; Fri, 05 Nov 2021 14:32:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=IUvwPhlH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S232936AbhKESvr (ORCPT + 99 others); Fri, 5 Nov 2021 14:51:47 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232987AbhKESvg (ORCPT ); Fri, 5 Nov 2021 14:51:36 -0400 Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32C67C061205 for ; Fri, 5 Nov 2021 11:48:56 -0700 (PDT) Received: by mail-qv1-xf31.google.com with SMTP id i13so7890197qvm.1 for ; Fri, 05 Nov 2021 11:48:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=Yw+xYYZxJY7aqJNmLJZqOSvkSUnGIUGzQbrZ89NrdYY=; b=IUvwPhlHPqszZsAvbv+dcliHFp/WpGdH694upHpX58UFOvrraajf4xRiPtUEESlFVC Tq5AxF3WsE9/hDfFLWirPsNthoPGxbxmDfSKT0kmKviloXLurGTpV7iTtQ47h3sSOpuf M/W1GQOyFFfU4W3pO1SWfg6Mn2XvzrsiZDUmHtv3KxdiJXWzXdPpNZr/Xw0y6ngmDgnB 3OgCDZig9jBlo9Ms7oZVP7U96m/LEkBXz0lUDzGRAIHQkX8YnK/BXPBrz8ZU+lypsk7b owtsnIU69/4e8emMtvgs40ce9w1+K7jp8Ea8JJ3yzzYSE6oOu+d+r9SS17GDUDAxMPHZ mmSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Yw+xYYZxJY7aqJNmLJZqOSvkSUnGIUGzQbrZ89NrdYY=; b=6Q3mIFFHveDg8Rpgzst4tx64ZyNcrVcEHSSkE1wNThXJCdY6kIkbIGCoSGwOeIBQ47 VgxAzLUCnh6d40gTEfl487yxd8d2qabPQLtQlTJ6ueFaOXGje06LXXOMj/q+VEJhbKqL SL5TS9g/LQnpZdP+Xx5RQLokk25UFHOEFsc1EO7VnL349oXOfaGQCWhdQNQ6HdTEW4FB NdEdcuStf7CsRHERKgE5dhmiLU+2qW+/D+u2CNrqJQ10BJzf1ODT3yIkj9o++c19/v3E z1vX6cPD20X5euq0jOU0LO8BHAVqKb7x6a84uPIXPWV7Rvf3S/l6ZEn/rNC+23xPopt4 XTVg== X-Gm-Message-State: AOAM530O21EH6Y3BVOQfkivsjx7e1+c1cflijSVxcZJh0sD5ssu4z0z6 2opIWpZWvfDJyKfMyPfgajrXzqxSVKyOjw== X-Received: by 2002:ad4:5747:: with SMTP id q7mr935708qvx.19.1636138134991; Fri, 05 Nov 2021 11:48:54 -0700 (PDT) Received: from [192.168.1.93] (pool-71-163-245-5.washdc.fios.verizon.net. [71.163.245.5]) by smtp.gmail.com with ESMTPSA id s14sm724536qkg.115.2021.11.05.11.48.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 05 Nov 2021 11:48:54 -0700 (PDT) Subject: Re: [PATCH] drivers: thermal: Reset previous low and high trip during thermal zone init To: Manaf Meethalavalappu Pallikunhi , Zhang Rui , Daniel Lezcano , Amit Kucheria Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <1635883240-24293-1-git-send-email-manafm@codeaurora.org> From: Thara Gopinath Message-ID: <51de966a-9c9e-88a8-5c2c-96773a64d527@linaro.org> Date: Fri, 5 Nov 2021 14:48:53 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <1635883240-24293-1-git-send-email-manafm@codeaurora.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/2/21 4:00 PM, Manaf Meethalavalappu Pallikunhi wrote: > During the suspend is in process, thermal_zone_device_update bails out > thermal zone re-evaluation for any sensor trip violation without > setting next valid trip to that sensor. It assumes during resume > it will re-evaluate same thermal zone and update trip. But when it is > in suspend temperature goes down and on resume path while updating > thermal zone if temperature is less than previously violated trip, > thermal zone set trip function evaluates the same previous high and > previous low trip as new high and low trip. Since there is no change > in high/low trip, it bails out from thermal zone set trip API without > setting any trip. It leads to a case where sensor high trip or low > trip is disabled forever even though thermal zone has a valid high > or low trip. > > During thermal zone device init, reset thermal zone previous high > and low trip. It resolves above mentioned scenario. > > Signed-off-by: Manaf Meethalavalappu Pallikunhi Reviewed-by: Thara Gopinath -- Warm Regards Thara (She/Her/Hers) > --- > drivers/thermal/thermal_core.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/thermal/thermal_core.c b/drivers/thermal/thermal_core.c > index 21db445..2b7a0b4 100644 > --- a/drivers/thermal/thermal_core.c > +++ b/drivers/thermal/thermal_core.c > @@ -477,6 +477,8 @@ static void thermal_zone_device_init(struct thermal_zone_device *tz) > { > struct thermal_instance *pos; > tz->temperature = THERMAL_TEMP_INVALID; > + tz->prev_low_trip = -INT_MAX; > + tz->prev_high_trip = INT_MAX; > list_for_each_entry(pos, &tz->thermal_instances, tz_node) > pos->initialized = false; > } >