An error occurred fetching the project authors.
- 06 Mar, 2012 7 commits
-
-
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 <johannes.berg@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Johannes Berg authored
There's no SKU override, we always just use it from EEPROM. As such, we can remove it from the config and use it in hw_param only. Since iwl_eeprom_check_sku() really needs to fill it in also rename that to iwl_eeprom_init_hw_params(). Signed-off-by:
-
Johannes Berg authored
There's no reason to set EXIT_PENDING when we start removing the module, as mac80211 will cleanly shut down the device in this case. Additionally, there's no point in rejecting commands to the device when we're cleaning up as that only leads to unwanted errors from mac80211 being printed, such as failed to remove key (...) from hardware (-16) 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:
-
Johannes Berg authored
The statistics are currently only half-heartedly locked against concurrent reading & modification so introduce a lock to really protect them. Signed-off-by:
-
Johannes Berg authored
Now that the transport has its own locking, there's no need to have the sta_lock in the shared data. Also, it can be a BH lock as it's not used from IRQ handlers. Signed-off-by:
-
Johannes Berg authored
There's only one place using this function, so move it where it's needed. Signed-off-by:
-
- 27 Feb, 2012 12 commits
-
-
Emmanuel Grumbach authored
No one needs it any more Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
This is temporary, but at least we can now throw the bus away and move the iwl_pci_{probe,remove} functions. Signed-off-by: -
Emmanuel Grumbach authored
Export it as "nic_error" notification, the error handling will be in the op_mode. Signed-off-by:
-
Emmanuel Grumbach authored
Export it as "hw_rf_kill" notification. Signed-off-by:
-
Emmanuel Grumbach authored
Export them as "queue_full" and "queue_not_full" notification. Signed-off-by:
-
Emmanuel Grumbach authored
This is the op_mode's Rx handler. Signed-off-by:
-
Emmanuel Grumbach authored
This handler allows the transport layer to free an skb from the op_mode. This can happen when the driver is stopped while Tx packets are pending in the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Define the op_mode as an interface with its ops. All the functions of the op_mode are "private", but its ops is made public in iwl-op-mode.h. The drv object starts the op_mode by using the start function in the public ops. Signed-off-by:
-
Emmanuel Grumbach authored
iwl_remove stops the wifi flows, so rename. Moreover, we can possibly stop the wifi flows even if the driver is statically compiled in the kernel, so remove the __devexit pragma. Signed-off-by:
-
Emmanuel Grumbach authored
Fetch the fw and spawn the op_mode. The op_mode that we need to fetch is determined from the fw file. Since the fw is fetched very early in the init flow, we can determine what op_mode to spawn. Signed-off-by:
-
Johannes Berg authored
The uCode flags modification is op_mode dependent since the P2P config is an op-mode config. This also fixes P2P enabling: due to the uCode loading code shuffle moving the SKU check before the EEPROM was read it was always false and would always disable PAN/P2P. Signed-off-by:
-
Emmanuel Grumbach authored
This will allow to have different behavior depending on the fw. Different fw APIs require completely different implementation of the mac80211 APIs. Each of these implementations is called an op_mode. The current op_mode is called DVM which states for dual virtual MAC. Signed-off-by:
-
- 17 Feb, 2012 7 commits
-
-
Don Fry authored
Remove the references to iwl_priv from the firmware request and parsing routines. They are generic to the nic. Signed-off-by:
Don Fry <donald.h.fry@intel.com> Signed-off-by:
-
Emmanuel Grumbach authored
Remove the return value. Signed-off-by:
-
Emmanuel Grumbach authored
iwl_down was just a wrapper around __iwl_down which was called from one place only. Replace it to direct call to iwl_down. Add lockdep warning in iwl_down to ensure it was called with the mutex held. Signed-off-by:
-
Don Fry authored
Change the prameters to the ucode (de)allocate routines to iwl_nic as they are not transport operations. Signed-off-by:
-
Don Fry authored
Move firmware_loading_complete from iwl_priv to iwl_nic and rename it to more accurately reflect what it does. Signed-off-by:
-
Don Fry authored
Delete ucode_ver from iwl_priv and use iwl_nic instead. Signed-off-by:
-
Johannes Berg authored
In order to separate the different parts of the driver better, we are reducing the shared data. This moves the workqueue to "priv", and removes it from the transport. To do this, simply use schedule_work() in the transport. Signed-off-by:
-
- 02 Feb, 2012 14 commits
-
-
Don Fry authored
The routines dealing with the ucode are spread through several files. Move them all to the same file and create a iwl-ucode.h file with the ucode file definitions. Signed-off-by:
-
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 authored
change a comment to be a little more clear Signed-off-by:
-
Emmanuel Grumbach authored
The HW revision is now read by the transport layer in its allocation. Signed-off-by:
-
Emmanuel Grumbach authored
This is another clean up of the proble flow. Signed-off-by:
-
Emmanuel Grumbach authored
This handler stops the HW and puts it in low power state. It will allow to clean up the flows in the upper layers. Signed-off-by:
-
Emmanuel Grumbach authored
This is transport related Signed-off-by:
-
Emmanuel Grumbach authored
Kill the trans_ops->prepare_card_hw which is now useless. Signed-off-by:
-
Emmanuel Grumbach authored
This handler will become thicker, reflect its real role now. Signed-off-by:
-
Emmanuel Grumbach authored
This is transport related Signed-off-by:
-
Emmanuel Grumbach authored
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:
-
Emmanuel Grumbach authored
Change the way we alloc the transport on the way. Since the transport is allocated from a bus specific area, we can give the bus specific parameters (i.e. pci_dev for PCI) to the transport. This will be useful when the bus layer will be killed. Signed-off-by:
-
Emmanuel Grumbach authored
Allocating the shrd area dynamically will allow more agility while revamping the flows. Signed-off-by:
-
