[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87il793hmi.fsf@kernel.org>
Date: Sat, 14 Oct 2023 08:20:05 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Abhishek Kumar <kuabhs@...omium.org>,
Jeff Johnson <quic_jjohnson@...cinc.com>
Cc: johannes.berg@...el.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, ath10k@...ts.infradead.org,
linux-wireless@...r.kernel.org
Subject: Re: [PATCH 2/2] ath10k: mac: enable
WIPHY_FLAG_CHANNEL_CHANGE_ON_BEACON on ath10k
Kalle Valo <kvalo@...nel.org> writes:
> Abhishek Kumar <kuabhs@...omium.org> wrote:
>
>> Enabling this flag, ensures that reg_call_notifier is called
>> on beacon hints from handle_reg_beacon in cfg80211. This call
>> propagates the channel property changes to ath10k driver, thus
>> changing the channel property from passive scan to active scan
>> based on beacon hints.
>> Once the channels are rightly changed from passive to active,the
>> connection to hidden SSID does not fail.
>>
>> Signed-off-by: Abhishek Kumar <kuabhs@...omium.org>
>
> There's no Tested-on tag, on which hardware/firmware did you test this?
>
> This flag is now enabled on ALL ath10k supported hardware: SNOC, PCI, SDIO and
> maybe soon USB. I'm just wondering can we trust that this doesn't break
> anything.
Jeff, what are your thoughts on this? I'm worried how different ath10k
firmwares can be and if this breaks something.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists