- 11 Jul, 2011 18 commits
-
-
Meenakshi Venkataraman authored
WiFi throughput drops drastically when BT is turned on, BT and WiFi are simultaneously transmitting/receiving traffic. This is particularly true when BT has higher priority over WiFi, and hence the device defers TX frames. The AP assumes that the channel is bad and reduces the data rate, implying longer airtime, which exacerbates the problem further, resulting ultimately in what is popularly called the "death-spiral" phenomenon. The use of PS-poll in such scenarios guarantees a low but consistent throughput. Since the death-spiral phenomenon is observed only when the RSSI is low, use PS-poll only when RSSI is low and disable when high, with a known hysterisis. This feature specifies the high and low thresholds and implements the callbacks registered with mac80211, which will be called when threshold events occur. iwlwifi: dynamic pspoll: optimize rssi monitor code Signed-off-by:
Meenakshi Venkataraman <meenakshi.venkataraman@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Meenakshi Venkataraman authored
mac80211 maintains a running average of the RSSI when a STA is associated to an AP. Report threshold events to any driver that has registered callbacks for getting RSSI measurements. Implement callbacks in mac80211 so that driver can set thresholds. Add callbacks in mac80211 which is invoked when an RSSI threshold event occurs. mac80211: add tracing to rssi_reports api and remove extraneous fn argument mac80211: scale up rssi thresholds from driver by 16 before storing Signed-off-by:
-
Wey-Yi Guy authored
For bt combo devices, need to use bt enabled handlers and functions Reported-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
No need to do double level indirect call after driver split no functional changes Signed-off-by:
-
Fry, Donald H authored
Not needed since the driver split. Eliminate redundant routine. Signed-off-by:
-
Fry, Donald H authored
Not needed since the driver split. Signed-off-by:
-
Fry, Donald H authored
Not needed since the driver split. Signed-off-by:
-
Emmanuel Grumbach authored
This removes the for priv->trans.ops->... Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
Not needed since the driver split. Signed-off-by:
-
Emmanuel Grumbach authored
Now, there are only two functions to send a host command: * send_cmd that receives a iwl_host_cmd * send_cmd_pdu that builds the iwl_host_cmd itself and received flags The flags CMD_ASYNC / CMD_SYNC / CMD_WANT_SKB are not changed by the API functions. Kill the unused flags CMD_SIZE_NORMAL / CMD_NO_SKB on the way. Signed-off-by:
-
Emmanuel Grumbach authored
Code duplication was needed during the move, not needed any more. Signed-off-by:
-
Emmanuel Grumbach authored
Tx stop moves to transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Rx stop moves to transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Tx free functions move to the transport layer. Unify the functions that deal with tx queues and cmd queue. Since the CMD queue is not fully allocated, but uses the q->n_bd / q->window trick, the release flow of TX queue and CMD queue was different. iwlagn_txq_free_tfd receives now the index of the TFD to be freed, which allows to unify the release flow for all the queues. Signed-off-by:
-
Emmanuel Grumbach authored
It is uneeded since Johannes removed the HUGE flag. The DMA mapping is always held in the same index as the command. Signed-off-by:
-
John W. Linville authored
Conflicts: net/bluetooth/l2cap_core.c
-
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6John W. Linville authored
Conflicts: drivers/net/wireless/ath/ath5k/sysfs.c net/bluetooth/l2cap_core.c net/mac80211/wpa.c
-
Ilia Kolomisnky authored
There can 3 reasons for the "command reject" reply produced by the stack. Each such reply should be accompanied by the relevand data ( as defined in spec. ). Currently there is one instance of "command reject" reply with reason "invalid cid" wich is fixed. Also, added clean-up definitions related to the "command reject" replies. Signed-off-by:
Ilia Kolomisnky <iliak@ti.com> Signed-off-by:
Gustavo F. Padovan <padovan@profusion.mobi>
-
- 08 Jul, 2011 22 commits
-
-
Vinicius Costa Gomes authored
This will be useful when userspace wants to restrict some kinds of operations based on the length of the key size used to encrypt the link. Signed-off-by:
Vinicius Costa Gomes <vinicius.gomes@openbossa.org> Signed-off-by:
-
Vinicius Costa Gomes authored
In some cases it will be useful having the key size used for encrypting the link. For example, some profiles may restrict some operations depending on the key length. The key size is stored in the key that is passed to userspace using the pin_length field in the key structure. For now this field is only valid for LE controllers. 3.0+HS controllers define the Read Encryption Key Size command, this field is intended for storing the value returned by that command. Signed-off-by:
-
Vinicius Costa Gomes authored
As the key format has changed to something that has a dynamic size, the way that keys are received and sent must be changed. The structure fields order is changed to make the parsing of the information received from the Management Interface easier. Signed-off-by:
-
Vinicius Costa Gomes authored
Signed-off-by:
-
Vinicius Costa Gomes authored
Now that it's possible that the exchanged key is present in the link key list, we may be able to estabilish security with an already existing key, without need to perform any SMP procedure. Signed-off-by:
-
Vinicius Costa Gomes authored
With this we can use only one place to store all keys, without need to use a field in the connection structure for this purpose. Signed-off-by:
-
Vinicius Costa Gomes authored
Now when the LTK is received from the remote or generated it is stored, so it can later be used. Signed-off-by:
-
Vinicius Costa Gomes authored
Before implementing SM key distribution, the pairing features exchange must be better negotiated, taking into account some features of the host and connection requirements. If we are in the "not pairable" state, it makes no sense to exchange any key. This allows for simplification of the key negociation method. Signed-off-by:
-
Vinicius Costa Gomes authored
Now that we have methods to finding keys by its parameters we can reject an encryption request if the key isn't found. Signed-off-by:
-
Vinicius Costa Gomes authored
As the LTK (the new type of key being handled now) has more data associated with it, we need to store this extra data and retrieve the keys based on that data. Methods for searching for a key and for adding a new LTK are introduced here. Signed-off-by:
-
Vinicius Costa Gomes authored
We need these changes because SMP keys may have more information associated with them, for example, in the LTK case, it has an encrypted diversifier (ediv) and a random number (rand). Signed-off-by:
-
Vinicius Costa Gomes authored
This adds support for generating and distributing all the keys specified in the third phase of SMP. This will make possible to re-establish secure connections, resolve private addresses and sign commands. For now, the values generated are random. Signed-off-by:
-
Rajkumar Manoharan authored
Recent firmware changes report tx ack status properly to driver. Hence updating ath9k_htc driver capabilities. Signed-off-by:
Rajkumar Manoharan <rmanohar@qca.qualcomm.com> Signed-off-by:
-
Rajkumar Manoharan authored
This patch removes read only registers that cause invalid address access and also updates index for measurement filter calibration window size. Signed-off-by:
-
Rajkumar Manoharan authored
The power detector calibration is disabled because this block doesn't exist in AR9003 based chips and also parallel calibration is enabled otherwise the calibration will never stop. Signed-off-by:
-
Rajkumar Manoharan authored
The number of temperature reading samples to average during a Tx packet is decreased to 1 from 2 to improve 5G Tx EVM with chain 0-only mode. Signed-off-by:
-
Luciano Coelho authored
If we try to stop a scheduled scan while it is not running, we should return -ENOENT instead of simply ignoring the command and returning success. This is more consistent with other parts of the code. Reported-by:
Johannes Berg <johannes@sipsolutions.net> Signed-off-by:
Luciano Coelho <coelho@ti.com> Signed-off-by:
-
Mohammed Shafi Shajakhan authored
Signed-off-by:
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> Signed-off-by:
-
Yogesh Ashok Powar authored
In XMIT path, the skb that we get from the kernel itself is not aligned with 4-byte boundary on some embedded platforms. Had it not been the presence of tx_pkt_offset field in txpd, 4 byte memory alignment was not possible without memmove of entire skb. And that would have increased MIPS instead of reducing. With this patch few memory cycles can be saved while fetching interface header and txpd structure because of 4 bytes memory alignment. Reported-by:
Philip Rakity <prakity@marvell.com> Signed-off-by:
Yogesh Ashok Powar <yogeshp@marvell.com> Tested-by:
Bing Zhao <bzhao@marvell.com> Signed-off-by:
-
Amitkumar Karwar authored
Debugfs command 'info' shows wrong interface type. The regression occurred due to commit eecd8250 (mwifiex: remove MWIFIEX_BSS_MODE_ macros) in which we replaced MWIFIEX_BSS_MODE_* macros by NL80211_IFTYPE_*, for example, MWIFIEX_BSS_MODE_IBSS (2) --> NL80211_IFTYPE_ADHOC (1) The issue is fixed by swapping static character array used to display interface type information. Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
-
Amitkumar Karwar authored
Htcapinfo is unnecessarily sent in assoc request in WEP security due to a regression introduced by commit 2be50b8d (mwifiex: remove redundant encryption_mode mapping). The issue is fixed in this patch. Signed-off-by:
-
Pavel Roskin authored
Signed-off-by:
Pavel Roskin <proski@gnu.org> sc->imask may change if ath5k_set_current_imask() races against itself. Signed-off-by:
-
