mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-09 05:39:54 -04:00
drm/amd/pm: avoid false alarm due to confusing softwareshutdowntemp setting
commit 971df65cbf32da9bc9af52c1196ca504dd316086 upstream. Normally softwareshutdowntemp should be greater than Thotspotlimit. However, on some VEGA10 ASIC, the softwareshutdowntemp is 91C while Thotspotlimit is 105C. This seems not right and may trigger some false alarms. Signed-off-by: Evan Quan <evan.quan@amd.com> Acked-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Cc: stable@vger.kernel.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
f84804af09
commit
6fb192c06a
1 changed files with 12 additions and 2 deletions
|
|
@ -375,8 +375,18 @@ static int vega10_thermal_set_temperature_range(struct pp_hwmgr *hwmgr,
|
|||
/* compare them in unit celsius degree */
|
||||
if (low < range->min / PP_TEMPERATURE_UNITS_PER_CENTIGRADES)
|
||||
low = range->min / PP_TEMPERATURE_UNITS_PER_CENTIGRADES;
|
||||
if (high > tdp_table->usSoftwareShutdownTemp)
|
||||
high = tdp_table->usSoftwareShutdownTemp;
|
||||
|
||||
/*
|
||||
* As a common sense, usSoftwareShutdownTemp should be bigger
|
||||
* than ThotspotLimit. For any invalid usSoftwareShutdownTemp,
|
||||
* we will just use the max possible setting VEGA10_THERMAL_MAXIMUM_ALERT_TEMP
|
||||
* to avoid false alarms.
|
||||
*/
|
||||
if ((tdp_table->usSoftwareShutdownTemp >
|
||||
range->hotspot_crit_max / PP_TEMPERATURE_UNITS_PER_CENTIGRADES)) {
|
||||
if (high > tdp_table->usSoftwareShutdownTemp)
|
||||
high = tdp_table->usSoftwareShutdownTemp;
|
||||
}
|
||||
|
||||
if (low > high)
|
||||
return -EINVAL;
|
||||
|
|
|
|||
Loading…
Reference in a new issue