From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from canpmsgout03.his.huawei.com (canpmsgout03.his.huawei.com [113.46.200.218]) (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 BAFE5156237; Fri, 10 Oct 2025 03:29:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=113.46.200.218 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760066989; cv=none; b=PaaEMUgv1QfjxppeDYcZLw4gxX5KtVrO1pXiB/quyDJsfEO8PWGWoFz4BiZFLLs+b+bYt3/77KmhLcrx976tRnJh6aEbjB+EEq+WiaQDpuoYBpgwnjaANvEkq9gHAlLladjMuN4EeF7xpnZwpaAuO1g23gdsvHNBkXDHno+34tQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760066989; c=relaxed/simple; bh=2c1nq8EQZfZOPpq72pvGLcklP0BpO4y12HpirU/2WCo=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=Q+WBATSR3SpaagroZfDIkF+WLQg/JpHCtJayR3+L8cjNYeG1JCTxY6nGD9AFD7CDYnlXCEjx0jGTayWeRDglnXuWdtvC8lCEqOQ2wzq6cGYk9wWOzEjdQJUZ6ztsoHdXZUNqTUk/aNCOTMpnJGU8zx/EBpb7R62Ygsi5WVELbfE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=hisilicon.com; spf=pass smtp.mailfrom=hisilicon.com; arc=none smtp.client-ip=113.46.200.218 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=hisilicon.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=hisilicon.com Received: from mail.maildlp.com (unknown [172.19.163.174]) by canpmsgout03.his.huawei.com (SkyGuard) with ESMTPS id 4cjXK06XChzpSw3; Fri, 10 Oct 2025 11:28:52 +0800 (CST) Received: from kwepemr500004.china.huawei.com (unknown [7.202.195.141]) by mail.maildlp.com (Postfix) with ESMTPS id 78BF71402C8; Fri, 10 Oct 2025 11:29:38 +0800 (CST) Received: from [10.67.121.58] (10.67.121.58) by kwepemr500004.china.huawei.com (7.202.195.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 10 Oct 2025 11:29:37 +0800 Message-ID: <0dca2bf6-0f87-422d-a348-5ab33a9683d2@hisilicon.com> Date: Fri, 10 Oct 2025 11:29:36 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 6/8] cpufreq: CPPC: Add sysfs for min/max_perf and perf_limited To: Sumit Gupta , , , , , , , , , , , , , , , , , CC: , , , , , , References: <20251001150104.1275188-1-sumitg@nvidia.com> <20251001150104.1275188-7-sumitg@nvidia.com> Content-Language: en-US From: Jie Zhan In-Reply-To: <20251001150104.1275188-7-sumitg@nvidia.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: kwepems100002.china.huawei.com (7.221.188.206) To kwepemr500004.china.huawei.com (7.202.195.141) On 10/1/2025 11:01 PM, Sumit Gupta wrote: > Add sysfs interfaces for Minimum Performance, Maximum Performance > and Performance Limited Register in the cppc_cpufreq driver. > > Reviewed-by: Randy Dunlap > Signed-off-by: Sumit Gupta > --- > .../ABI/testing/sysfs-devices-system-cpu | 43 +++++++++++++++++++ > 1 file changed, 43 insertions(+) > > diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu > index ab8cd337f43a..82141b45d58c 100644 > --- a/Documentation/ABI/testing/sysfs-devices-system-cpu > +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu > @@ -327,6 +327,49 @@ Description: Energy performance preference > > This file is only present if the cppc-cpufreq driver is in use. > > +What: /sys/devices/system/cpu/cpuX/cpufreq/min_perf > +Date: September 2025 > +Contact: linux-pm@vger.kernel.org > +Description: Minimum Performance > + > + Read/write a 32 bits value from/to this file. This file > + conveys the minimum performance level at which the platform > + may run. Minimum performance may be set to any performance > + value in the range [Lowest Performance, Highest Performance], > + inclusive but must be set to a value that is less than or > + equal to that specified by the Maximum Performance Register. > + > + Writing to this file only has meaning when Autonomous Selection > + is enabled. > + > + This file is only present if the cppc-cpufreq driver is in use. > + > +What: /sys/devices/system/cpu/cpuX/cpufreq/max_perf > +Date: September 2025 > +Contact: linux-pm@vger.kernel.org > +Description: Minimum Performance Not adapted > + > + Read/write a 32 bits value from/to this file. This file conveys > + the maximum performance level at which the platform may run. > + Maximum performance may be set to any performance value in the > + range [Lowest Performance, Highest Performance], inclusive. > + > + Writing to this file only has meaning when Autonomous Selection is > + enabled. > + > + This file is only present if the cppc-cpufreq driver is in use. > + > +What: /sys/devices/system/cpu/cpuX/cpufreq/perf_limited > +Date: September 2025 > +Contact: linux-pm@vger.kernel.org > +Description: Minimum Performance Not adapted > + > + Read/write a 32 bits value from/to this file. This file indicates > + to OSPM that an unpredictable event has limited processor > + performance, and the delivered performance may be less than > + desired/minimum performance. > + > + This file is only present if the cppc-cpufreq driver is in use. > > What: /sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1} > Date: August 2008