- Jul 12, 2011
-
-
Felix Fietkau authored
The radio seems to perform better that way Signed-off-by:
Felix Fietkau <nbd@openwrt.org> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Felix Fietkau authored
Now that the clock rate is initialized properly and SIFS, EIFS, USEC, slot time and ACK timeout are properly calculated by the generic code, the 'async FIFO' register hacks are no longer necessary. Signed-off-by:
-
Felix Fietkau authored
Initialize the the clock-to-TSF field of AR_USEC and the SIFS and EIFS time registers based on the clock rate instead of relying on initvals. With those changes, some of the hardcoded AR9287 1.3+ specific overrides can be dropped. Signed-off-by:
-
Felix Fietkau authored
This chip uses the async FIFO feature and runs the MAC at 117 MHz Signed-off-by:
-
Felix Fietkau authored
Enabling half/quarter rate makes the MAC run at half/quarter clock speed. Signed-off-by:
-
Felix Fietkau authored
All devices support this, but some disable it using an EEPROM flag for some reason. Improves 5 GHz performance on those devices. Signed-off-by:
-
Felix Fietkau authored
Use the proper masks for the register instead. Fixes adding the (still unused) half/quarter PLL flags. Signed-off-by:
-
Amitkumar Karwar authored
Currently device is not able to transmit in 40MHz in spite of enabling 40MHz support in HTCapInfo IE in assoc req, because 11n specific FW capabilities for transmission are not initialized. This patch adds code to initilize these capabilities. Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
Yogesh Ashok Powar <yogeshp@marvell.com> Signed-off-by:
Kiran Divekar <dkiran@marvell.com> Signed-off-by:
Bing Zhao <bzhao@marvell.com> Signed-off-by:
-
Don Fry authored
Not needed since the driver split. Move single use routines to calling location and keep static where possible. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
For testing purpose, we need better control of msc from user application. Separate the fixed_rate between debugfs and testmode and enforce it. Signed-off-by:
Kenny Hsu <kenny.hsu@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
The only host command allow to send to uCode is the one initiated from testmode if testmode is the owner of uCode Signed-off-by:
-
Wey-Yi Guy authored
Since we open the door to allow application control the device behavior through testmode, add command to allow application request the ownership of the uCode Signed-off-by:
-
Wey-Yi Guy authored
For all the hist command request from testmode, set the CMD_ON_DEMAND flag. this flag will be used later to control the uCode behavior Signed-off-by:
-
Wey-Yi Guy authored
Declare iwl_mac_rssi_callback as "static" Signed-off-by:
-
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:
-
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:
-
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
-
- Jul 11, 2011
-
-
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>
-
- Jul 09, 2011
-
-
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:
-
