Re: [PATCH v3 1/3] dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop

2024-04-29 Thread Kalle Valo
Bjorn Andersson writes: > On Mon, Apr 29, 2024 at 04:04:51PM +0200, Marc Gonzalez wrote: > >> 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() >>

Re: [PATCH v3 2/3] wifi: ath10k: do not always wait for MSA_READY indicator

2024-04-29 Thread Bjorn Andersson
On Mon, Apr 29, 2024 at 04:06:29PM +0200, Marc Gonzalez wrote: > The ath10k driver waits for an "MSA_READY" indicator > to complete initialization. If the indicator is not > received, then the device remains unusable. > > Several msm8998-based devices are affected by this issue. > Oddly, it seems

Re: [PATCH v3 1/3] dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop

2024-04-29 Thread Bjorn Andersson
On Mon, Apr 29, 2024 at 04:04:51PM +0200, Marc Gonzalez wrote: > 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

Re: [PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices

2024-04-29 Thread Bjorn Andersson
On Tue, Apr 30, 2024 at 12:24:40AM +0100, Bryan O'Donoghue wrote: > On 29/04/2024 15:01, Marc Gonzalez wrote: > > Work around missing MSA_READY indicator in ath10k driver > > (apply work-around for all msm8998 devices) > > > > CHANGELOG v3 > > - Add a paragraph in binding commit to explain why we

Re: [PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices

2024-04-29 Thread Bryan O'Donoghue
On 29/04/2024 15:01, Marc Gonzalez wrote: Work around missing MSA_READY indicator in ath10k driver (apply work-around for all msm8998 devices) CHANGELOG v3 - Add a paragraph in binding commit to explain why we use a DT property instead of a firmware feature bit. - Warn if the

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-04-29 Thread James Prestwood
Hi Eric, On 4/29/24 5:18 AM, Kalle Valo wrote: Eric Park writes: On 4/25/24 5:51 AM, Kalle Valo wrote: I do not use Network Manager or other connection managers when testing. It's much more reliable to use wpasupplicant directly and you get full control. I usually create a custom config

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-04-29 Thread Eric Park
On 4/29/2024 12:32 PM, Kalle Valo wrote: If the problem is on ath10k side I would rather semove support for 802.11w altogether (until it's fixed). It's controlled with this flag: ieee80211_hw_set(ar->hw, MFP_CAPABLE); Alternatively if it works on some hardware and not on others we

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-04-29 Thread Kalle Valo
Eric Park writes: > On 2024-04-29 14:18, Kalle Valo wrote: >> If you run wpa_supplicant -dddt (or similar) you get a lot of debug >> output, I'm sure it will also include the cipher. > > Good to know, thank you. Will keep this in mind the next time I'm > troubleshooting WPA-levels. > >> Very

[PATCH v3 1/3] dt-bindings: net: wireless: ath10k: add qcom,no-msa-ready-indicator prop

2024-04-29 Thread Marc Gonzalez
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,

[PATCH v3 3/3] arm64: dts: qcom: msm8998: set qcom,no-msa-ready-indicator for wifi

2024-04-29 Thread Marc Gonzalez
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,

[PATCH v3 2/3] wifi: ath10k: do not always wait for MSA_READY indicator

2024-04-29 Thread Marc Gonzalez
The ath10k driver waits for an "MSA_READY" indicator to complete initialization. If the indicator is not received, then the device remains unusable. Several msm8998-based devices are affected by this issue. Oddly, it seems safe to NOT wait for the indicator, and proceed immediately when

[PATCH v3 0/3] Work around missing MSA_READY indicator for msm8998 devices

2024-04-29 Thread Marc Gonzalez
Work around missing MSA_READY indicator in ath10k driver (apply work-around for all msm8998 devices) CHANGELOG v3 - Add a paragraph in binding commit to explain why we use a DT property instead of a firmware feature bit. - Warn if the "no_msa_ready_indicator" property is true, but we actually

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-04-29 Thread Eric Park
On 2024-04-29 14:18, Kalle Valo wrote: If you run wpa_supplicant -dddt (or similar) you get a lot of debug output, I'm sure it will also include the cipher. Good to know, thank you. Will keep this in mind the next time I'm troubleshooting WPA-levels. Very good that you found this is 802.11w

Re: QCA6174 showing terrible performance when connecting via WPA3-SAE

2024-04-29 Thread Kalle Valo
Eric Park writes: > On 4/25/24 5:51 AM, Kalle Valo wrote: > >> I do not use Network Manager or other connection managers when testing. >> It's much more reliable to use wpasupplicant directly and you get full >> control. I usually create a custom config file and then start the >> supplicant