Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp7434543pxb; Thu, 18 Feb 2021 09:57:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyaj0cGudbgmqShQWnzVdpEFZFFghEk8c8JMepAGyHLW7HHa572fcS8jnjot6sWr44L41ag X-Received: by 2002:aa7:d90b:: with SMTP id a11mr5301133edr.250.1613671052745; Thu, 18 Feb 2021 09:57:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613671052; cv=none; d=google.com; s=arc-20160816; b=SJIATduOqGD2sHkAzZ5urUuG832oiI+WGsIgNRxDQbjIVdze4G3HTd/P4XdeRELfcq vfEo96Pf5OC0WTKgbrefngjA5BnbvkRwk4Merv1nat1Vy/zpT5UHiiNivHp6x9BG/VyW 9B2pY4hfRcS1Xqbqov3wAxAktMPO0Pvg9zH8KkMUNRz14aDu+zWjwSL7fO9a23OqExdB tYdedKaIhM7WH3VWGl7xmyvJDDSa4cRlLTzp2awR7bxdt9MOujsuUMv5YFuwsIMBguqg tYuUjSPZXNfvdHMS888YHjqw8j9axEG4/BFLxWpgJ2dXaBDnekNbnPnA7CqmRUhoOOyj F5+g== 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=p89DwoOOsvw+CnJ+KQOJKP+OK4RgyV7iDfRp7yPRuZo=; b=fjfaWvJTGSqJk4JTlwH39ZhOPiRvPyshs/lyeXqCiMWv2TrKcfkh8ObUbyocJlz/En R+CAV9KfdJ0qzeyLKltStKh984TYN54u3AulVI2M8tVMYzy/1dCc82fahp5ZxQMu9hDL zk5Ak7xiF4S9oUAQ2Jc6Q+Li2GBow5mhnyd5FIf7A01Ak3m/hKIyc6fjH6J7XXnePZru tYv3qbvbm4qNOaRqFjU2XYbmImU3i4wYKcW6ePK7kxAdkVw1epnzucs/zBQzxm805zHQ nww/9oD9/+h7MZMyj8Oq2qRIpelM1lCK8HM2mt4sDjYIBXwwDyBsqs8G5K2/kZWYJcwf sgvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=sgctuxKe; 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 e16si3959218edy.358.2021.02.18.09.57.09; Thu, 18 Feb 2021 09:57:32 -0800 (PST) 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=sgctuxKe; 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 S234679AbhBRRzg (ORCPT + 99 others); Thu, 18 Feb 2021 12:55:36 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55382 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230351AbhBRPNs (ORCPT ); Thu, 18 Feb 2021 10:13:48 -0500 Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABDAAC061756 for ; Thu, 18 Feb 2021 07:03:23 -0800 (PST) Received: by mail-qk1-x72d.google.com with SMTP id 81so2328992qkf.4 for ; Thu, 18 Feb 2021 07:03:23 -0800 (PST) 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=p89DwoOOsvw+CnJ+KQOJKP+OK4RgyV7iDfRp7yPRuZo=; b=sgctuxKei7vpMxAFsHQIa8x6kCjgbaZvDkmVddN/LebhlxKF/pKp6tjD2DTiXUgLCt 1cz7XUznrCNS7chrttB3GVbH2iITgGkEtzHzD1aLraA2mGEz1aU8d0vo+6V19zbzlTQp t4u5OBodgkj8GBJO1U6v4tGZz9yUUMo/kB720eV6RZjLH15grwDdYcBBTitxrohj0hGy HZ4oJUxIow1RUSGGTJttrInJn2tM97F6Ii1y9uIIduW/WO9LxAmlO3z8ZCTcL/jHMFxW Pqgm2El0fVG5MnU9qCwEGnKK7g37Y18a6/jWLnMR7yIruP1Rw4mrmzXr3vQQCSS8Aovn T7AQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=p89DwoOOsvw+CnJ+KQOJKP+OK4RgyV7iDfRp7yPRuZo=; b=VAq8nMNIOnMTO32fSIzhzfgGPi5YsCRI0XQmJetf2ksMy6re297KTcTtPvEEmD2+55 EHl0w+YPVKKa4VSsILjCwS9Yt5x47b3Gmhoq6A8MUs/4wjBYjBpvMntSTy7t8qNKxyIA tzHaMaYSu8G9tUsFzdBUqTSXgstrI8CMoDdWP9SGlkhgG3ZGsFY/eis8qqiOc4PeppTs K8IOgPBuPFvwv+/U2U2aHJkG4e4+i4qGHYjZMWkT4tM47/iY2YntVchJYVxWW+jr67Ol tCaFBW+4j18nZRFtqSScW26KPSuhBXVP5+sGF/gBJNJ7TKmUVCpH16D8kQCfW7nkyXhW //2g== X-Gm-Message-State: AOAM532LJl/YVaxDEHbjy9iPB2S6jrz20tIQd8gMndPPI61VisKVWfCW R09HQ3oojDDQrD76vjJY+2jtlg== X-Received: by 2002:a37:8b84:: with SMTP id n126mr4461711qkd.223.1613660602315; Thu, 18 Feb 2021 07:03:22 -0800 (PST) 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 u133sm4135077qka.116.2021.02.18.07.03.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 18 Feb 2021 07:03:21 -0800 (PST) Subject: Re: [PATCH] cpufreq: exclude boost frequencies from valid count if not enabled To: Viresh Kumar Cc: rjw@rjwysocki.net, bjorn.andersson@linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org References: <20210217000013.4063289-1-thara.gopinath@linaro.org> <20210217055029.a25wjsyoosxageti@vireshk-i7> <4c9d9d44-5fa5-3ae1-e9bb-45cf6521b764@linaro.org> <20210218084847.743rttqwlmwyx6pz@vireshk-i7> From: Thara Gopinath Message-ID: Date: Thu, 18 Feb 2021 10:03:20 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20210218084847.743rttqwlmwyx6pz@vireshk-i7> 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 2/18/21 3:48 AM, Viresh Kumar wrote: > On 17-02-21, 10:32, Thara Gopinath wrote: >> First of all, I am still unable to find this setting in the sysfs space. > > The driver needs to call cpufreq_enable_boost_support() for that. Ok. that makes sense. > >> Irrespective the ideal behavior here will be to change the cpufreq cooling >> dev max state when this happens. > > Hmm.. recreating it every time boost frequency is enabled is like > inviting trouble and it will be tricky. Maybe it can be done, I don't > know.:) Scheduling a notifier for max frequency change from the qos framework should do the work, right? > -- Warm Regards Thara