From: Luben Tuikov <luben.tuikov@amd.com>
To: "Lazar, Lijo" <lijo.lazar@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Alex Deucher <Alexander.Deucher@amd.com>
Subject: Re: [PATCH 0/5] 0 MHz is not a valid current frequency
Date: Wed, 13 Oct 2021 12:22:09 -0400 [thread overview]
Message-ID: <e3d94e8a-ea9b-85cc-8e85-2ee2e6725f2f@amd.com> (raw)
In-Reply-To: <858da53c-7937-3ebf-360d-f20f30f825d9@amd.com>
On 2021-10-13 00:14, Lazar, Lijo wrote:
>
> On 10/13/2021 8:40 AM, Luben Tuikov wrote:
>> Some ASIC support low-power functionality for the whole ASIC or just
>> an IP block. When in such low-power mode, some sysfs interfaces would
>> report a frequency of 0, e.g.,
>>
>> $cat /sys/class/drm/card0/device/pp_dpm_sclk
>> 0: 500Mhz
>> 1: 0Mhz *
>> 2: 2200Mhz
>> $_
>>
>> An operating frequency of 0 MHz doesn't make sense, and this interface
>> is designed to report only operating clock frequencies, i.e. non-zero,
>> and possibly the current one.
>>
>> When in this low-power state, round to the smallest
>> operating frequency, for this interface, as follows,
>>
> Would rather avoid this -
>
> 1) It is manipulating FW reported value. If at all there is an uncaught
> issue in FW reporting of frequency values, that is masked here.
> 2) Otherwise, if 0MHz is described as GFX power gated case, this
> provides a convenient interface to check if GFX is power gated.
>
> If seeing a '0' is not pleasing, consider changing to something like
> "NA" - not available (frequency cannot be fetched at the moment).
There's a ROCm tool which literally asserts if the values are not ordered in increasing order. Now since 0 < 550, but 0 is listed as the second entry, the tool simply asserts and crashes.
It is not clear what you'd rather see here:
$cat /sys/class/drm/card0/device/pp_dpm_sclk
0: 550Mhz
1: N/A *
2: 2200MHz
$_
Is this what you want to see? (That'll crash other tools which expect %uMhz.)
Or maybe just a list without default hint, i.e. no asterisk?
$cat /sys/class/drm/card0/device/pp_dpm_sclk
0: 550Mhz
1: 2200MHz
$_
What should the output be?
We want to avoid showing 0, but still show numbers.
Regards,
Luben
>
> Thanks,
> Lijo
>
>> $cat /sys/class/drm/card0/device/pp_dpm_sclk
>> 0: 500Mhz *
>> 1: 2200Mhz
>> $_
>>
>> Luben Tuikov (5):
>> drm/amd/pm: Slight function rename
>> drm/amd/pm: Rename cur_value to curr_value
>> drm/amd/pm: Rename freq_values --> freq_value
>> dpm/amd/pm: Sienna: 0 MHz is not a current clock frequency
>> dpm/amd/pm: Navi10: 0 MHz is not a current clock frequency
>>
>> .../gpu/drm/amd/pm/swsmu/smu11/navi10_ppt.c | 60 +++++++++------
>> .../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 73 ++++++++++++-------
>> 2 files changed, 86 insertions(+), 47 deletions(-)
>>
next prev parent reply other threads:[~2021-10-13 16:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 3:10 [PATCH 0/5] 0 MHz is not a valid current frequency Luben Tuikov
2021-10-13 3:10 ` [PATCH 1/5] drm/amd/pm: Slight function rename Luben Tuikov
2021-10-13 14:50 ` Russell, Kent
2021-10-13 14:53 ` Luben Tuikov
2021-10-18 22:52 ` Paul Menzel
2021-10-18 23:02 ` Luben Tuikov
2021-10-13 3:10 ` [PATCH 2/5] drm/amd/pm: Rename cur_value to curr_value Luben Tuikov
2021-10-13 3:10 ` [PATCH 3/5] drm/amd/pm: Rename freq_values --> freq_value Luben Tuikov
2021-10-13 3:10 ` [PATCH 4/5] dpm/amd/pm: Sienna: 0 MHz is not a current clock frequency Luben Tuikov
2021-10-13 3:10 ` [PATCH 5/5] dpm/amd/pm: Navi10: " Luben Tuikov
2021-10-13 4:14 ` [PATCH 0/5] 0 MHz is not a valid current frequency Lazar, Lijo
2021-10-13 7:06 ` Quan, Evan
2021-10-13 13:58 ` Alex Deucher
2021-10-13 14:17 ` Lazar, Lijo
2021-10-13 16:22 ` Luben Tuikov [this message]
2021-10-13 17:06 ` Lazar, Lijo
2021-10-13 17:19 ` Alex Deucher
2021-10-15 2:25 ` Quan, Evan
2021-10-18 20:19 ` Deucher, Alexander
2021-10-18 20:29 ` Luben Tuikov
2021-10-19 1:04 ` Russell, Kent
2021-10-19 1:06 ` Russell, Kent
2021-10-19 4:27 ` Luben Tuikov
2021-10-19 13:25 ` Russell, Kent
2021-10-19 13:54 ` Luben Tuikov
2021-10-26 21:26 ` Alex Deucher
2021-10-26 22:00 ` Luben Tuikov
2021-10-27 5:20 ` Lazar, Lijo
2021-10-27 15:12 ` Alex Deucher
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=e3d94e8a-ea9b-85cc-8e85-2ee2e6725f2f@amd.com \
--to=luben.tuikov@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=lijo.lazar@amd.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