summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/ti/wlcore/sysfs.c
diff options
context:
space:
mode:
authorWright Feng2017-08-03 11:37:59 +0200
committerKalle Valo2017-08-08 13:51:22 +0200
commit99976fc084129e07df3a066dc15651853386da19 (patch)
tree5bf8117f497219bf554a6e446c7a8cbf7e0168a2 /drivers/net/wireless/ti/wlcore/sysfs.c
parentbrcmfmac: Add support for CYW4373 SDIO/USB chipset (diff)
downloadkernel-qcow2-linux-99976fc084129e07df3a066dc15651853386da19.tar.gz
kernel-qcow2-linux-99976fc084129e07df3a066dc15651853386da19.tar.xz
kernel-qcow2-linux-99976fc084129e07df3a066dc15651853386da19.zip
brcmfmac: fix wrong num_different_channels when mchan feature enabled
When the device/firmware supports multi-channel, it can have P2P connection and regular connection with AP simultaneous. In this case, the num_different_channels in wiphy info was not correct when firmware supports multi-channel (The iw wiphy# info showed "#channels <= 1" in interface combinations). It caused association failed and error message "CTRL-EVENT-FREQ-CONFLICT error" in wpa_supplicant when P2P GO interface was running at the same time. The root cause is that the num_different_channels was always overridden to 1 in brcmf_setup_ifmodes even multi-channel was enabled. We correct the logic by moving num_different_channels setting forward. Signed-off-by: Wright Feng <wright.feng@cypress.com> Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'drivers/net/wireless/ti/wlcore/sysfs.c')
0 files changed, 0 insertions, 0 deletions