summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2025-04-30 15:23:14 +0300
committerMiri Korenblit <miriam.rachel.korenblit@intel.com>2025-05-06 20:22:58 +0300
commit822c7bd5ef25017883f99e120f2145320ddb8750 (patch)
treef2e3df40efc9fbf5fbacb4435408eff653b34c79 /tools/perf/scripts/python
parentb2d98a6cee3ae02a681f8cae01161ff803001e69 (diff)
downloadlinux-822c7bd5ef25017883f99e120f2145320ddb8750.tar.gz
linux-822c7bd5ef25017883f99e120f2145320ddb8750.zip
wifi: iwlwifi: implement TOP reset follower
For the upcoming SC hardware, a new reset mode "(silent) TOP reset" will be available. When BT initiates that reset, it'll negotiate with the WiFi firmware which makes it appear to the driver as the reset interrupt. To distinguish it from all the other reasons for the reset interrupt, there's (now) a status field in CSR 0x110. Implement the part of TOP reset where we react to BT doing it. This requires disambiguating the interrupt, depending on the state of the device, since we can even get TOP reset from BT while waiting for the reset handshake. If TOP reset is done by BT while we're not trying to do reset anyway, then simply reprobe, since we cannot keep the state of the device as it's being reset, after waiting the needed 180ms to let the device reset/settle. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com> Link: https://patch.msgid.link/20250430151952.fb86bfbdca40.Ibe40bf54003e3f8929b671324a395e76eb64a4d8@changeid
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions