[RFC PATCH 2/2] wifi: ath10k: only wait for response to SET_KEY
Baochen Qiang
baochen.qiang at oss.qualcomm.com
Wed Feb 25 18:59:43 PST 2026
On 2/13/2026 1:56 AM, Jeff Johnson wrote:
> On 2/11/2026 6:11 PM, James Prestwood wrote:
>> On 2/9/26 6:12 PM, Richard Acayan wrote:
>>> When sending DELETE_KEY, the driver times out waiting for a response
>>> that doesn't come. Only wait for a response when sending SET_KEY.
>>
>> We've run into the exact same thing on the QCA6174 and have been
>> carrying an identical patch to this for at least a year.
>>
>> https://lore.kernel.org/linux-wireless/b2838a23-ea30-4dee-b513-f5471d486af2@gmail.com/
>
> Baochen,
> Were we ever able to reproduce this?
unfortunately no
> Do we normally always get a response to DELETE_KEY but in some instances it
> comes very late (or not at all)?
In my tests, I never hit this issue so seems can always get a response.
> If we remove the wait, is there any concern that a late arriving DELETE_KEY
> response might be processed as a response to a subsequent SET_KEY command?
I would suggest not to remove the wait, but instead reduce the timeout to like 1s, just
like the patch "[RFC 0/1] wifi: ath10k: improvement on key removal failure".
>
> /jeff
More information about the ath10k
mailing list