Commit 737abcab authored by Marc Gonzalez's avatar Marc Gonzalez Committed by Bjorn Andersson
Browse files

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: default avatarMarc Gonzalez <mgonzalez@freebox.fr>
Acked-by: default avatarJeff Johnson <quic_jjohnson@quicinc.com>
Reviewed-by: default avatarKonrad Dybcio <konrad.dybcio@linaro.org>
Link: https://lore.kernel.org/r/0914f96e-fcfd-4088-924a-fc1991bce75f@freebox.fr


Signed-off-by: default avatarBjorn Andersson <andersson@kernel.org>
parent ffaa4b5d

arch/arm64/boot/dts/qcom/msm8998.dtsi

+1 −0
Original line number Diff line number Diff line
@@ -3194,6 +3194,7 @@ wifi: wifi@18800000 { 
			iommus = <&anoc2_smmu 0x1900>,

				 <&anoc2_smmu 0x1901>;

			qcom,snoc-host-cap-8bit-quirk;

			qcom,no-msa-ready-indicator;

		};

	};

};