aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/flamegraph.py
diff options
context:
space:
mode:
authorBaochen Qiang <quic_bqiang@quicinc.com>2025-03-28 13:32:27 +0800
committerJeff Johnson <jeff.johnson@oss.qualcomm.com>2025-03-31 14:43:12 -0700
commit88fd03cf51a7d67dac976ecce079ccfc79376966 (patch)
treee599f9b6b4cfb33567471ac2184b7e628f4a6779 /tools/perf/scripts/python/flamegraph.py
parentwifi: ath11k: refactor ath11k_core_suspend/_resume() (diff)
downloadlinux-88fd03cf51a7d67dac976ecce079ccfc79376966.tar.gz
linux-88fd03cf51a7d67dac976ecce079ccfc79376966.zip
wifi: ath11k: support non-WoWLAN mode suspend as well
Previously commit 166a490f59ac ("wifi: ath11k: support hibernation") was reverted due to [1], so currently we only support WoWLAN mode suspend. This works well in scenarios where WLAN power is sustained during suspend, however breaks in those where power is cut off. This change basically brings the reverted commit back, but differs in that we decide based on the PM policy to choose WoWLAN mode suspend or the non-WoWLAN mode. As stated in the previous patch for now the PM policy is determined based on machine models. That said we will choose WoWLAN mode suspend if we are running on machines listed in ath11k_pm_quirk_table, otherwise we choose the other one. [1] https://bugzilla.kernel.org/show_bug.cgi?id=219196 Tested-on: WCN6855 hw2.0 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.30 Tested-by: Muhammad Usama Anjum <usama.anjum@collabora.com> Tested-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Baochen Qiang <quic_bqiang@quicinc.com> Link: https://patch.msgid.link/20250328-ath11k-bring-hibernation-back-v3-4-23405ae23431@quicinc.com Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions