- 20 Jun, 2011 16 commits
-
-
Mike McCormack authored
These are a potential source of confusion, as most C code treats all non-zero values as true. Signed-off-by:
Mike McCormack <mikem@ring3k.org> Acked-by:
Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Mike McCormack authored
rtl_ps_set_rf_state's protect_or_not parameter is not set to true anywhere, except for commented out code. It enables some legacy locking code, which is no longer used, so delete the parameter and the old locking code. Signed-off-by:
-
Mike McCormack authored
offchan_deley should be offchan_delay Signed-off-by:
-
Rafał Miłecki authored
Function managing IRQs is needed for external drivers like b43. On the other side we do not expect writing any hosts drivers outside of bcma, so this is safe to do not export functions related to this. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
-
Pavel Roskin authored
Signed-off-by:
Pavel Roskin <proski@gnu.org> Signed-off-by:
-
John W. Linville authored
Nothing else is freeing it, and this mirrors the error handling path already in ath5k_init_softc. https://bugzilla.kernel.org/show_bug.cgi?id=37592Signed-off-by:
Tsyvarev Andrey <tsyvarev@ispras.ru>
-
Rafał Miłecki authored
Signed-off-by:
-
Rafał Miłecki authored
Signed-off-by:
-
Mohammed Shafi Shajakhan authored
checking the status of PAPRD_AGC2_POWER(Log(ADC_power) measured after last gain-change in dB) field suggests whether the PAPRD is completely/properly done. This is an additional check apart from polling for PAPRD done bit being set. Susinder suggests that the ideal power range value should be 0xf0 to 0xfe. With AR9382 we do have the values in this range. to have a common check for all platforms we take agc2_power should be atleast greater than 0xe0 Cc: susinder@qca.qualcomm.com Cc: senthilb@qca.qualcomm.com Cc: kmuthusa@qca.qualcomm.com Signed-off-by:Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com> Signed-off-by:
-
Mohammed Shafi Shajakhan authored
when the AP is configured with HT40/2.4GHz and when PAPRD is enabled in station we have PAPRD training frames never sent out because of the following failure "PAPRD target power delta out of range". This consistently happens in channel 10,11 in Over The Air testing and rarely in channel 6 under wired setup. the reason behind this issue is all the HT40 rates target power are 0 when we operate in channel 10/11 at 2.4GHz Signed-off-by:Mohammed Shafi Shajakhan <mshajakhan@atheros.com> Signed-off-by:
-
Eliad Peller authored
Cancel all relevant timers/works before suspending (wowlan). This patch handles the following warning: WARNING: at net/mac80211/util.c:565 queueing ieee80211 work while going to suspend Backtrace: [<bf07b598>] (ieee80211_can_queue_work+0x0/0x4c [mac80211]) [<bf07c28c>] (ieee80211_queue_work+0x0/0x30 [mac80211]) [<bf0690dc>] (ieee80211_sta_timer+0x0/0x3c [mac80211]) [<c00a3008>] (run_timer_softirq+0x0/0x220) [<c009e530>] (__do_softirq+0x0/0x130) [<c009e660>] (irq_exit+0x0/0xb4) [<c004c4a0>] (ipi_timer+0x0/0x4c) [<c0046350>] (do_local_timer+0x0/0x88) [<c00488ec>] (cpu_idle+0x0/0xe0) [<c05294e8>] (rest_init+0x0/0xe0) [<c0008958>] (start_kernel+0x0/0x314) Signed-off-by:
Eliad Peller <eliad@wizery.com> 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
-
Kalle Valo authored
core.h references ieee80211_ops but doesn't include mac80211.h, which issues a warning once mac80211-compat.h is taken into use. Acked-by:
Kalle Valo <kvalo@adurom.com> Signed-off-by:
-
Kalle Valo authored
zd_chip.h contains one function with a pointer to ieee80211_hw but doesn't include mac80211.h. As a temporary solution include mac80211.h to avoid a warning. Signed-off-by:
-
Kalle Valo authored
The hacks break once mac80211-compat.h is taken into use. Fix it by adding an ifdef check. Signed-off-by:
-
Kalle Valo authored
The hacks break once mac80211-compat.h is taken into use. Fix it by adding an ifdef check. Signed-off-by:
-
- 18 Jun, 2011 24 commits
-
-
Wey-Yi Guy authored
Remove unused and incorrect EEPROM define Signed-off-by:Wey-Yi Guy <wey-yi.w.guy@intel.com>
-
Wey-Yi Guy authored
Same operation needed by multiple devices, move to single function. Signed-off-by: -
Wey-Yi Guy authored
Code alignment, no functional changes. Signed-off-by: -
Wey-Yi Guy authored
Add offset define for subsystem id in EEPROM Signed-off-by: -
Wey-Yi Guy authored
Add power_level module parameter to set the default power save level. Power save level has range from 1 - 5, default power save level is 1. Signed-off-by: -
Wey-Yi Guy authored
Add power_save module parameter to enable power management if needed Default power management is disabled. Signed-off-by: -
Emmanuel Grumbach authored
Since the irq number is just an unsigned int, store it inside iwl_bus instead of calling the get_irq ops every time it is needed. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
Since there is no protection around SYNC host command mechanism, at least WARN when collision happens between two SYNC host comamnds. I am not sure there is a real issue (beyond the HCMD_ACTIVE flag maintenance) with having two SYNC host commands at the same time, but at least now, we will know about it. Signed-off-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Emmanuel Grumbach authored
All pci related stuff is in iwl-pci.c. Signed-off-by:
-
Emmanuel Grumbach authored
In order to remove a few more dereference to priv->pdev that will be killed [Asoon, there is now a method to get the IRQ number. Signed-off-by:
-
Emmanuel Grumbach authored
The PCI_REVISION_ID is read and printed in iwl_pci_probe anyway using pr_info Signed-off-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Wey-Yi Guy authored
Continue to popule the PCI layer and the iwl_bus_ops with the power related stuff. Signed-off-by:
-
Emmanuel Grumbach authored
Get a pointer to the struct device during probe and get the rid of all the PCI specific DMA wrappers. Signed-off-by:
-
Emmanuel Grumbach authored
Since we have now a PCI layer, all the init and deinit code that is PCI related should move to there. Also move the IO functions: read8/read32/write32. They need hw_base which is killed from priv. Signed-off-by:
-
Emmanuel Grumbach authored
Bus specific layer must know how to return the struct device* of the device. Implement that as a callback of iwl_bus_ops and use that callback instead of using the priv->pdev pointer which is meant to disappear soon. Since the struct device * is needed in hot path, iwl_bus holds a pointer to it instead of calling get_dev all the time. Signed-off-by:
-
Emmanuel Grumbach authored
iwl_bus will represent a bus, and iwl_bus_ops all the operations that can be done on this bus. For the moment only set_prv_data is implemented. More to come... Signed-off-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Emmanuel Grumbach authored
Move some PCI functionality to the new iwl_pci.[ch] files: * the PCI_DEVICE_TABLE * the pci_driver struct definition * the PCI probe / remove functions * the PCI suspend / resume functions All these functions are now split: the trigger comes from the PCI layer which calls to the bus generic code located in the other files. This is the beginning only. There are still a lot of PCI related code needs to be gathered. Signed-off-by:
-
Emmanuel Grumbach authored
It is superfluous to disable the interrupts after we reset the NIC. The only entity that could enable the interrupts after the NIC is reset is the driver. So remove this pointless action. Signed-off-by:
-
Wey-Yi Guy authored
Flush command can target specified interface or all interfaces Signed-off-by: -
Wey-Yi Guy authored
When issue tx flush, also consider PAN Signed-off-by:
-
