1. 23 7月, 2010 2 次提交
  2. 03 7月, 2010 3 次提交
    • W
      iwlwifi: add support for device tx flush request · 65550636
      Wey-Yi Guy 提交于
      "Flush" request can come from two different sources, it can either from
      mac80211, or from device when the operation is needed. Here
      adding the support for device issue "flush" request.
      
      When receive tx complete with status is TX_STATUS_FAIL_RFKILL_FLUSH,
      issue REPLY_TXFIFO_FLUSH command to uCode to flush out all the tx frames
      in queues.
      
      In this condition, since mac80211 has no knowledge of "flush" operation,
      driver need to stop all the tx queues and wait for the operation
      completed before wake up the queues for frames transmission.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      65550636
    • W
      iwlwifi: add mac80211 flush callback support · 716c74b0
      Wey-Yi Guy 提交于
      Adding flush callback support in the driver. Two type of flush can be
      issued by mac80211:
      1. drop = true: frame drop is ok, issue REPLY_TXFIFO_FLUSH host command
      to uCode to drop all the frames in tx fifo queues; then return the
      control back to mac80211
      2. drop = false: wait for either all the frames in tx fifo queues been
      transmitted, or timeout; then return the control back to mac80211
      
      If the flush request coming from mac80211, mac80211 will make sure there
      are no additional frames push down to driver before flush operation is
      completed.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      716c74b0
    • W
      iwlwifi: fix fw_restart module parameter · c04f9f22
      Wey-Yi Guy 提交于
      fw_restart module parameter was broken by the recent check for stuck
      queue patch, driver check the fx_restart module parameter
      before reload the firmware; but the stuck queue timer kick in after
      firmware error and reload the firmware even fw_restart=0. In this case,
      driver should not reload the firmware, it is important to help debugging
      uCode error.
      
      The only case we can ignore the module parameter is when user request
      firmware reload from debugfs, which can bypass the checking and perform
      firmware reload all the time.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      c04f9f22
  3. 26 6月, 2010 2 次提交
  4. 22 6月, 2010 2 次提交
  5. 06 6月, 2010 5 次提交
  6. 14 5月, 2010 2 次提交
  7. 11 5月, 2010 12 次提交
  8. 28 4月, 2010 1 次提交
  9. 17 4月, 2010 6 次提交
  10. 10 4月, 2010 1 次提交
  11. 03 4月, 2010 1 次提交
  12. 01 4月, 2010 1 次提交
    • S
      iwlwifi: manage QoS by mac stack · e61146e3
      Stanislaw Gruszka 提交于
      We activate/deactivate QoS and setup default queue parameters in iwlwifi
      driver. Mac stack do the same, so we do not need repeat that work here.
      Stack also will tell when disable QoS, this will fix driver when working
      with older APs, that do not have QoS implemented.
      
      Patch make "force = true" in iwl_active_qos() assuming we always want
      to do with QoS what mac stack wish.
      
      Patch also remove unused qos_cap bits, do not initialize qos_active = 0,
      as we have it initialized to zero by kzalloc.
      Signed-off-by: NStanislaw Gruszka <sgruszka@redhat.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e61146e3
  13. 26 3月, 2010 2 次提交