diff options
| author | Marc Gonzalez <[email protected]> | 2024-04-29 16:07:27 +0200 |
|---|---|---|
| committer | Bjorn Andersson <[email protected]> | 2024-05-28 16:13:18 -0500 |
| commit | 737abcabe97bb37e38be2504acd28ad779dbaf3d (patch) | |
| tree | ed0f9a1461b84b1b9d34bc347f9cda7a5f99781c /tools/perf/scripts/python/flamegraph.py | |
| parent | ffaa4b5d5d07aed600d82929d8862263ce341a71 (diff) | |
arm64: dts: qcom: msm8998: set qcom,no-msa-ready-indicator for wifi
The ath10k driver waits for an "MSA_READY" indicator
to complete initialization. If the indicator is not
received, then the device remains unusable.
cf. ath10k_qmi_driver_event_work()
Several msm8998-based devices are affected by this issue.
Oddly, it seems safe to NOT wait for the indicator, and
proceed immediately when QMI_EVENT_SERVER_ARRIVE.
Jeff Johnson wrote:
The feedback I received was "it might be ok to change all ath10k qmi
to skip waiting for msa_ready", and it was pointed out that ath11k
(and ath12k) do not wait for it.
However with so many deployed devices, "might be ok" isn't a strong
argument for changing the default behavior.
cf. also
https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)#WLAN
Signed-off-by: Marc Gonzalez <[email protected]>
Acked-by: Jeff Johnson <[email protected]>
Reviewed-by: Konrad Dybcio <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Bjorn Andersson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions