- Sep 21, 2010
-
-
Felix Fietkau authored
The tid aggregation cleanup is a bit fragile, as it discards failed subframes in some places, and retransmits them in others. This could block the cleanup of an existing aggregation session, if a retransmission for a tid is issued, yet the tid is never scheduled again because of the cleanup state. Fix this by getting rid of as many subframes as possible, as early as possible, and immediately transmitting pending subframes as regular HT frames instead of waiting for the cleanup to complete. Drop all pending subframes while keeping track of the Block ACK window during aggregate tx completion to prevent sending out stale subframes, which could confuse the receiver side. Signed-off-by:
Felix Fietkau <nbd@openwrt.org> Cc: stable@kernel.org Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Felix Fietkau authored
A new aggregation session start can be issued by mac80211, even when the cleanup of the previous session has not completed yet. Since the data structure for the session is not recreated, this could corrupt the block ack window and lock up the aggregation session. Fix this by delaying the new session until the old one has been cleaned up. Signed-off-by:
-
Felix Fietkau authored
There's no reason to keep pointers to pending tx buffers around, if they're only used to keep track of which frames are still pending. Use a bitfield instead. Signed-off-by:
-
Eliad Peller authored
typo - while looking for specific bits we should do a bitwise-AND instead of logical-AND. Signed-off-by:
Eliad Peller <eliad@wizery.com> Acked-by:
Luciano Coelho <luciano.coelho@nokia.com> Signed-off-by:
-
Eliad Peller authored
copy the rx_status directly to skb->cb (control buffer) instead of copying it to a local struct and then copying it again (for each rx packet) Signed-off-by:
-
Christian Lamparter authored
This is a obvious bug, skb_queue_walk does not work if the iterator gets removed from the queue. Signed-off-by:
Christian Lamparter <chunkeey@googlemail.com> Signed-off-by:
-
Christian Lamparter authored
The driver has a set of different initvals for 20 MHz vs dynamic HT2040 operation. Because we can't change some of the registers "in-flight", the driver needs to perform a warm reset. Signed-off-by:
-
Christian Lamparter authored
Don't mark the device as completely dead just yet. If all goes to plan and carl9170_reboot succeeds then we can skip the expensive userspace-driven reinitialization anyway. And if it doesn't and carl9170_reboot fails, then carl9170_usb_cancel_urbs will do the necessary steps. Signed-off-by:
-
Christian Lamparter authored
This patch prevents the tasklet code from interfering while the firmware is down for an unscheduled maintenance. Signed-off-by:
-
Christian Lamparter authored
According to Atheros, chain 1 is not connected. Signed-off-by:
-
Christian Lamparter authored
Ever since carl9170 gained support to read the noisefloor, the reported noisefloor level was pretty poor. Initially I assumed that something was wrong in the PHY setup and it would be impossible to fix without any guidances. But this was not the case. In fact the nf readings were correct and the thing that was broken was the "simple" sign extension code! Signed-off-by:
-
Christian Lamparter authored
The eeprom provides a mask for all present rx chains. Why not use it instead of the generic initval default? Signed-off-by:
-
Bruno Randolf authored
Add the mac80211 callback function to configure the tx queue properties like cw_min, cw_max and aifs. Signed-off-by:
Bruno Randolf <br1@einfach.org> Signed-off-by:
-
Bruno Randolf authored
Get rid of overly complicated cw_min/max and AIFS configuration: * Validate values in ath5k_hw_set_tx_queueprops(), so we can use them directly without further checks or computation in ath5k_hw_reset_tx_queue(). * Simplifiy by using AR5K_TUNE_AIFS|CWMIN|CWMAX variables directly since we don't support XR or B channels. That way we can also remove AR5K_TXQ_USEDEFAULT and the confusing logic around it. * Update data types: AIFS is u8, CW's are u16. * Remove now unneeded variables in ath5k_hw. Signed-off-by:
-
Bruno Randolf authored
If we return a TX descriptor to the pool of available descriptors, while a queues TXDP still points to it we could potentially run into all sorts of troube. It has been suggested that there is hardware which can set the descriptors done bit before it reads ds_link and moves on to the next descriptor. While the documentation says this is not true for newer chipsets (the descriptor contents are copied to some internal memory), we don't know about older hardware. To be safe, we always keep the last descriptor in the queue, and avoid dangling TXDP pointers. Unfortunately this does not fully resolve the problem - queues still get stuck! This is similar to what ath9k does. Signed-off-by:
-
Bruno Randolf authored
Add a counter to show how many times a queue got stuck in the debugfs queue file. Signed-off-by:
-
Bruno Randolf authored
Since we do not know any better solution to the problem that TX queues can get stuck, this adds a timer-based watchdog, which will check for stuck queues and reset the hardware if necessary. Ported from ath9k commit 164ace38 . Signed-off-by:
-
Bruno Randolf authored
Clearer separation between queue handling and what we do with completed frames. Signed-off-by:
-
Bruno Randolf authored
It does not make sense to stop queues for NF calibration. This will not stop transmissions from the card, if there are queued packets. If we run out of TX buffers we need to stop all queues, not only one. Signed-off-by:
-
Bruno Randolf authored
Take txq lock in debug file and fix reporting of used buffers. Signed-off-by:
-
Bruno Randolf authored
Prepare ath5k for WME by using four hardware queues. The way we set up our queues matches the mac80211 queue priority 1:1, so we don't have to do any mapping for queue numbers. Every queue uses 50 of the total 200 available transmit buffers, so the DMA memory usage does not increase with this patch, but it might be good to fine-tune the number of buffers per queue later (depending on the CPU speed and load, and the speed of the medium access, it might not be big enough). Signed-off-by:
-
Bob Copeland authored
This change reorganizes the main ath5k file in order to re-group related functions and remove most of the forward declarations (from 61 down to 3). This is, unfortunately, a lot of churn, but there should be no functional changes. Signed-off-by:
Bob Copeland <me@bobcopeland.com> Signed-off-by:
-
Bruno Randolf authored
Fixing up a merge issue / concurrent development: Remove unneeded ath_crypt_caps flags, as per "ath9k_hw: remove useless hw capability flags" (364734fa ), but set the AESCCM flag for ath9k. common ath code still needs a flag for this because there is ath5k hardware which can't do AES in hardware. Signed-off-by:
-
Christian Lamparter authored
This patch is loosely based on an ath9k patch called: "ath9k_hw: sync initvals for ar9001 and ar9002 with Atheros" It includes the following changes/fixes: - AGC setting improvements - timing changes for improved performance Signed-off-by:
-
Ohad Ben-Cohen authored
Add MMC3 support on ZOOM, which has the wl1271 device hardwired to. The wl1271 is a 4-wire, 1.8V, embedded SDIO WLAN device with an external IRQ line, and power-controlled by a GPIO-based fixed regulator. Signed-off-by:
Ohad Ben-Cohen <ohad@wizery.com> Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Ohad Ben-Cohen authored
Add a fixed regulator vmmc device to enable power control of the wl1271 wlan device. Signed-off-by:
-
Ohad Ben-Cohen authored
The wl1271 device is using a reference clock that may change between board to board. Make the ref_clock parameter configurable by board settings instead of having a hard coded value in the sources. Signed-off-by:
-
Ohad Ben-Cohen authored
Remove the hard coded irq information, and instead take the irq information from the board's platform data. Signed-off-by:
-
Ohad Ben-Cohen authored
Add a simple mechanism to pass platform data to the SDIO instances of wl12xx. This way there is no confusion over who owns the 'embedded data', typechecking is preserved, and no possibility for the wrong driver to pick up the data. Originally proposed by Russell King. Signed-off-by:
-
Ohad Ben-Cohen authored
Make it possible for the set power method to indicate a success/failure return value. This is needed to support more complex power on/off operations such as SDIO power manipulations. Signed-off-by:
-
Ohad Ben-Cohen authored
Move wl12xx.h outside of the spi-specific location, so it can be shared with both spi and sdio solutions. Update all users of spi/wl12xx.h accordingly Signed-off-by:
-
- Sep 18, 2010
-
-
Wey-Yi Guy authored
For config bt command, initialize both tx_prio_boost and rx_prio_boost to "0". Signed-off-by:Wey-Yi Guy <wey-yi.w.guy@intel.com>
-
Wey-Yi Guy authored
Adding two new parameters in config bt API. these two parameters use the 3 reserved bytes, so there is no structure size changes. Make sure set both parameters to "zero" in order to preserve previous behavior. Signed-off-by: -
Wey-Yi Guy authored
For failure tx status 0x90 and 0x91, give the correct name to reflect the errors. Signed-off-by: -
Jay Sternberg authored
remove duplicate header and clean up format so it is defined once making changes consolicated ensuring consistancy of output. no function change to date displayed. Signed-off-by:
Jay Sternberg <jay.e.sternberg@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
Addition to standard tx frame failure report, adding aggregated frame failure report to debugfs Signed-off-by: -
Wey-Yi Guy authored
When uCode completed the aggregated frames transmission attempt, it will send tx command response with aggregated frame status. Keep track of the failure counter which help indicate any transmission error condition. Signed-off-by: -
Wey-Yi Guy authored
For aggregated frames with block ack, different status flag will be used as part of tx command response. Signed-off-by: -
Wey-Yi Guy authored
Tx command response sent to host by uCode after completed the transmission attempt. The status parameter indicates whether the transmission was successful, or else why if failed. Here we keep the counters to help understand the different failure cases. Signed-off-by: -
Wey-Yi Guy authored
If uCode fail to transmit frame, it will send reply tx back to driver with failure status; keep the counters of each failure cases for debugging. Signed-off-by:
-
