diff options
| author | Avinash Patil <patila@marvell.com> | 2015-06-05 01:01:54 +0530 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2015-06-08 11:49:47 +0300 |
| commit | 39d94eaa76e774f7dc4f3f338bf576d850f2ba11 (patch) | |
| tree | f205cb6fce5b870ed394a3329e25b99d6b015119 | |
| parent | 7a56c4168e4453732c35b1e33a683d91f04f379f (diff) | |
mwifiex: update current config_band info in start_ap
It was observed that AP beacons would not reflect correct regulatory
information upon starting AP in A band. This was because of missing
AP config band update in set_channel of start_ap.
Signed-off-by: Avinash Patil <patila@marvell.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
| -rw-r--r-- | drivers/net/wireless/mwifiex/uap_cmd.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/net/wireless/mwifiex/uap_cmd.c b/drivers/net/wireless/mwifiex/uap_cmd.c index a62b43ea9e2a..b74930054b8c 100644 --- a/drivers/net/wireless/mwifiex/uap_cmd.c +++ b/drivers/net/wireless/mwifiex/uap_cmd.c @@ -832,6 +832,8 @@ void mwifiex_uap_set_channel(struct mwifiex_private *priv, if (chandef.width > NL80211_CHAN_WIDTH_40) config_bands |= BAND_AAC; } + + priv->adapter->config_bands = config_bands; } int mwifiex_config_start_uap(struct mwifiex_private *priv, |