public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gautham R. Shenoy" <gautham.shenoy@amd.com>
To: Lifeng Zheng <zhenglifeng1@huawei.com>
Cc: rafael@kernel.org, lenb@kernel.org, robert.moore@intel.com,
	viresh.kumar@linaro.org, mario.limonciello@amd.com,
	ray.huang@amd.com, pierre.gondois@arm.com,
	acpica-devel@lists.linux.dev, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linuxarm@huawei.com, jonathan.cameron@huawei.com,
	zhanjie9@hisilicon.com, lihuisong@huawei.com,
	hepeng68@huawei.com, fanghao11@huawei.com
Subject: Re: [PATCH v4 6/6] cpufreq: CPPC: Support for autonomous selection in cppc_cpufreq
Date: Wed, 15 Jan 2025 20:21:08 +0530	[thread overview]
Message-ID: <Z4fLXPgMvwGur+pz@BLRRASHENOY1.amd.com> (raw)
In-Reply-To: <20250113122104.3870673-7-zhenglifeng1@huawei.com>

Hello Lifeng,


On Mon, Jan 13, 2025 at 08:21:04PM +0800, Lifeng Zheng wrote:
> Add sysfs interfaces for CPPC autonomous selection in the cppc_cpufreq
> driver.
> 

[..snip..]

> diff --git a/drivers/cpufreq/cppc_cpufreq.c b/drivers/cpufreq/cppc_cpufreq.c
> index bd8f75accfa0..ea6c6a5bbd8c 100644
> --- a/drivers/cpufreq/cppc_cpufreq.c
> +++ b/drivers/cpufreq/cppc_cpufreq.c
> @@ -814,10 +814,119 @@ static ssize_t show_freqdomain_cpus(struct cpufreq_policy *policy, char *buf)
>  
>  	return cpufreq_show_cpus(cpu_data->shared_cpu_map, buf);
>  }
> +
> +static ssize_t show_auto_select(struct cpufreq_policy *policy, char *buf)
> +{
> +	bool val;
> +	int ret;
> +
> +	ret = cppc_get_auto_sel(policy->cpu, &val);
> +
> +	/* show "<unsupported>" when this register is not supported by cpc */
> +	if (ret == -EOPNOTSUPP)
> +		return sysfs_emit(buf, "%s\n", "<unsupported>");
> +
> +	if (ret)
> +		return ret;
> +
> +	return sysfs_emit(buf, "%d\n", val);
> +}
> +
> +static ssize_t store_auto_select(struct cpufreq_policy *policy,
> +				 const char *buf, size_t count)
> +{
> +	bool val;
> +	int ret;
> +
> +	ret = kstrtobool(buf, &val);
> +	if (ret)
> +		return ret;
> +
> +	ret = cppc_set_auto_sel(policy->cpu, val);

When the auto_select register is not supported, since
cppc_set_reg_val() doesn't have the !CPC_SUPPORTED(reg) check, that
function won't return an error, and thus this store function won't
return an error either. Should there be a !CPC_SUPPORTED(reg) check in
cppc_set_reg_val() as well? Or should the store function call
cppc_get_auto_sel() to figure out if the register is supported or not?

--
Thanks and Regards
gautham.

  reply	other threads:[~2025-01-15 14:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 12:20 [PATCH v4 0/6] Support for autonomous selection in cppc_cpufreq Lifeng Zheng
2025-01-13 12:20 ` [PATCH v4 1/6] ACPI: CPPC: Add IS_OPTIONAL_CPC_REG macro Lifeng Zheng
2025-01-14 13:27   ` Rafael J. Wysocki
2025-01-15  7:52     ` zhenglifeng (A)
2025-01-13 12:21 ` [PATCH v4 2/6] ACPI: CPPC: Add cppc_get_reg_val and cppc_set_reg_val function Lifeng Zheng
2025-01-14 17:41   ` Rafael J. Wysocki
2025-01-15  8:10     ` zhenglifeng (A)
2025-01-13 12:21 ` [PATCH v4 3/6] ACPI: CPPC: Add macros to generally implement registers getting and setting functions Lifeng Zheng
2025-01-14 17:58   ` Rafael J. Wysocki
2025-01-15  8:58     ` zhenglifeng (A)
2025-01-15 11:12       ` Rafael J. Wysocki
2025-01-16  1:12         ` zhenglifeng (A)
2025-01-13 12:21 ` [PATCH v4 4/6] ACPI: CPPC: Refactor register value get and set ABIs Lifeng Zheng
2025-01-13 12:21 ` [PATCH v4 5/6] ACPI: CPPC: Add autonomous selection ABIs Lifeng Zheng
2025-01-14 18:24   ` Rafael J. Wysocki
2025-01-15  9:16     ` zhenglifeng (A)
2025-01-13 12:21 ` [PATCH v4 6/6] cpufreq: CPPC: Support for autonomous selection in cppc_cpufreq Lifeng Zheng
2025-01-15 14:51   ` Gautham R. Shenoy [this message]
2025-01-16  1:26     ` zhenglifeng (A)
2025-01-16  6:13       ` Gautham R. Shenoy
2025-01-16  8:01         ` zhenglifeng (A)
2025-01-16 14:33           ` Gautham R. Shenoy
2025-01-16 11:39   ` Russell Haley
2025-01-17  3:11     ` zhenglifeng (A)
2025-01-17 14:30       ` Mario Limonciello
2025-01-20  3:15         ` zhenglifeng (A)
2025-01-20 14:49           ` Pierre Gondois
2025-01-20 17:44             ` Mario Limonciello
2025-01-21  2:42               ` zhenglifeng (A)
2025-01-23 16:46                 ` Srinivas Pandruvada
2025-01-23 17:05                   ` Mario Limonciello
2025-01-24  3:53                     ` zhenglifeng (A)
2025-01-24 14:18                       ` srinivas pandruvada
2025-02-05  6:13                         ` zhenglifeng (A)
2025-01-24 14:32                       ` Russell Haley
2025-02-05  6:13                         ` zhenglifeng (A)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z4fLXPgMvwGur+pz@BLRRASHENOY1.amd.com \
    --to=gautham.shenoy@amd.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=fanghao11@huawei.com \
    --cc=hepeng68@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lenb@kernel.org \
    --cc=lihuisong@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mario.limonciello@amd.com \
    --cc=pierre.gondois@arm.com \
    --cc=rafael@kernel.org \
    --cc=ray.huang@amd.com \
    --cc=robert.moore@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox