diff options
| author | Bartosz Golaszewski <[email protected]> | 2024-08-13 21:07:50 +0200 |
|---|---|---|
| committer | Bartosz Golaszewski <[email protected]> | 2024-08-19 09:55:53 +0200 |
| commit | a9aaf1ff88a8cb99a1335c9eb76de637f0cf8c10 (patch) | |
| tree | bc5267405927a72522bbcda16019aa3f20887350 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 8400291e289ee6b2bf9779ff1c83a291501f017b (diff) | |
power: sequencing: request the WLAN enable GPIO as-is
If the WCN module is powered up before linux boots and the ath11k driver
probes at the same time as the power sequencing driver, we may end up
driving the wlan-enable GPIO low in the latter, breaking the start-up of
the WLAN module. Request the wlan-enable GPIO as-is so that if the WLAN
module is already starting/started, we leave it alone.
Fixes: 2f1630f437df ("power: pwrseq: add a driver for the PMU module on the QCom WCN chipsets")
Reported-by: Stephan Gerhold <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Bartosz Golaszewski <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions