summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAlexander Sverdlin <alexander.sverdlin@siemens.com>2026-09-29 14:08:02 +0200
committerUwe Kleine-König <ukleinek@kernel.org>2026-09-30 08:13:35 +0200
commite74b9a7ee50071aad25d3989bf985292f90b0c6e (patch)
treefd1f630d5a7600ebcc33da706149e3419513afcb /tools/perf/scripts/python
parent45c3d07e3f18cff2b3ea8b797387451a3df9d421 (diff)
downloadlinux-next-e74b9a7ee50071aad25d3989bf985292f90b0c6e.tar.gz
linux-next-e74b9a7ee50071aad25d3989bf985292f90b0c6e.zip
pwm: tiehrpwm: Clear period on disable to allow reconfiguration
Both channels share one period register, so ehrpwm_pwm_config() rejects a period differing from the sibling's period_cycles[]. That value was cleared only in .free(), not in .disable(), so a stopped channel kept blocking the sibling from switching to a new frequency. Clear it in .disable() too. Testcase: cd /sys/class/pwm/pwmchip0; echo 0 > export; echo 1 > export for p in pwm0 pwm1; do echo 1000000 > $p/period; echo 500000 > $p/duty_cycle echo 1 > $p/enable; echo 0 > $p/enable; echo 2000000 > $p/period done echo 1 > pwm0/enable # before: -EINVAL, after: succeeds Fixes: 01b2d4536f02 ("pwm: pwm-tiehrpwm: Fix conflicting channel period setting") Cc: stable@vger.kernel.org Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com> Link: https://patch.msgid.link/20260929120806.2790355-1-alexander.sverdlin@siemens.com Signed-off-by: Uwe Kleine-König <ukleinek@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions