- 24 Jun, 2011 2 commits
-
-
Johannes Berg authored
When we stop the device while a command is in flight that uses multiple TBs, we can leak the DMA buffers for the second and higher TBs. Fix this by using iwlagn_unmap_tfd() as we do when we normally recover the entry. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com>
-
Johannes Berg authored
Simplify the code and use SIMPLE_DEV_PM_OPS to define iwl_dev_pm_ops instead of doing the same thing manually. Signed-off-by:
-
- 22 Jun, 2011 38 commits
-
-
Hauke Mehrtens authored
Two functions in ssb are using register_pci_controller() which is __devinit. The functions ssb_pcicore_init_hostmode() and ssb_gige_probe() should also be __devinit. This fixes the following warning: WARNING: vmlinux.o(.text+0x2727b8): Section mismatch in reference from the function ssb_pcicore_init_hostmode() to the function .devinit.text:register_pci_controller() The function ssb_pcicore_init_hostmode() references the function __devinit register_pci_controller(). This is often because ssb_pcicore_init_hostmode lacks a __devinit annotation or the annotation of register_pci_controller is wrong. WARNING: vmlinux.o(.text+0x273398): Section mismatch in reference from the function ssb_gige_probe() to the function .devinit.text:register_pci_controller() The function ssb_gige_probe() references the function __devinit register_pci_controller(). This is often because ssb_gige_probe lacks a __devinit annotation or the annotation of register_pci_controller is wrong. Reported-by:
Ralf Baechle <ralf@linux-mips.org> Signed-off-by:
Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Gabor Juhos authored
Signed-off-by:
Gabor Juhos <juhosg@openwrt.org> Signed-off-by:
-
Gabor Juhos authored
The patch adds a callback to ath9k_platform_data. If the callback is provided by the platform code, then it can be used to hard reset the WMAC device. The callback is required for doing a hard reset of the AR9330 chips to get them working again after a hang. Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
The patch adds the missing configuration code for diversity group 1. Signed-off-by:
-
Gabor Juhos authored
Also remove two empty lines. Signed-off-by:
-
Gabor Juhos authored
The current values must be used only on AR9485 chips. Other chips requires different values. Signed-off-by:
-
Gabor Juhos authored
The 'ar9003_hw_antdiv_comb_conf_get' function sets div_group to 2 however that value is not used in 'ath_ant_div_comb_alt_check'. Signed-off-by:
-
Gabor Juhos authored
The AR9330 is a single stream chip. Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
A multiplication is missing from the current formula. Cc: Vasanthakumar Thiagarajan <vasanth@atheros.com> Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
The AR9330 1.0 and 1.1 are using the same revision, thus it is not possible to distinguish the two chips. The platform setup code can distinguish the chips based on the SoC revision. Add a callback function to ath9k_platform_data in order to allow getting the revision number from the platform code. Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Gabor Juhos authored
Signed-off-by:
-
Mohammed Shafi Shajakhan authored
higher the chainmask, lesser the power_delta to be added to the paprd_training_power Signed-off-by:
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> Signed-off-by:
-
Johannes Berg authored
Use the new consistent dump feature from (generic) netlink to advertise when dumps are incomplete. Readers may note that this does not initialize the rdev->bss_generation counter to a non-zero value. This is still OK since the value is modified only under spinlock when the list is modified. Since the dump code holds the spinlock, the value will either be > 0 already, or the list will still be empty in which case a consistent dump will actually be made (and be empty). Signed-off-by:
-
Amitkumar Karwar authored
In some cases local pointers are used to cast void pointers passed to the function. Those unnecessary local pointers are also removed. This patch was inspired by Joe Perches' patch [PATCH net-next 1/2] wireless: Remove casts of void *; and the comments from Julian Calaby. Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Cc: Joe Perches <joe@perches.com> Cc: Julian Calaby <julian.calaby@gmail.com> Signed-off-by:
Bing Zhao <bzhao@marvell.com> Signed-off-by:
-
Jussi Kivilinna authored
As USB_INT_ID_RETRY_FAILED can override USB_INT_ID_REGS, beacon interrupt (CR_INTERRUPT) might be lost. Problem is that when device trigger CR_INTERRUPT it disables HW interrupt. Now if USB_INT_ID_REGS with CR_INTERRUPT gets lost, beacon interrupt stays disabled until beacon watchdog notices the stall. This happen very often on heavy TX. Improve watchdog to trigger earlier, after three missing beacon interrupts. Signed-off-by:
Jussi Kivilinna <jussi.kivilinna@mbnet.fi> Signed-off-by:
-
Jussi Kivilinna authored
zd_mac_config_beacon() has only limited time to set up beacon when called from beacon interrupt handler/worker. So do not let it retry acquiring beacon fifo semaphore in interrupt handler. Beacon fifo semaphore should not be locked by firmware anyway at this time, it's only locked when device is using/txing beacon. Signed-off-by:
-
