- 18 Apr, 2011 2 commits
-
-
Wey-Yi Guy authored
All _agn devices support continuous uCode trace, remove checking Signed-off-by:Wey-Yi Guy <wey-yi.w.guy@intel.com>
-
Wey-Yi Guy authored
After driver split, no need to call led functions through callback Signed-off-by:
-
- 08 Apr, 2011 5 commits
-
-
Johannes Berg authored
There's no need to keep both normal and BT statistics versions around all the time in memory when we only use a subset of both. So keep only the subsets that we need in memory, depending on the debug config). Also, in doing so, we can remove all the calls to iwl_bt_statistics() in the driver as we'll just access the copied statistics now. Finally, also remove this call from the one place where it might still be needed and automatically detect what kind of statistics the device is sending based on their size. This way, we don't need to keep track of which devices do what any more, which is good since this is subject to change based on the ucode version (as some ucode even for non-BT devices will in fact use BT statistics). Warn upon encountering a statistics command from the ucode that isn't known, so we will find such issues earlier in the future. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Tested-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
_agn driver should perform both sensitivity and chain noise calib. Signed-off-by: -
Wey-Yi Guy authored
After driver split, set_l0s config is no longer needed, remove it Signed-off-by: -
Wey-Yi Guy authored
After driver split, no need to use function pointer for those event and register dump function. Signed-off-by: -
root authored
define of firmware filenames use extra macro to build the files name. Signed-off-by:
Jay Sternberg <jay.e.sternberg@intel.com> Signed-off-by:
-
- 07 Apr, 2011 6 commits
-
-
Johannes Berg authored
The ISR (interrupt service routine) ops are now no longer necessary since they are the same for all devices this driver now handles. Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Johannes Berg authored
Again, a 4965 specific code path that we no longer need in iwlagn. Signed-off-by:
-
Wey-Yi Guy authored
Signed-off-by:
-
Johannes Berg authored
Only 4965 had a bootstrap microcode image, so the agn driver can completely ignore that and we can remove some code from it. Signed-off-by:
-
Johannes Berg authored
All agn devices behave the same, so there's no need to go through function pointers for any of the ucode loading functionality. Signed-off-by:
-
Johannes Berg authored
At least EEPROM version 0x11A has the wrong number of chains programmed into it for some reason, so we need to override in the driver. Signed-off-by:
-
- 25 Mar, 2011 1 commit
-
-
Johannes Berg authored
Since the driver split, there's no need for function pointers any more for aggregation queue setup and teardown as all devices now share the same code. Simplify this. Signed-off-by:
-
- 28 Feb, 2011 1 commit
-
-
Stanislaw Gruszka authored
Remove check_plcp_health and check_ack_health ops methods, they are unneeded after iwlegacy driver split. Merge check health code into to iwl-rx.c and make functions static. Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Acked-by:
-
- 21 Feb, 2011 1 commit
-
-
Fry, Donald H authored
New iwlwifi-5000 microcode requires driver support for API version 5. Signed-off-by:
-
- 13 Dec, 2010 2 commits
-
-
Wey-Yi Guy authored
Multiple devices use almost the same .cfg with minor differences. Use macro and remove the duplication. By doing this, reduce the chance for mistake while modify .cfg parameters Signed-off-by: -
Wey-Yi Guy authored
For WiFi/WiMAX combo devices, if WiMAX own the RF, WiFi driver try to access RF and fail. This is the W/A to To avoid WiFi keep reloading firmware and try to access RF again. Signed-off-by:
-
- 06 Dec, 2010 1 commit
-
-
Stanislaw Gruszka authored
This patch replace monitor/recover timer by watchdog based on time stamp. New code allow to discover hangs more precisely. Timeout values are currently doubled monitoring period values of previous timer. This have to be tuned based of firmware timing capabilities. Tested on 3945, 4965, 5300, 6300. Signed-off-by:
-
- 24 Nov, 2010 1 commit
-
-
Wey-Yi Guy authored
The valid tx/rx antenna information is part of EEPROM, so use it to configure the device. For few cases, the EEPROM did not reflect the correct antenna, but it is too late to modify the EEPROM, so overwrite with .cfg parameters Signed-off-by:
-
- 16 Nov, 2010 2 commits
-
-
Wey-Yi Guy authored
EEPROM contain the SKU information for the device, use it. Signed-off-by: -
Wey-Yi Guy authored
Set the default led mode for different devices. For the newer devices such as 6000g2a, 6000g2b and newer, the default led mode is On/Off instead of blinking. The led_mode still can be control through module parameter 0: system default 1: On/Off 2: blinking Signed-off-by:
-
- 15 Nov, 2010 3 commits
-
-
Wey-Yi Guy authored
There were two type of isr supported by iwlwifi devices. legacy isr - only used by legacy devices (3945 & 4965) ict isr - used by all new generation of iwlwifi devices Move all the isr related functions into ops, the ict type of isr supports only needed for newer devices. Signed-off-by:
-
Johannes Berg authored
In order to simplify the flow, and make new enhancements easier, separate out the RXON processing for modern AGN (5000 and newer) from RXON processing for the older 3945 and 4965 devices. Avoid changing these old ones to avoid regressions and move their code to a new file (iwl-legacy.c). 4965 gets the commit_rxon that used to be common for all AGN devices, but with removed PAN support. The new RXON processing is more central and does more work in committing, so that it is easier to follow. To make it more evident what is split out for legacy, split the necessary operations for that into a new struct iwl_legacy_ops. Those parts that still exist in the new AGN code don't need to be parametrized. Signed-off-by:
-
Johannes Berg authored
In the future, 4965 and modern AGN devices will need to have different mac80211 callbacks since they have different capabilities. Prepare for that by making the mac80211 operations a device config. Signed-off-by:
-
- 07 Oct, 2010 4 commits
-
-
Johannes Berg authored
Since all devices share the same operation here, there's no need to call it indirectly. Signed-off-by:
-
Johannes Berg authored
The set_pwr_src operation is only ever used from within the same sub-driver that it is declared in, so it can just be called directly instead of being an operation. Also, it is never called to set the power source to V_aux, so change the two functions accordingly (but keep the V_aux code for documentation purposes in a comment). Signed-off-by:
-
Johannes Berg authored
This operation is only ever called from set_hw_params, which is also already based on the config/ops, so that there's no need to have a separate set_ct_kill op and we can just call the right ct_threshold function. Signed-off-by:
-
Johannes Berg authored
All drivers share the same implementation, so there's no need to call this via a function pointer nor to export it. Signed-off-by:
-
- 06 Oct, 2010 1 commit
-
-
Wey-Yi Guy authored
move paramater definitions to a device paramater structure only leaving the device name, which antennas are used and what firmware file to use in the iwl_cfg structure. this will not completely remove the redundancies but greatly reduce them for devices that only vary by name or antennas. the parameters that are more likely to change within a given device family are left in iwl_cfg. also separate bt param structure added to help reduce more. Signed-off-by:
-
- 17 Sep, 2010 2 commits
-
-
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
Include bt_status_read function pointer for 5150 device Signed-off-by:
-
- 27 Aug, 2010 3 commits
-
-
Johannes Berg authored
iwlwifi occasionally needs to find the virtual interface pointer to give it to mac80211, but right now it only keeps one. Move it into the context so that we can keep one pointer each. Signed-off-by:
-
Johannes Berg authored
The broadcast station ID is per context, so add a variable for the ID in the context and use it everywhere we previously hardcoded it. Signed-off-by:
-
Johannes Berg authored
In order to support multiple interfaces, we must move a lot of data into per-context structures so we can use the contexts the device offers. To start with, this makes a lot of code context-aware, more changes will move more things into the context structure. Signed-off-by:
-
- 24 Aug, 2010 2 commits
-
-
Shanyu Zhao authored
A few cases in iwlwifi driver function ieee80211_frequency_to_channel() is called to get channel number from center frequency. This is not needed since the channel number is already saved in hw_value field of struct ieee80211_channel in function iwlcore_init_geos(). So replace those function calls with hw_value field of struct ieee80211_channel. Signed-off-by:
Shanyu Zhao <shanyu.zhao@intel.com> Signed-off-by:
-
Wey-Yi Guy authored
"Thermal Throttling" is an advance feature which only available for newer _agn devices. Move from iwl-core to iwl-agn for better code organization. Signed-off-by:
-
- 18 Aug, 2010 1 commit
-
-
Wey-Yi Guy authored
For 5000 series of devices, use long monitor timer to check stuck tx queues. This modification apply to all the 5000 series including 5300 and others. Cc: stable@kernel.org [2.6.35] Reported-by:
drago01 <drago01@gmail.com> Signed-off-by:
-
- 14 Aug, 2010 2 commits
-
-
Wey-Yi Guy authored
For 5000 and 6000g2b series of devices, use long monitor timer to check stuck tx queues. .6000g2b series device, it is WiFi/BT combo device, there are some cases, tx queues are not move for a period of time because the WiFi/BT coex. .5000 series device, it is being reported firmware got reload more often than necessary, so extend the timer to avoid un-necessary reload. Signed-off-by: -
Wey-Yi Guy authored
Change the name for monitor timer, also adding define for long monitor timer; long monitor timer can be used for the type of devices require longer time to determine the uCode is stuck on tx and needed reload. Signed-off-by:
-
