diff options
| author | Brian Norris <briannorris@chromium.org> | 2019-02-14 16:31:29 -0800 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2019-02-19 17:15:44 +0200 |
| commit | 6f21ab30469d670de620f758330aca9f3433f693 (patch) | |
| tree | ae4352e52dccc855e9f9ac6325ecb3ae93e0d154 /drivers/fsi/fsi-occ.c | |
| parent | 65a576e27309120e0621f54d5c81eb9128bd56be (diff) | |
| download | linux-6f21ab30469d670de620f758330aca9f3433f693.tar.bz2 | |
mwifiex: don't advertise IBSS features without FW support
As it is, doing something like
# iw phy phy0 interface add foobar type ibss
on a firmware that doesn't have ad-hoc support just yields failures of
HostCmd_CMD_SET_BSS_MODE, which happened to return a '-1' error code
(-EPERM? not really right...) and sometimes may even crash the firmware
along the way.
Let's parse the firmware capability flag while registering the wiphy, so
we don't allow attempting IBSS at all, and we get a proper -EOPNOTSUPP
from nl80211 instead.
Fixes: e267e71e68ae ("mwifiex: Disable adhoc feature based on firmware capability")
Signed-off-by: Brian Norris <briannorris@chromium.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'drivers/fsi/fsi-occ.c')
0 files changed, 0 insertions, 0 deletions