- 30 Oct, 2012 5 commits
-
-
Johannes Berg authored
Even before channel contexts/multi-channel, having a single global TX power limit was already problematic, in particular if two managed interfaces connected to two APs with different power constraints. The channel context introduction completely broke this though and in fact I had disabled TX power configuration there for drivers using channel contexts. Change everything to track TX power per interface so that different user settings and different channel maxima are treated correctly. Also continue tracking the global TX power though for compatibility with applications that attempt to configure the wiphy's TX power globally. Signed-off-by:Johannes Berg <johannes.berg@intel.com>
-
Johannes Berg authored
The TX power setting is currently per wiphy (hardware device) but with multi-channel capabilities that doesn't make much sense any more. Allow drivers (and mac80211) to advertise support for per-interface TX power configuration. When the TX power is configured for the wiphy, the wdev will be NULL and the driver can still handle that, but when a wdev is given the TX power can be set only for that wdev now. Signed-off-by: -
Johannes Berg authored
Setting the wdev to NULL when the channel can't be set for that interface type (to treat the channel setting for the wiphy/monitor) currently works, but is confusing in the code if netdev/wdev aren't both set/unset in the same way. Move the check whether the channel can be set to where it's needed so that wdev and netdev are always both assigned or NULL. Signed-off-by: -
Johannes Berg authored
To use mac80211_hwsim for testing channel contexts it has to support them, and for that it has to support hw scan and hw-remain-on-channel. Since it's pure software, the off-channel activities are really not off-channel but listening and sending on a second channel. Also, the multi-channel isn't really doing TDM, it's just on both channels at the same time. For testing purposes, you can specify the number of concurrent channels with a module parameter, it is set to one by default. When set to two or more, the userspace API for wmediumd is disabled as it has no provisions for multi-channel yet. Signed-off-by: -
Johannes Berg authored
-
- 29 Oct, 2012 35 commits
-
-
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wirelessJohn W. Linville authored
Conflicts: drivers/net/wireless/mwifiex/cfg80211.c
-
Hauke Mehrtens authored
The BCM43222 with the chipid 43222 or 0xa8d6 in hex do not need any special handling in the pmu code. This prevents some error messages being shown. Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Hauke Mehrtens authored
14e4:4350 is found on a Broadcom BCM43222. Signed-off-by:
-
Rajkumar Manoharan authored
Signed-off-by:
Rajkumar Manoharan <rmanohar@qca.qualcomm.com> Signed-off-by:
-
Rajkumar Manoharan authored
Signed-off-by:
-
Rajkumar Manoharan authored
Whenever WLAN receives scheduling msg from BT, it reduces tx power based on RSSI level. And then BT starts simultaneous transmission along with WLAN. Sometimes HW MAC compares tx power that is used prior to power reduction which is causing BT transmission to defer. Signed-off-by:
-
Rajkumar Manoharan authored
This reduced the power consumption to half in full and network sleep. Signed-off-by:
-
Rajkumar Manoharan authored
This reduced the power consumption to half in full and network sleep. Cc: stable@vger.kernel.org Cc: Paul Stewart <pstew@chromium.org> Signed-off-by:
-
Pontus Fuchs authored
This driver is for the AR5523 chipset from Atheros. It was created in 2007 by Christoph Hellwig but it was never finished. I found it a couple of months ago and after some polishing it's working pretty fine. The driver was written with the FreeBSD driver (uath) as reference, which was written with the reverse-engineered windows driver as reference, hence the feature set is very limited. Station mode only, no HW crypto offload. Signed-off-by:
Pontus Fuchs <pontus.fuchs@gmail.com> Signed-off-by:
-
Arend van Spriel authored
For AP feature the IEs are stored in global structure. For future functionality like P2P-GO it needs to be stored per virtual interface so better store it in the virtual interface structure. Reviewed-by:
Hante Meuleman <meuleman@broadcom.com> Reviewed-by:
Pieter-Paul Giesberts <pieterpg@broadcom.com> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
Franky Lin <frankyl@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
The macro wiphy_to_cfg() is a bit redundant as the function already has a pointer variable to brcmf_cfg80211_info structure. Reviewed-by:
-
Arend van Spriel authored
With multiple interfaces suspend will need to iterate over all and bring down the link. Reviewed-by:
-
Arend van Spriel authored
The driver had a global constant ether_bcast, which was copied whenever a broadcast mac address was needed. This patch does a memset(dest, 0xFF, ETH_ALEN) instead and consequently removes the global ether_bcast. Reviewed-by:
-
Arend van Spriel authored
The function now return the status for a virtual interface so it seems better rename the function to understand what it does. Reviewed-by:
-
Arend van Spriel authored
The enumeration wl_prof_list is no longer used so it can be safely removed. Reviewed-by:
-
Arend van Spriel authored
A couple of unused fields have been removed and kernel-doc info has been added to the structure. Reviewed-by:
-
Arend van Spriel authored
In wl_cfg80211.c debugfs directory was created to expose dtim_period and beacon_interval. However, this can be easily obtained using iw so it is removed from the driver. Reviewed-by:
-
Arend van Spriel authored
The connection status is to be kept per virtual interface and the scanning status is for device. So they need to be separated for multiple interface support. Reviewed-by:
-
Arend van Spriel authored
This checks the status that will soon be moved to virtual interface data so preparing for that use the structure brcmf_cfg80211_vif as parameter instead. Reviewed-by:
-
Arend van Spriel authored
The profile information applies to an interface so each virtual interface needs it. So it is removed from brcmf_cfg80211_info and added to brcmf_cfg80211_vif structure. Reviewed-by:
-
Arend van Spriel authored
This patch introduces the brcmf_cfg80211_vif structure which is used to keep track of multiple virtual interfaces in the driver. Reviewed-by:
-
Arend van Spriel authored
The function brcmf_find_bssidx() is no longer used so remove it from the driver code. Reviewed-by:
-
Arend van Spriel authored
The first two parameters given to send_key_to_dongle() are redundant so they have been removed. Reviewed-by:
-
Hante Meuleman authored
modify the setup code to use the refactored firmware interface layer. Reviewed-by:
-
Franky Lin authored
Use brcmf_sdio_hdparser to handle header of super frame and sub frame in glomming frame read. Signed-off-by:
-
Arend van Spriel authored
The functions for communicating were given the net_device only because its private data contained struct brcmf_if object. However, not all firmware related interfaces will be associated with a net_device. To accomodate provisioning firmware for such interfaces the struct brcmf_if object will be passed to the fwil functions. Reviewed-by:
-
Arend van Spriel authored
The firmware carries channel information in a different format as the provided ieee80211_channel structure. Conversion is needed when receiving requests from cfg80211 carrying ieee80211_channel structures. This patch adds a utility function to do that. Reviewed-by:
-
Arend van Spriel authored
The firmware interface has functions to send bsscfg specific commands to the device. These functions currently have a bssidx parameter, but that same information is stored in struct brcmf_if, which is in the private data of the net_device parameter. Reviewed-by:
-
Arend van Spriel authored
In brcmf_bus_start() a number of settings are sent to the device. For this functions are used that bypass the common firmware interface. By reordering the code in brcmf_bus_start() this bypass can be removed. Signed-off-by:
-
Arend van Spriel authored
When the firmware notifies the driver about adding a new interface it also provides an index for the bss associated with this interface. This index will be needed for upcoming features like peer-to-peer. By adding this index in struct brcmf_if it is easy to obtain as this will be associated with the net_device private data. Signed-off-by:
-
Hante Meuleman authored
reuse ioctl waiting method. Reviewed-by:
-
Hante Meuleman authored
function brcmf_c_mkiovar_bsscfg became redundant with refactoring of firmware interface layer. Reviewed-by:
-
Hante Meuleman authored
switch to new firmware interface layer and remove redundant code. Reviewed-by:
-
Hante Meuleman authored
Variable iswl always gets initialised to the same and support for this var is not needed. Reviewed-by:
-
Hante Meuleman authored
Refactor the functions that are related to getting and setting data to and and from the firmware. Reviewed-by:
-
