summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorMiri Korenblit <miriam.rachel.korenblit@intel.com>2025-09-15 11:34:24 +0300
committerMiri Korenblit <miriam.rachel.korenblit@intel.com>2025-10-28 16:05:17 +0200
commit5c0251598f29646a19a7232c9437b6faa22ab4c2 (patch)
tree5cff71ae5afa2079de0899912337938d44b61431 /tools/perf/scripts/python
parent9dc6e9dfdf9d9efe5afd2322e450b83a449993db (diff)
wifi: iwlwifi: mld: reschedule check_tpt_wk also not in EMLSR
When the throughput count reaches the threshold, EMLSR is no longer blocked by throughput. This doesn't mean that EMLSR will be activated immediately, since there might be other reasons that block EMLSR. When the throughput blocker is not set, check_tpt_wk should run every 5 seconds and check if the throughput blocker should be set (if the throughtput counter dropped). If not, it should reschedule itself. In the current code, the worker will reschedule itself only if we are in EMLSR. This is wrong, since we might be in a case where the throughput blocker is not set but we are not in EMLSR, and then we will never check again the throughput counters (and block EMLSR if needed). Fix this by rescheduling the worker also when EMLSR is not active. Reviewed-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com> Link: https://patch.msgid.link/20250915113137.2a9cf2b2529d.I8284c0da9597e4c963e38ae133384f6f42044499@changeid
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions