3df8057ced9033d2b26f9ce696ff5f5b9bff634c
[openwrt/openwrt.git] /
1 From fa9050927fa885410055ee03c948c2252693d296 Mon Sep 17 00:00:00 2001
2 From: Arend van Spriel <arend.vanspriel@broadcom.com>
3 Date: Thu, 11 Jul 2019 10:45:32 +0200
4 Subject: [PATCH] brcmfmac: allow 160MHz in custom regulatory rules
5
6 The driver has custom regulatory rules which had maximum bandwidth
7 for 5GHz channels set to 80MHz. As a consequence the driver can
8 not use 160MHz in AP mode even when the device supports it. So
9 relax the rules allowing 160MHz. After wiphy_register() the channel
10 flags are updated according what the device actually supports.
11
12 Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
13 Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
14 Reviewed-by: Franky Lin <franky.lin@broadcom.com>
15 Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
16 Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
17 ---
18 drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 4 ++--
19 1 file changed, 2 insertions(+), 2 deletions(-)
20
21 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
22 +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
23 @@ -189,9 +189,9 @@ static const struct ieee80211_regdomain
24 */
25 REG_RULE(2484-10, 2484+10, 20, 6, 20, 0),
26 /* IEEE 802.11a, channel 36..64 */
27 - REG_RULE(5150-10, 5350+10, 80, 6, 20, 0),
28 + REG_RULE(5150-10, 5350+10, 160, 6, 20, 0),
29 /* IEEE 802.11a, channel 100..165 */
30 - REG_RULE(5470-10, 5850+10, 80, 6, 20, 0), }
31 + REG_RULE(5470-10, 5850+10, 160, 6, 20, 0), }
32 };
33
34 /* Note: brcmf_cipher_suites is an array of int defining which cipher suites