From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3739D46D098; Tue, 21 Jul 2026 19:26:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784661965; cv=none; b=laGLZ1/lnsmbEhbyWV2JAPnIU2LT4yyNIXKjs5Q7QPwWAMWaDjLxDxH3PJO6ibv202/9RoZCuVp/R9Or8UpkpwYy91gzU8UgUO5+TigF5Q1t8okey5fYV9icMEsOgE5Y0zIZ1Cf1Xd8A0EjmkH2rJ8WZjnTiZUJUWFuxYU8bmTc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784661965; c=relaxed/simple; bh=gTnwX+qZAlC05qs2GnapVL7z8UxH3tghtalx88EZOQA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Pe1BHZpj3LTg32ynhBY+NDSJ8zlR9Zk8wG8WiaFV+0xVaBf+AxAS2QDVYImH4FJfZezjVJoH2xxvOlF8xijY+qzoTC60Bc1CmGOQP3TtV+QwStFn1szayZ4zhAtUMuW25DRkWLn24aI9XcqjdLYwqFm7lcBtrf0DvvH6l7O94uA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=kn4roOxP; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="kn4roOxP" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9D52B1F000E9; Tue, 21 Jul 2026 19:26:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784661964; bh=2WbkMomA2YrNn/1o8CVK4x6UQRGBotzVE8lh79Fxd0c=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=kn4roOxPFedDxL28Udtsg6QCou8i00wORXzFBogA88I4GnkxVE3CwXTih5069mEx5 0xDnJjOWhbQixbsD8+ht0vxxQZ788UY2v2K0KZOmL4JicYugLrSO+YP5UR1A7IjKtQ jsR/XRNs3Nb+YvLbcNk5ksIruyQ+bheHn87rBFWs= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, Pengjie Zhang , Zhongqiu Han , "Rafael J. Wysocki" , Sasha Levin Subject: [PATCH 6.12 0264/1276] cpufreq: Documentation: fix conservative governor freq_step description Date: Tue, 21 Jul 2026 17:11:47 +0200 Message-ID: <20260721152451.991209869@linuxfoundation.org> X-Mailer: git-send-email 2.55.0 In-Reply-To: <20260721152446.065700225@linuxfoundation.org> References: <20260721152446.065700225@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.12-stable review patch. If anyone has any objections, please let me know. ------------------ From: Pengjie Zhang [ Upstream commit 03120e1425262c7d11f93362a88e579a1720390b ] The conservative governor documentation incorrectly states that setting freq_step to 0 will use the default 5% frequency step. In reality, since at least commit 8e677ce83bf4 ("[CPUFREQ] conservative: fixup governor to function more like ondemand logic"), freq_step=0 has always caused the governor to skip frequency updates entirely. Correct the documentation to reflect the actual behavior: freq_step=0 disables frequency changes by the governor entirely. Fixes: 2a0e49279850 ("cpufreq: User/admin documentation update and consolidation") Signed-off-by: Pengjie Zhang Reviewed-by: Zhongqiu Han [ rjw: Subject adjustment ] Link: https://patch.msgid.link/20260603055635.1549943-1-zhangpengjie2@huawei.com Signed-off-by: Rafael J. Wysocki Signed-off-by: Sasha Levin --- Documentation/admin-guide/pm/cpufreq.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/admin-guide/pm/cpufreq.rst b/Documentation/admin-guide/pm/cpufreq.rst index 0818f248374137..0c3f7247e3a349 100644 --- a/Documentation/admin-guide/pm/cpufreq.rst +++ b/Documentation/admin-guide/pm/cpufreq.rst @@ -573,8 +573,8 @@ This governor exposes the following tunables: 100 (5 by default). This is how much the frequency is allowed to change in one go. Setting - it to 0 will cause the default frequency step (5 percent) to be used - and setting it to 100 effectively causes the governor to periodically + it to 0 disables frequency changes by the governor entirely and setting + it to 100 effectively causes the governor to periodically switch the frequency between the ``scaling_min_freq`` and ``scaling_max_freq`` policy limits. -- 2.53.0