mbox series

[0/2] Update the channel list if the change in channel flags

Message ID 20221222124221.30894-1-quic_youghand@quicinc.com (mailing list archive)
Headers show
Series Update the channel list if the change in channel flags | expand

Message

Youghandhar Chintala Dec. 22, 2022, 12:42 p.m. UTC 
There are connection failures in hidden SSID case when the device is with
default reg domain WW.
For WW reg domain most of the 5 GHz channels are passive. When device
listens to the beacon on that channel, the driver is updating its channel
flag but firmware is not aware of it and firmware is not sending probes
on that channels.
Due to this, we are seeing connection failures when the device is tries to
connect with hidden SSID AP.
Whenever the driver detects a channel flag change, send the updated channel
list command to the firmware.

Youghandhae Chintala (2):
  wifi: cfg80211: Add beacon hint notifier support
  wifi: ath10k: update the channel list if change in channel flags.

 drivers/net/wireless/ath/ath10k/mac.c | 11 +++++++++++
 include/net/cfg80211.h                |  2 ++
 net/wireless/reg.c                    |  5 ++++-
 3 files changed, 17 insertions(+), 1 deletion(-)

Comments

Kalle Valo Dec. 22, 2022, 2 p.m. UTC | #1 
Youghandhar Chintala <quic_youghand@quicinc.com> writes:

> There are connection failures in hidden SSID case when the device is with
> default reg domain WW.
> For WW reg domain most of the 5 GHz channels are passive. When device
> listens to the beacon on that channel, the driver is updating its channel
> flag but firmware is not aware of it and firmware is not sending probes
> on that channels.
> Due to this, we are seeing connection failures when the device is tries to
> connect with hidden SSID AP.
> Whenever the driver detects a channel flag change, send the updated channel
> list command to the firmware.
>
> Youghandhae Chintala (2):
>   wifi: cfg80211: Add beacon hint notifier support
>   wifi: ath10k: update the channel list if change in channel flags.

If you submit patches again, please _always_ increase the version number
(ie. this one should be v2). Now there are two v1 patchsets and
difficult for maintainers to pick which one to take.

But don't resend the patchset just because of this. Hopefully this mail
makes it clear that this is v2.