Yes, 32a0000.pwm is currently in use
I have also modified /etc/nvfancontrol.conf
POLLING_INTERVAL 2
<FAN 1>
TMARGIN ENABLED
FAN_GOVERNOR cont {
STEP_SIZE 10
}
FAN_CONTROL close_loop {
RPM_TOLERANCE 100
}
FAN_PROFILE quiet {
#TEMP HYST PWM RPM
0 0 255 5000
10 0 255 5000
30 0 190 4000
40 0 130 3000
55 0 80 1800
105 0 80 1800
}
FAN_PROFILE cool {
#TEMP HYST PWM RPM
0 0 255 6000
35 0 255 6000
70 0 0 0
105 0 0 0
}
THERMAL_GROUP 0 {
GROUP_MAX_TEMP 105
#Thermal-Zone Coeffs Max-Temp
CPU-therm 20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0
GPU-therm 20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0
SOC0-therm 20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0
SOC1-therm 20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0
SOC2-therm 20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 0
}
FAN_DEFAULT_CONTROL close_loop
FAN_DEFAULT_PROFILE quiet
FAN_DEFAULT_GOVERNOR cont
KICKSTART_PWM 64
However, when I measured the PWM frequency signal after turning it on, it still remained at 60k~100kHz.
This phenomenon occurs in development kits and customized boards.