From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: "Feng, Kenneth" <Kenneth.Feng@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "Arif, Maisam" <Maisam.Arif@amd.com>
Subject: Re: [PATCH] drm/amd/pm: disallow the fan setting if there is no fan on smu13
Date: Tue, 8 Aug 2023 16:22:43 +0530 [thread overview]
Message-ID: <5c867303-5d03-ebed-533d-d418ea920694@amd.com> (raw)
In-Reply-To: <DM4PR12MB516542C45FA8B45093D22C468E0DA@DM4PR12MB5165.namprd12.prod.outlook.com>
On 8/8/2023 3:56 PM, Feng, Kenneth wrote:
> [AMD Official Use Only - General]
>
> Currently no_fan is determined in sw init.
> if (!smu->ppt_funcs->get_fan_control_mode)
> smu->adev->pm.no_fan = true;
>
> This is the case that some boards have fans and some don't have.
> smu->ppt_funcs->get_fan_control_mode still need to be defined.
> !smu_cmn_feature_is_supported(smu, SMU_FEATURE_FAN_CONTROL_BIT) is enough to get the fan capability.
> Not sure if it's better to depend on pm.no_fan.
What I meant is, based on fan control feature bit you could set
pm.no_fan flag.
When pm.no_fan is set, we won't create hwmon fan attributes for
get/set[1]. That way you could avoid the other checks also. Also when
PMFW is not controlling, it's not guaranteed that the fan controller is
initialized correctly for get to return correct speed/pwm.
[1]
https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/amd/pm/amdgpu_pm.c#L3338
Thanks,
Lijo
> Thanks.
>
>
>
> -----Original Message-----
> From: Lazar, Lijo <Lijo.Lazar@amd.com>
> Sent: Tuesday, August 8, 2023 6:12 PM
> To: Feng, Kenneth <Kenneth.Feng@amd.com>; amd-gfx@lists.freedesktop.org
> Cc: Arif, Maisam <Maisam.Arif@amd.com>
> Subject: Re: [PATCH] drm/amd/pm: disallow the fan setting if there is no fan on smu13
>
>
>
> On 8/8/2023 1:21 PM, Kenneth Feng wrote:
>> disallow the fan setting if there is no fan on smu13
>>
>> Signed-off-by: Kenneth Feng <kenneth.feng@amd.com>
>> ---
>> drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c b/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c
>> index 9b62b45ebb7f..09ef0a7e7679 100644
>> --- a/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c
>> +++ b/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c
>> @@ -1131,7 +1131,9 @@ smu_v13_0_display_clock_voltage_request(struct smu_context *smu,
>>
>> uint32_t smu_v13_0_get_fan_control_mode(struct smu_context *smu)
>> {
>> - if (!smu_cmn_feature_is_enabled(smu, SMU_FEATURE_FAN_CONTROL_BIT))
>> + if (!smu_cmn_feature_is_supported(smu, SMU_FEATURE_FAN_CONTROL_BIT))
>> + return AMD_FAN_CTRL_NONE;
>
> If there is no PMFW fan control, isn't it better to set pm.no_fan?
>
> Thanks,
> Lijo
>
>> + else if (!smu_cmn_feature_is_enabled(smu, SMU_FEATURE_FAN_CONTROL_BIT))
>> return AMD_FAN_CTRL_MANUAL;
>> else
>> return AMD_FAN_CTRL_AUTO;
>> @@ -1143,7 +1145,7 @@ smu_v13_0_auto_fan_control(struct smu_context *smu, bool auto_fan_control)
>> int ret = 0;
>>
>> if (!smu_cmn_feature_is_supported(smu, SMU_FEATURE_FAN_CONTROL_BIT))
>> - return 0;
>> + return -EINVAL;
>>
>> ret = smu_cmn_feature_set_enabled(smu, SMU_FEATURE_FAN_CONTROL_BIT, auto_fan_control);
>> if (ret)
>> @@ -1204,7 +1206,8 @@ smu_v13_0_set_fan_control_mode(struct smu_context *smu,
>>
>> switch (mode) {
>> case AMD_FAN_CTRL_NONE:
>> - ret = smu_v13_0_set_fan_speed_pwm(smu, 255);
>> + if (smu_cmn_feature_is_supported(smu, SMU_FEATURE_FAN_CONTROL_BIT))
>> + ret = -EINVAL;
>> break;
>> case AMD_FAN_CTRL_MANUAL:
>> ret = smu_v13_0_auto_fan_control(smu, 0);
prev parent reply other threads:[~2023-08-08 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:51 [PATCH] drm/amd/pm: disallow the fan setting if there is no fan on smu13 Kenneth Feng
2023-08-08 10:12 ` Lazar, Lijo
2023-08-08 10:26 ` Feng, Kenneth
2023-08-08 10:52 ` 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=5c867303-5d03-ebed-533d-d418ea920694@amd.com \
--to=lijo.lazar@amd.com \
--cc=Kenneth.Feng@amd.com \
--cc=Maisam.Arif@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.