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 46B81363081; Tue, 21 Jul 2026 17:55:24 +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=1784656525; cv=none; b=siL+GN9r1xVA8VfN08giDPpc3qqJzNcdNJh7MGuAT+IKij0U2qmZph3LuS1Ft2x1wkXTNSwHPQY4aATGLDlFIiUCIEmALSMHmwtPjlyznj5FzktnXVDtoFQ8Q0pcwQ7SOOSoe8hGA6zIsBTREAqdxXtGRXdmTs/ZKAbhW1c4Ta8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784656525; c=relaxed/simple; bh=8FkBwVogN0kpJzdZTu1iWM+ZrUVE9lyarcsKrXvpg4s=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=b+mjDrkEfRmJNl+tyxK1cdZX87zoJxKi5C3dSk3d77JFsAie/i/k/GyJ62x3mLKiXe7jutYOgZV89Nud2S5D0BVNSBjpFC3G1637iABnb3mwdBvfDoNuHCuI3y+XNhOGRl+dWaIRrdowG3kAnzH4vduEt1Us/DsyjBsJnDxL7l4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ghlDTX0n; 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="ghlDTX0n" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9F6051F000E9; Tue, 21 Jul 2026 17:55:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784656524; bh=Mr4V8raG2ZzRsDaXmT/iz6m+NWLkPLp27Hs34lGSWXo=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=ghlDTX0nJOblPhkxKakirHL3ge5EDJH74jw0If6hcaO7HeM3VHsVgTD9nRdg8KAiQ WLFSKpCEqk0YsX8qL5IO3ozs+cBZVe8xi0X3lB5mp2ALL1xZ4NuYoFzHTd10lkQctb 7UBE4LMIhXDmAciCcp4prKsM14LWPXsRznDuSXcM= 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.18 0377/1611] cpufreq: Documentation: fix conservative governor freq_step description Date: Tue, 21 Jul 2026 17:08:13 +0200 Message-ID: <20260721152523.670718363@linuxfoundation.org> X-Mailer: git-send-email 2.55.0 In-Reply-To: <20260721152514.750365251@linuxfoundation.org> References: <20260721152514.750365251@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.18-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 33122fbe9f6a0e..9909c7d5c6172d 100644 --- a/Documentation/admin-guide/pm/cpufreq.rst +++ b/Documentation/admin-guide/pm/cpufreq.rst @@ -586,8 +586,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