1. 24 3月, 2010 38 次提交
  2. 20 3月, 2010 2 次提交
    • W
      iwlwifi: code cleanup for connectivity recovery · fa8f130c
      Wey-Yi Guy 提交于
      Split the connectivity check and recovery routine into separated
      functions based on the types
         1. iwl_good_ack_health() - check for ack count
         2. iwl_good_plcp_health() - check for plcp error
      
      Based on the type of errors being detected, different recovery methods
      will be used to bring the system back to normal operational state.
      
      Because different NIC has different HW and uCode, the behavior is also
      different; these functions thus now form part of the ops infrastructure,
      so we can have more control on how to monitor and recover from error condition
      case per device.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      fa8f130c
    • W
      iwlwifi: Recover TX flow failure · d5a0ffa3
      Wey-Yi Guy 提交于
      Monitors the tx statistics to detect the drop in throughput.
      When the throughput drops, the ratio of the actual_ack_count and the
      expected_ack_count also drops.  At the same time, the aggregated
      ba_timeout (the number of ba timeout retries) also rises.  If the
      actual_ack_count/expected_ack_count ratio is 0 and the number of ba
      timeout retries rises to BA_TIMEOUT_MAX, no tx packets can be delivered.
      Reloading the uCode and bring the system back to normal operational
      state.
      Signed-off-by: NTrieu 'Andrew' Nguyen <trieux.t.nguyen@intel.com>
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      d5a0ffa3