From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Feng, Kenneth" <Kenneth.Feng@amd.com>,
"Wang, Yang(Kevin)" <KevinYang.Wang@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/amd/pm: update deep sleep status on smu v14.0.2/3
Date: Thu, 17 Oct 2024 13:26:44 +0530 [thread overview]
Message-ID: <dad2b821-aee5-4a5d-baef-4af7fc5ee8c0@amd.com> (raw)
In-Reply-To: <DM4PR12MB5165E79EEDD00A4F1DFE25478E462@DM4PR12MB5165.namprd12.prod.outlook.com>
On 10/17/2024 5:16 AM, Feng, Kenneth wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> The logic is that when entering the compute workload, enable deep sleep.
> When exiting the compute workload, disable deep sleep.
> It's not required to do the deep sleep setting in other workload type.
> Thanks.
>
This patch looks good. Please name temp_profile_mode as current_profile
for clarity and may be comment about smu->power_profile_mode as the
new/target mode.
With those -
Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>
Thanks,
Lijo
>
> -----Original Message-----
> From: Wang, Yang(Kevin) <KevinYang.Wang@amd.com>
> Sent: Wednesday, October 16, 2024 8:38 PM
> To: Feng, Kenneth <Kenneth.Feng@amd.com>; amd-gfx@lists.freedesktop.org
> Cc: Feng, Kenneth <Kenneth.Feng@amd.com>
> Subject: RE: [PATCH] drm/amd/pm: update deep sleep status on smu v14.0.2/3
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> -----Original Message-----
> From: Kenneth Feng <kenneth.feng@amd.com>
> Sent: Wednesday, October 16, 2024 3:19 PM
> To: amd-gfx@lists.freedesktop.org
> Cc: Wang, Yang(Kevin) <KevinYang.Wang@amd.com>; Feng, Kenneth <Kenneth.Feng@amd.com>
> Subject: [PATCH] drm/amd/pm: update deep sleep status on smu v14.0.2/3
>
> disable deep sleep during the compute workload for the potential performance loss on smu v14.0.2/3
>
> Signed-off-by: Kenneth Feng <kenneth.feng@amd.com>
> ---
> drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c b/drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c
> index 27f4e0ce447d..ecdd11a87311 100644
> --- a/drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c
> +++ b/drivers/gpu/drm/amd/pm/swsmu/smu14/smu_v14_0_2_ppt.c
> @@ -1784,7 +1784,7 @@ static int smu_v14_0_2_set_power_profile_mode(struct smu_context *smu,
> DpmActivityMonitorCoeffInt_t *activity_monitor =
> &(activity_monitor_external.DpmActivityMonitorCoeffInt);
> int workload_type, ret = 0;
> -
> + uint32_t temp_profile_mode = smu->power_profile_mode;
> smu->power_profile_mode = input[size];
>
> if (smu->power_profile_mode >= PP_SMC_POWER_PROFILE_COUNT) { @@ -1842,6 +1842,11 @@ static int smu_v14_0_2_set_power_profile_mode(struct smu_context *smu,
> }
> }
>
> + if (smu->power_profile_mode == PP_SMC_POWER_PROFILE_COMPUTE)
> + smu_v14_0_deep_sleep_control(smu, false);
> + else if (temp_profile_mode == PP_SMC_POWER_PROFILE_COMPUTE)
> + smu_v14_0_deep_sleep_control(smu, true);
> [Kevin]:
>
> This code logic doesn't seem easy to understand, If I understand correctly, can I modify it to the following writing style:
>
> If (new profile != current profile) {
> smu_v14_0_deep_sleep_control(smu, new profile == compute profile ? false : true);
> smu->power_profile_mode = new profile.
> }
>
> Best Regards,
> Kevin
> /* conv PP_SMC_POWER_PROFILE* to WORKLOAD_PPLIB_*_BIT */
> workload_type = smu_cmn_to_asic_specific_index(smu,
> CMN2ASIC_MAPPING_WORKLOAD,
> --
> 2.34.1
>
>
prev parent reply other threads:[~2024-10-17 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 7:19 [PATCH] drm/amd/pm: update deep sleep status on smu v14.0.2/3 Kenneth Feng
2024-10-16 12:37 ` Wang, Yang(Kevin)
2024-10-16 23:46 ` Feng, Kenneth
2024-10-17 7:56 ` Lazar, Lijo [this message]
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=dad2b821-aee5-4a5d-baef-4af7fc5ee8c0@amd.com \
--to=lijo.lazar@amd.com \
--cc=Kenneth.Feng@amd.com \
--cc=KevinYang.Wang@amd.com \
--cc=amd-gfx@lists.freedesktop.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