- 25 Apr, 2011 38 commits
-
-
Johannes Berg authored
Currently, the code to tear down BA sessions will execute after queues are stopped, but attempt to send frames, so those frames will just get queued, which isn't intended. Move this code to before to tear down the sessions properly. Additionally, after stopping queues, flush the TX queues in the driver driver to make sure all the frames went out. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Nishant Sarmukadam authored
Tell the firmware to enable the life time expiry of tx packets in the hardware. The hardware will now refer to the timestamp in every tx packet and decide whether the packet needs to be dropped or transmitted. Signed-off-by:
Nishant Sarmukadam <nishants@marvell.com> Signed-off-by:
Pradeep Nemavat <pnemavat@marvell.com> Signed-off-by:
-
Nishant Sarmukadam authored
Since queues are not stopped anymore, management frames would be dropped if the corresponding tx queue is full. This can cause issues say when we want to setup an ampdu stream and action frames i.e addba requests keep getting dropped frequently. Fix this by reserving some buffers to allow management frames to go through in queue full conditions. Signed-off-by:
-
Pradeep Nemavat authored
Timestamp tx packets using a HW micro-second timer. This timestamp will be compared to the current timestamp in the hardware and if the difference is greater than 500ms, the packet will be dropped. Signed-off-by:
-
Pradeep Nemavat authored
This is in preparation to support life time expiry of packets in the hardware to avoid head-of-line blocking where a slow client can hog a tx queue and affect the traffic to a faster client from the same queue. Time stamp the packets in driver to allow dropping them in the hardware if they are queued for more than 500ms. If queues are stopped, packets will be queued up outside the driver. Since we will be able to timestamp the packets only after they hit the driver, the timestamp will be less accurate since we cannot consider the time the packets spent in queues outside the driver. With this commit, to achieve accurate timestamping, the tx queues will not be stopped in normal conditions. The only scenarios where the queues will be stopped are when firmware commands are executing or if the interface is brought down. Now, we need to be prepared for a situation where packets hit the driver even after the tx queues are full. Drop all such packets in the driver itself. Signed-off-by:
-
Stanislaw Gruszka authored
My commit 3598e177 "iwlwifi: fix enqueue hcmd race conditions" move hcmd callback after command queue reclaim, to avoid call it with hcmd_lock. But since queue read index was updated, cmd data can be overwritten. Fix problem by calling callback before taking hcmd_lock and queue reclaim. Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Acked-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
-
Rafał Miłecki authored
We probably got false positive results for checking PLL being down. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
-
Sujith Manoharan authored
Signed-off-by:
Sujith Manoharan <Sujith.Manoharan@atheros.com> Signed-off-by:
-
Sujith Manoharan authored
Signed-off-by:
-
Sujith Manoharan authored
Set the maximum ampdu size of a station correctly in the target by using the ampdu_factor. Signed-off-by:
-
Sujith Manoharan authored
* Register the driver's maximum ampdu subframe limit to mac80211. * Cleanup the target capabilities structure and fix an endian issue. * Fix BTCOEX by sending a command to the target when the BT priority changes. * Bump the required firmware version to 1.1 Signed-off-by:
-
Sujith Manoharan authored
Signed-off-by:
-
Rafał Miłecki authored
Default min_msk on my 0x4312 is 0x80000CBB, not 0xCBB. Now we follow specs and wl (noticed in MMIO dumps). Signed-off-by:
-
Rafał Miłecki authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
AR9340 is a AR9003 family built-in 2x2 wmac of ar934x SOCs. It is single band in ar9341 SOC and dual band in ar9344/ar9342 SOCs. Signed-off-by:
Vasanthakumar Thiagarajan <vasanth@atheros.com> Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Use hw supported chains instead of hard coded values. Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Add a bool in ath9k_platform_data to pass AHB clock speed information. Driver needs this to configure PLL on some SOCs. Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
Vasanthakumar Thiagarajan authored
Signed-off-by:
-
John W. Linville authored
Merge branch 'wireless-next-2.6' of git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-2.6
-
-
- 22 Apr, 2011 2 commits
-
-
Johannes Berg authored
This variable is only ever checked right after the function that sets it, but the same function will also return the status, so we can pass it through instead of checking hw_ready later. Signed-off-by:
-
Johannes Berg authored
On new hardware, ucode images always come in pairs: code and data. Therefore, combine the variables into an appropriate struct and use that when both code and data are needed. Also, combine allocation and copying so that we have less code in total. Signed-off-by:
-
