- 29 Aug, 2011 40 commits
-
-
Emmanuel Grumbach authored
priv->mac80211_registered and priv->hw needed to move to shared. stop_queue API was added in order to allow the upper layer to stop the SW queues for regulatory purposes. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by:
John W. Linville <linville@tuxdriver.com>
-
Emmanuel Grumbach authored
This one is really transport related. ==== moves Stanislaw's code to BSD area ==== Signed-off-by:
-
Emmanuel Grumbach authored
This one is really transport related. Signed-off-by:
-
Emmanuel Grumbach authored
Remove a few dereferences of priv from the transport layer while at it. Signed-off-by:
-
Emmanuel Grumbach authored
Since all the check_empty logic is now in the transport layer, the upper layer doesn't need to know anything about tx queues. The disable aggregation flow was the last to know what a tx queue is, so move it too. Signed-off-by:
-
Emmanuel Grumbach authored
This logic is responsible to tell mac80211 when the HW queues are empty and the BA session can be started / torn down. Fix a bug on the way: When the the Tx BA session is stopped and the HW queues aren't empty, we stop the SW queue to drain the HW queue and then switch to the legacy HW queue. This is the IWL_EMPTYING_HW_QUEUE_DELBA state. While in this state, we never wake the SW queue, even when the HW queue is almost empty, since we need to drain it completely. Look at iwl_trans_pcie_reclaim regarding this. Once the HW queue is really empty, we must wake the SW queue in order to get traffic to the legacy queue. This step was missing leading to an odd situation were the traffic would just stall after we tore down a Tx BA session while the HW queue was not empty. Signed-off-by:
-
Emmanuel Grumbach authored
The queues and all the related logic suits to the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
This mapping is transport related. This allows us to remove the notion of tx queue from the tx path in the upper layer. iwl_wake_any_queue moved to transport layer since it needs to access these mappings. The TX API is nicer now: int (*tx)(struct iwl_trans *trans, struct sk_buff *skb, struct iwl_device_cmd *dev_cmd, u8 ctx, u8 sta_id); Signed-off-by:
-
Emmanuel Grumbach authored
In a near future, the upper layer won't be aware of the tx queues. This allows to remove one place where the upper layer needed to provide the tx queue index to the transport layer. This also saves around 1.5MB. Signed-off-by:
-
Emmanuel Grumbach authored
the mapping tx_queue -> fifo is really transport related. The upper layer should be involved in such things. Note that upon agg_disable, the queue is always mapped to fifo 0, but this doesn't matter since when the queue will be setup again for a new BA session, it will be configured to the good fifo anyway. Signed-off-by:
-
Emmanuel Grumbach authored
This removes the need for iwl_tx_info. Each tx queue holds an array of skbs, the transport layer doesn't need to know anything about the context in which a specific skb is sent. Signed-off-by:
-
Emmanuel Grumbach authored
When we remove the module, we free all the tx and rx resources. Before doing that, we'd better stop the tx / rx activity. Calling iwl_trans_stop_device in iwl_remove helps also to remove a few API functions: * rx_free: happens in iwl_trans_free * tx_free: happens in iwl_trans_free * disable_sync_irq: happens in iwl_trans_stop_device Signed-off-by:
-
Emmanuel Grumbach authored
There are still quite a few, but much less. A few fields have been moved /copied to hw_params which sits in the shared area: * priv->cfg->base_params->num_of_ampdu_queues * priv->cfg->base_params->shadow_reg_enable * priv->cfg->sku * priv->ucode_owner Signed-off-by:
-
Emmanuel Grumbach authored
The rate scaling and the transport need to access the data in iwl_tid_data, hence the move. Note that the only component in the upper layer that needs this data is the rate scaling. Refactoring the rate scaling may help to move iwl_tid_data from the shared area to the transport area. Signed-off-by:
-
Wey-Yi Guy authored
One more sku for 2000 series with different Subsystem ID Signed-off-by:
-
Emmanuel Grumbach authored
Move all the iwlXXX_abgn_cfg forward declaration to a separate file so that iwl-pci.c doesn't need to include iwl-agn.h that includes all iwl-dev.h This allows to provide real encapsulation. Dereferencing iwl_priv in the bus layer will now lead to a compilation error. Signed-off-by:
-
Daniel Halperin authored
CC [M] drivers/net/wireless/iwlwifi/iwl-pci.o drivers/net/wireless/iwlwifi/iwl-pci.c:506: warning: iwl_pci_suspend defined but not used drivers/net/wireless/iwlwifi/iwl-pci.c:519: warning: iwl_pci_resume defined but not used These are only used if CONFIG_PM_SLEEP is enabled. CONFIG_PM depends (CONFIG_PM_SLEEP || CONFIG_PM_RUNTIME), so it can be set without CONFIG_PM_SLEEP selected. Signed-off-by:
Daniel Halperin <dhalperi@cs.washington.edu> Signed-off-by:
-
Emmanuel Grumbach authored
Which means that iwl-io.c doesn't need to include iwl-dev.h any more. Signed-off-by:
-
Emmanuel Grumbach authored
a few h files weren't self contained. Fix that. Move iwl_dma_ptr to transport layer since it is not used by the upper layer any more. Signed-off-by:
-
Emmanuel Grumbach authored
It is relevant for PCIe only. Signed-off-by:
-
Emmanuel Grumbach authored
Since iwl-fh.h contains transport related data, it shouldn't be included by the upper layer. Only the transport layer and iwl-agn-ucode.c includes it. Signed-off-by:
-
Emmanuel Grumbach authored
Some of them weren't used at all, the others always had the same value since the driver split. Signed-off-by:
-
Emmanuel Grumbach authored
Continue to the clean up of the priv dereferencing from the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
These are transport layer related. Move also the corresponding debugfs handlers. Signed-off-by:
-
Emmanuel Grumbach authored
Since it is needed for host commands only, it is needed in transport layer only Signed-off-by:
-
Emmanuel Grumbach authored
Change a lot of functions to have them receive iwl_trans and not iwl_priv. Signed-off-by:
-
Emmanuel Grumbach authored
This helper is used by the transport and the upper layer. Kill __iwl_free_pages which was used in the transport only. Signed-off-by:
-
Emmanuel Grumbach authored
Logic move after all priv->status moved to struct iwl_shared Signed-off-by:
-
Emmanuel Grumbach authored
BUILD_BUG_ON(ARRAY_SIZE(iwlagn_ipan_queue_to_tx_fifo) != IWLAGN_FIRST_AMPDU_QUEUE); This check can be buggy. IWLAGN_FIRST_AMPDU_QUEUE has to be greater than the ARRAY_SIZE of iwlagn_ipan_queue_to_tx_fifo. Signed-off-by:
-
Emmanuel Grumbach authored
Needed for PCIe only Signed-off-by:
-
Emmanuel Grumbach authored
Now that the reclaim flow has been moved to the transport layer, a lot of functions can be made static or don't need to be exported outside the transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
The reclaim flow is really transport related. Define a simple API to allow the upper layer to request from the transport layer to reclaim packets until an index written in the Tx response / BA notification. The transport layer prepares a list of the packets that are being freed and passes this list to the upper layer. Between the two layers, the CB of the skb is used to pass a pointer to the context (BSS / PAN) in which the skb was sent. Signed-off-by:
-
Emmanuel Grumbach authored
It is accessed by the transport layer only, hence the move. The debugfs handlers that accessed it moved to the transport layer too. The rx_handlers part of it stayed in the upper layer and a special debugfs has been added for it Also add missing includes to iwl-commands.h. Signed-off-by:
-
Wey-Yi Guy authored
Add more comments to iwl_mod_params Signed-off-by:
-
Wey-Yi Guy authored
Add comments for better description Signed-off-by:
-
Wey-Yi Guy authored
Different subsystem ID Signed-off-by:
-
Wey-Yi Guy authored
Enable HT aggregation when it reach reasonable traffic without checking traffic load which delay enabling the aggregation and lower the throughput but this behavior can be overwrite by module parameter this address https://bugzilla.kernel.org/show_bug.cgi?id=40042Signed-off-by:
-
Emmanuel Grumbach authored
It is transport dependent, move to the PCIe transport layer. Signed-off-by:
-
Emmanuel Grumbach authored
Since the ISR is entirely in the transport layer, its data should be in the pcie specific region. Change sync_irq to first disable and then synchronize the IRQ. iwl_isr and iwl_isr_ict now receive iwl_trans. Signed-off-by:
-
Emmanuel Grumbach authored
These flows needs to access the APM and a few other registers that can differ between different transports. Signed-off-by:
-
