From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 210142C11D6; Wed, 25 Feb 2026 08:49:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772009394; cv=none; b=keF8bucdMtkVTqsOcS8RqXjl1xt3UIqoW7Ldji3qjTYloSj6RvJveT6GV3fOOEa+Az7lVnRUyyc7Q5bruEKAd0YLbARYAPRr3UUYimtKmtcid78jloxk9rMECfJl5HKSnDUFySmr/JUCPt3SlDM4NSvIW04R9Som6b4iY6pqpQM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772009394; c=relaxed/simple; bh=0XuRh2d/myguiCEUP5T6yX1ZmrbAbjyTCrGGdy3n8YA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=sMjK1Z1xsRRNVaOOehM9jY1ueASlviPsykMoeM/Yp/fcnhx6u0YNGdWb6Kww0XRxhnAme5xaQbZiZUWiPoWWlKBjiO2dK5ExbdQLB3T+/f4ExzvyQGOUH1PezV/E4P9Vxk5KFYCg+af5XGOlhtxbcdEu/t/pbnSDPx5BfUQ7A74= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com 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 51B531691; Wed, 25 Feb 2026 00:49:46 -0800 (PST) Received: from e135073.nice.arm.com (e135073.arm.com [10.34.125.27]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 196543F59E; Wed, 25 Feb 2026 00:49:48 -0800 (PST) From: Pierre Gondois To: linux-kernel@vger.kernel.org Cc: Jie Zhan , Lifeng Zheng , Ionela Voinescu , Sumit Gupta , Christian Loehle , Pierre Gondois , "Rafael J. Wysocki" , Viresh Kumar , Huang Rui , "Gautham R. Shenoy" , Mario Limonciello , Perry Yuan , Srinivas Pandruvada , Len Brown , Saravana Kannan , linux-pm@vger.kernel.org Subject: [PATCH v5 1/6] cpufreq: Remove per-CPU QoS constraint Date: Wed, 25 Feb 2026 09:49:18 +0100 Message-ID: <20260225084930.1692228-2-pierre.gondois@arm.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260225084930.1692228-1-pierre.gondois@arm.com> References: <20260225084930.1692228-1-pierre.gondois@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit policy->max_freq_req represents the maximum allowed frequency as requested by the policyX/scaling_max_freq sysfs file. This request applies to all CPUs of the policy. It is not possible to request a per-CPU maximum frequency. Thus, the interaction between the policy boost and scaling_max_freq settings should be handled by adding a boost specific QoS constraint. This will be handled in the following patches. This patch reverts of: commit 1608f0230510 ("cpufreq: Fix re-boost issue after hotplugging a CPU") Reviewed-by: Lifeng Zheng Signed-off-by: Pierre Gondois --- drivers/cpufreq/cpufreq.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c index 4472bb1ec83c7..db414c052658b 100644 --- a/drivers/cpufreq/cpufreq.c +++ b/drivers/cpufreq/cpufreq.c @@ -1481,10 +1481,6 @@ static int cpufreq_policy_online(struct cpufreq_policy *policy, blocking_notifier_call_chain(&cpufreq_policy_notifier_list, CPUFREQ_CREATE_POLICY, policy); - } else { - ret = freq_qos_update_request(policy->max_freq_req, policy->max); - if (ret < 0) - goto out_destroy_policy; } if (cpufreq_driver->get && has_target()) { -- 2.43.0