Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp367385pxb; Mon, 25 Oct 2021 09:48:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwVegGbff1BE5AecNMJnXcYE3CO38ZWLb7m4J2TvpN5a9YsaulKMd/LO2I4ovdPGF0KLF42 X-Received: by 2002:a17:907:7248:: with SMTP id ds8mr11217706ejc.378.1635180512107; Mon, 25 Oct 2021 09:48:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635180512; cv=none; d=google.com; s=arc-20160816; b=RxUaXHv+kaceaZ88zmz+LVHUUTK7WPkOI27J3S6YDohi3rc3HHWW1ggR7lwrdKvv3u myi9/Pls9wX1TmSpeV2XRqyCC2/1H7+4vkv2j+p5tIZJ8ds4yQhG2g0W2wx3qNsn0Vkv mtIlHZ50uO6mAMGSUAkfXXbSs5Ohdjn2/SJhkFUs67890yoJwu5x4Q2HzKz7HmgSwIOn 7q5h3l7nAiECMbeBIhkhirU+FvPSFNRA4D+Df8+yya+K9WtbnbCEJMGJDp1P020ka2+r O30fUAL7VDlE27XnIi5fAY2U5SdU7DL0qzpKZK1ZYcf5Fok4HleZft1Vo7vQVzODAXX8 ob4g== 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; bh=ZQ7AjOs4bKGob/saOBLWoJgu0Ep2UY6sgNVRUaYyP9I=; b=CUHGGKIR2UQinAAn2M0wv/0WcmL3s1mr0gfRsjfZhP2AY4nUZWLxTkemVc2rEBcz5F xIbWoHVPG9nwfdpLOfQKr2fZsPf7tRXCcMzWMV+LB+VeNjfjWyu4ILuFH3ls/N7vsso8 7DprpxHUxcls3sE531pvITcZS6Vjgs5sIylec9pT3Vw+LeSjaDuf3KRGiqjIPyuO/BoU G7s7VDL6abhqoEY5ZTT9rbAbeoCSkYylUbsMDBAGnvtpjc93Ivbyw8kdsMVoNdm+YovA DUSvDBhalIrOqEoVzZqhnMyBURIXSJ+jlwIT9sGENQh/TF7W3vO/R6b2qNgDbl5Wzm2k /keA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z5si3355059edd.390.2021.10.25.09.48.07; Mon, 25 Oct 2021 09:48:32 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234026AbhJYQpk (ORCPT + 99 others); Mon, 25 Oct 2021 12:45:40 -0400 Received: from foss.arm.com ([217.140.110.172]:48052 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234036AbhJYQpi (ORCPT ); Mon, 25 Oct 2021 12:45:38 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 498441FB; Mon, 25 Oct 2021 09:43:16 -0700 (PDT) Received: from [10.57.21.241] (unknown [10.57.21.241]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 006DD3F5A1; Mon, 25 Oct 2021 09:43:12 -0700 (PDT) Subject: Re: [PATCH v2 0/5] Refactor thermal pressure update to avoid code duplication To: rafael@kernel.org, viresh.kumar@linaro.org, daniel.lezcano@linaro.org Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, sudeep.holla@arm.com, will@kernel.org, catalin.marinas@arm.com, linux@armlinux.org.uk, gregkh@linuxfoundation.org, amitk@kernel.org, amit.kachhap@gmail.com, thara.gopinath@linaro.org, bjorn.andersson@linaro.org, agross@kernel.org References: <20211015144550.23719-1-lukasz.luba@arm.com> From: Lukasz Luba Message-ID: <3cc80fea-1320-9a1a-9954-85b30f3d933a@arm.com> Date: Mon, 25 Oct 2021 17:43:11 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20211015144550.23719-1-lukasz.luba@arm.com> 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 10/15/21 3:45 PM, Lukasz Luba wrote: > Hi all, > > This patch set v2 aims to refactor the thermal pressure update > code. There are already two clients which do similar thing: > convert the capped frequency value into the capacity of > affected CPU and call the 'set' function to store the > reduced capacity into the per-cpu variable. > There might be more than two of these users. In near future > it will be scmi-cpufreq driver, which receives notification > from FW about reduced frequency due to thermal. Other vendors > might follow. Let's avoid code duplication and potential > conversion bugs. Move the conversion code into the arch_topology.c > where the capacity calculation setup code and thermal pressure sit. > > Apart from that $subject patches, there is one patch (3/5) which fixes > issue in qcom-cpufreq-hw.c when the thermal pressure is not > updated for offline CPUs. It's similar fix that has been merged > recently for cpufreq_cooling.c: > 2ad8ccc17d1e4270cf65a3f2 > > Changes: > v2: > - added Reviewed-by from Thara for patch 3/5 > - changed the doxygen comment and used mult_frac() > according to Thara's suggestion in patch 1/5 > v1 -> [1] > Gentle ping. Viresh, Daniel, Rafael could you have a look at this, please? Regards, Lukasz