103-v5.4-0003-brcmfmac-allow-160MHz-in-custom-regulatory-rules.patch 1.5 KB

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