Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 7311ea85 authored by Amitkumar Karwar's avatar Amitkumar Karwar Committed by Kalle Valo
Browse files

mwifiex: fix AP start problem for newly added interface 



It's been observed that if interface type is changed from managed to
__ap, AP can be successfully started. But there is a problem if new
ap interface is added.

The problem got resolved after sending appropriate commands to firmware
in add_interface handler.

Signed-off-by: default avatarAmitkumar Karwar <akarwar@marvell.com>
Signed-off-by: default avatarCathy Luo <cluo@marvell.com>
Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
parent 568fb26e

drivers/net/wireless/marvell/mwifiex/cfg80211.c

+8 −0
Original line number Diff line number Diff line
@@ -2737,6 +2737,7 @@ struct wireless_dev *mwifiex_add_virtual_intf(struct wiphy *wiphy, 
	struct mwifiex_private *priv;

	struct net_device *dev;

	void *mdev_priv;

	int ret;



	if (!adapter)

		return ERR_PTR(-EFAULT);
@@ -2862,6 +2863,13 @@ struct wireless_dev *mwifiex_add_virtual_intf(struct wiphy *wiphy, 
	mwifiex_init_priv_params(priv, dev);

	priv->netdev = dev;



	ret = mwifiex_send_cmd(priv, HostCmd_CMD_SET_BSS_MODE,

			       HostCmd_ACT_GEN_SET, 0, NULL, true);

		return ERR_PTR(ret);



	ret = mwifiex_sta_init_cmd(priv, false, false);

		return ERR_PTR(ret);



	mwifiex_setup_ht_caps(&wiphy->bands[NL80211_BAND_2GHZ]->ht_cap, priv);

	if (adapter->is_hw_11ac_capable)

		mwifiex_setup_vht_caps(