From: Dhananjay Ugwekar <Dhananjay.Ugwekar@amd.com>
To: "Gautham R.Shenoy" <gautham.shenoy@amd.com>,
"Meng, Li (Jassmine)" <Li.Meng@amd.com>,
"rafael@kernel.org" <rafael@kernel.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Yuan, Perry" <Perry.Yuan@amd.com>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"Huang, Ray" <Ray.Huang@amd.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] cpufreq/amd-pstate-ut: Handle the inconsistency
Date: Wed, 26 Jun 2024 12:15:14 +0530 [thread overview]
Message-ID: <4214cbfd-b8d2-4eb6-9870-5c74c056e51f@amd.com> (raw)
In-Reply-To: <875xtw2s8g.fsf@BLR-5CG11610CF.amd.com>
Hello Gautham,
On 6/26/2024 10:52 AM, Gautham R.Shenoy wrote:
> "Meng, Li (Jassmine)" <Li.Meng@amd.com> writes:
>
> Hello Jassmine,
>
>>
>> Hi Dhananjay:
>> Sorry for the delay.
>>
>> I think the correction to this issue should be in function amd_pstae_init_freq() of file amd-pstate.c.
>> The value of norminal_freq should be consistent with other
>> values(max_freq,min_freq etc.).
>
> Perry wanted nominal_freq to be in MHz since it is not exposed to the
> user via any of the cpufreq sysfs interfaces.
>
> IMO, it woyuld be good to to rename the variables to have their units
> for better readability along with a bunch of other
> cleanups/code deduplication. But can it be done separately ?
Yes that could be part of a separate cleanup patchset.
>
>
>>
>>> -----Original Message-----
>>> From: Ugwekar, Dhananjay <Dhananjay.Ugwekar@amd.com>
>>> Sent: Tuesday, June 25, 2024 9:52 PM
>>> To: rafael@kernel.org; viresh.kumar@linaro.org; Shenoy, Gautham Ranjal
>>> <gautham.shenoy@amd.com>; Limonciello, Mario
>>> <Mario.Limonciello@amd.com>; Yuan, Perry <Perry.Yuan@amd.com>;
>>> skhan@linuxfoundation.org; Meng, Li (Jassmine) <Li.Meng@amd.com>;
>>> Huang, Ray <Ray.Huang@amd.com>
>>> Cc: linux-pm@vger.kernel.org; linux-kernel@vger.kernel.org
>>> Subject: Re: [PATCH 1/2] cpufreq/amd-pstate-ut: Handle the inconsistency
>>>
>>> Minor modification, the commit subject is supposed to be
>>> "cpufreq/amd-pstate-ut: Handle the inconsistency between nominal_freq
>>> and other *_freq units"
>
> How about:
>
> "cpufreq/amd-pstate-ut: Convert nominal_freq to khz during comparisons"
Sure, this seems easier to understand and more concise. Will update in v2.
>
> Otherwise the patch looks good to me.
>
> Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Thanks for reviewing!
Regards,
Dhananjay
>
> --
> Thanks and Regards
> gautham.
>
next prev parent reply other threads:[~2024-06-26 6:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 13:41 [PATCH 0/2] AMD Pstate driver fixes Dhananjay Ugwekar
2024-06-25 13:41 ` [PATCH 1/2] cpufreq/amd-pstate-ut: Handle the inconsistency Dhananjay Ugwekar
2024-06-25 13:51 ` Dhananjay Ugwekar
2024-06-25 15:11 ` Mario Limonciello
2024-06-26 7:56 ` Dhananjay Ugwekar
2024-06-26 1:49 ` Meng, Li (Jassmine)
2024-06-26 5:22 ` Gautham R.Shenoy
2024-06-26 6:45 ` Dhananjay Ugwekar [this message]
2024-06-25 15:05 ` Mario Limonciello
2024-06-26 8:02 ` Dhananjay Ugwekar
2024-06-25 13:41 ` [PATCH 2/2] cpufreq/amd-pstate: Fix the scaling_min/max_freq setting on shared memory CPPC systems Dhananjay Ugwekar
2024-06-25 15:09 ` Mario Limonciello
2024-06-26 8:10 ` Dhananjay Ugwekar
2024-06-26 5:24 ` Gautham R.Shenoy
2024-06-26 7:57 ` Dhananjay Ugwekar
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=4214cbfd-b8d2-4eb6-9870-5c74c056e51f@amd.com \
--to=dhananjay.ugwekar@amd.com \
--cc=Li.Meng@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Ray.Huang@amd.com \
--cc=gautham.shenoy@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=viresh.kumar@linaro.org \
/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
all inboxes | Powered by JetHome®