An error occurred fetching the project authors.
- 27 May, 2013 1 commit
-
-
Johannes Berg authored
There are a number of parameters that aren't really hardware specific but rather define how the DVM firmware is used. Move these into the DVM configuration. Reviewed-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
Johannes Berg <johannes.berg@intel.com>
-
- 06 Mar, 2013 1 commit
-
-
Emmanuel Grumbach authored
Newer devices can work on different buses. This means that their configuration can be shared between different buses. Hence the configuration structures should exported to all the buses and not only to PCIE. Change this. Note that this requires all the fields to be the same amongst the buses. If differences will appear, we can always define a part that is bus dependent. Today, this is not needed. Signed-off-by:
-
- 24 Jan, 2013 1 commit
-
-
Johannes Berg authored
Update Copyright notices to 2013. Reviewed-by:
-
- 06 Dec, 2012 1 commit
-
-
Eytan Lifshitz authored
Since we will have several forms of NVM (EEPROM, OTP, etc.) and they will have different layouts, make the parsed data more generic. This allows functional code to be independent of a specific layout. Also change some variables and function names from having "eeprom" to "nvm" in their name. Signed-off-by:
Eytan Lifshitz <eytan.lifshitz@intel.com> Reviewed-by:
-
- 06 Jun, 2012 4 commits
-
-
Paul Bolle authored
Commit 7c5ba4a8 ("iwlwifi: move queue watchdog into transport") introduced the named constant 'IWL_WATCHHDOG_DISABLED'. Rename it to 'IWL_WATCHDOG_DISABLED'. Signed-off-by:
Paul Bolle <pebolle@tiscali.nl> Reviewed-by:
-
Johannes Berg authored
The EEPROM reading/parsing code is all mixed in the driver today, and the EEPROM is parsed only when we access data from it. This is problematic because the NVM needs to be parsed and that is independent of reading it. Also, the NVM format for new devices will be different and probably require a new parser. Therefore refactor the reading and parsing and create two independent components. Reading the EEPROM requires direct hardware accesses and therefore access to the transport, but parsing is independent and can be done on an NVM blob. Reviewed-by:
-
Johannes Berg authored
There's no need to dynamically fill the HT40 band bitmap as it's a device parameter, just put it into the HT configuration. Reviewed-by:
-
Johannes Berg authored
Structure the code a bit more and move all PCIe code including the hardware configuration files into a PCIe specific subdirectory. Reviewed-by:
-
- 24 Apr, 2012 1 commit
-
-
Meenakshi Venkataraman authored
Report correctly the latest released version of the iwlwifi firmware for all iwlwifi-supported devices. Cc: stable@vger.kernel.org #3.3+ Signed-off-by:
Meenakshi Venkataraman <meenakshi.venkataraman@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
- 23 Apr, 2012 2 commits
-
-
Johannes Berg authored
We can't get rid of everything yet due to the BT definitions that I'm not quite sure yet how to handle, but we can get rid of most unneeded includes. Signed-off-by:
-
Johannes Berg authored
The hardware files belong to the core PCI functionality, but the eeprom header file mixes higher-level functionality and the defines, so move out the specific defines and put them into the appropriate HW files instead. Signed-off-by:
-
- 12 Apr, 2012 5 commits
-
-
Johannes Berg authored
Having the pointer to lib_ops in the config makes it impossible to split the driver into different modules. Determine the ops based on the device family enumeration to get rid of the direct pointer. Also move all the opmode specific code from the iwl-[1256]000.c files into a new file iwl-agn-devices.c so that the former only have configuration data now. Signed-off-by:
-
Johannes Berg authored
This will later be used to dynamically bind the configuration data for DVM and MVM. For now, we can use it to get rid of the additional_nic_config() hook. Signed-off-by:
-
Johannes Berg authored
The whole code around eeprom is distributed across whole bunch of different files, most of which belong to the to-be-DVM code. As a result, it is currently very hard to split out the EEPROM code to be generic. However, it is also quite unlikely that the current EEPROM code will be needed by the MVM code as that has different mechanisms to query the EEPROM (it does so through the uCode.) So, at least temporarily, move everything into priv. If it becomes necessary to use the code from MVM, we will have to split it out, but then it's also easier since we'll know what pieces we need. Signed-off-by:
-
Johannes Berg authored
The hw_params are mostly values that are derived from the actual hardware config. As such, while it is possible that MVM will require similar ones, it makes more sense -- at least for now -- to put them into the DVM struct. Signed-off-by:
-
Johannes Berg authored
This removes one of the two sources of device restarts in the upper layer -- those are a bit inconvenient because normal restarts originate in the transport. By moving the watchdog down it can be treated the same. Also rewrite the watchdog logic. Timers are much more efficient when they never fire, so instead firing a timer every 500ms set up a timer for each TX queue and fire it only when the queue is really stuck. This avoids the CPU waking up when everything is working well. While at it, remove the wd_disable config item and replace it by simply setting wd_timeout to IWL_WATCHHDOG_DISABLED (0). Signed-off-by:
-
- 09 Apr, 2012 1 commit
-
-
Johannes Berg authored
The queue mapping is not only dynamic, it is also dependent on the uCode, as we can already see today with the dual-mode and non-dual-mode being different. Move the queue mapping out of the transport layer and let the higher layer manage it. Part of the transport configuration is how to set up the queues. Signed-off-by:
-
- 09 Mar, 2012 1 commit
-
-
Wey-Yi Guy authored
BIg portion of "iwlwifi: remove max_txq_num from hw_params" was missing during merge, here is the fix for it. Signed-off-by:
-
- 08 Mar, 2012 1 commit
-
-
Johannes Berg authored
The sensitivity parameters are never modified, so they should be const. Also remove the unused max_nrg_cck value to save some space. Signed-off-by:
-
- 07 Mar, 2012 4 commits
-
-
Johannes Berg authored
It's only needed in a few places. Signed-off-by:
-
Johannes Berg authored
The HW configuration settings base_params, ht_params and bt_params all should be const, make it so. Signed-off-by:
-
Johannes Berg authored
This is a hardware parameter, so it shouldn't be configurable by the user. Users can disable aggregation (which is the only thing affected) with 11n_disable. Signed-off-by:
-
Johannes Berg authored
Add wrappers to send commands from the DVM op-mode (which essentially consists of the current driver). This will allow us to move specific sanity checks there. Also, this removes iwl_trans_send_cmd_pdu() since that can now be taken care of in the DVM-specific wrapper. Signed-off-by:
-
- 06 Mar, 2012 3 commits
-
-
Johannes Berg authored
Writing to the global config structures is always wrong. To protect against such mistakes in the future, mark them const. Signed-off-by:
-
Johannes Berg authored
It's not really a good idea to write to the global static configuration. Use the valid TX/RX antenna information only from the HW params struct except in the case where the values from the config are used to override the values from the EEPROM. Signed-off-by:
-
Johannes Berg authored
Some data doesn't need protection, some of the lock places are simply useless, and some data can be protected with the mutex instead. Thus the shared lock can be removed by making those changes. Signed-off-by:
-
- 17 Feb, 2012 2 commits
-
-
Emmanuel Grumbach authored
This will allow to set the hw_params after we fetch the uCode. Signed-off-by:
-
Emmanuel Grumbach authored
Remove the return value. Signed-off-by:
-
- 02 Feb, 2012 2 commits
-
-
Don Fry authored
There is nothing device specific in the initialization of the bcast_sta_id so move it to the common inititalization routine. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
From now on, the transport layer in charge of providing access to the device. So change all the driver to give a pointer to the transport to all the low level functions that actually access the device. Signed-off-by:
-
- 24 Jan, 2012 1 commit
-
-
Wey-Yi Guy authored
Update Copyright to 2012 Signed-off-by:
-
- 06 Jan, 2012 1 commit
-
-
Wey-Yi Guy authored
Update Copyright to 2012 Signed-off-by:
-
- 16 Dec, 2011 1 commit
-
-
Don Fry authored
Move the configuration pointer from the upper level iwl_priv to the lower level iwl_shared structure, with associated code fixes. Signed-off-by:
-
- 08 Dec, 2011 1 commit
-
-
Don Fry authored
The eeprom image is a device level component, move from iwl_priv to iwl_shared, with associated code changes. Signed-off-by:
-
- 02 Dec, 2011 1 commit
-
-
Wey-Yi Guy authored
The current default watchdog timer is enabled, but we are seeing issues on legacy devices. So change the default setting of watchdog timer to per device based. But user still can use the "wd_disable" module parameter to overwrite the system setting Cc: stable@vger.kernel.org #3.0+ Signed-off-by:
-
- 28 Nov, 2011 1 commit
-
-
Johannes Berg authored
The init microcode knows very well which calibrations are required and sends us results for those that are. Consequently, we can just send all of those to the RT uCode again. The problem with having the driver know about this is that it is a uCode feature, not a hardware feature so the config is completely unsuitable. The only thing we need to check is whether the device needs crystal calibration or not, add a new parameter to the configuration for that. This makes new uCode work on 6000 series devices. Signed-off-by:
-
- 25 Nov, 2011 1 commit
-
-
Johannes Berg authored
The init microcode knows very well which calibrations are required and sends us results for those that are. Consequently, we can just send all of those to the RT uCode again. The problem with having the driver know about this is that it is a uCode feature, not a hardware feature so the config is completely unsuitable. The only thing we need to check is whether the device needs crystal calibration or not, add a new parameter to the configuration for that. This makes new uCode work on 6000 series devices. Signed-off-by:
-
- 14 Oct, 2011 3 commits
-
-
Emmanuel Grumbach authored
Move iwl_enable_rfkill_int to iwl-core.h, and remove the empty iwl-helpers.h Signed-off-by:
-
Johannes Berg authored
The inline function in this header is only used in a single file, so we can move it there. Signed-off-by:
-
Wey-Yi Guy authored
After driver split, no need to separate station management functions in two files, merge it Signed-off-by:
-
