1. 19 11月, 2009 1 次提交
  2. 03 11月, 2009 1 次提交
  3. 28 10月, 2009 1 次提交
    • W
      iwlwifi: additional items in sensitivity range table · 55036d66
      Wey-Yi Guy 提交于
      Add more items to sensitivity range table to avoid using hardcoded values.
      Initialize the table per device since unique per device information is
      required to perform sensitivity calibration.
      
      additional items in sensitivity range table:
         .barker_corr_th_min: Barker correlation threshold minimum
         .barker_corr_th_min_mrc: Barker correlation threshold minimum for MRC
         .nrg_th_cca: Energy threshold for Clear Channel Assessment
      
      Barker codes are a technique used in WLAN encoding for transmission.
      MRC is "Maximal Ratio Combining", a technique for optimally combining the
      signals from 2 or more receivers to achieve a better signal.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      55036d66
  4. 08 10月, 2009 2 次提交
  5. 14 8月, 2009 1 次提交
    • J
      iwlwifi: automatically adjust sleep level · e312c24c
      Johannes Berg 提交于
      Depending on required latency requested by pm_qos (via mac80211)
      we can automatically adjust the sleep state. Also, mac80211 has
      a user-visible dynamic sleep feature where we are supposed to
      stay awake after sending/receiving frames to better receive
      response frames to our packets, this can be integrated into the
      sleep command.
      
      Currently, and this patch doesn't change that yet, we default
      to using sleep level 1 if PS is enabled. With a module parameter
      to iwlcore, automatic adjustment to changing network latency
      requirements can be enabled -- this isn't yet the default due
      to requiring more testing.
      
      The goal is to enable automatic adjustment and then go into the
      deepest possible sleep state possible depending on the networking
      latency requirements.
      
      This patch does, however, enable IEEE80211_HW_SUPPORTS_DYNAMIC_PS
      to avoid the double-timer (one in software and one in the device)
      when transmitting -- the exact timeout may be ignored but that is
      not of big concern.
      
      Note also that we keep the hard-coded power indices around for
      thermal throttling -- the specification of that calls for using
      the specified power levels. Those can also be selected in debugfs
      to allow easier testing of such parameters.
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      e312c24c
  6. 28 7月, 2009 1 次提交
    • J
      iwlwifi: fix up command sending · c2acea8e
      Johannes Berg 提交于
      The current command sending in iwlwifi is a bit of a mess:
       1) there is a struct, iwl_cmd, that contains both driver
          and device data in a single packed structure -- this
          is very confusing
       2) the on-stack data and the command metadata share a
          structure by embedding the latter in the former, which
          is also rather confusing because it leads to weird
          unions and similarly odd constructs
       3) each txq always has enough space for 256 commands,
          even if only 32 end up being used
      
      This patch fixes these things:
       1) rename iwl_cmd to iwl_device_cmd and keep track of
          command metadata and device command separately, in
          two arrays in each tx queue
       2) remove the 'meta' member from iwl_host_cmd and only
          put in the required members
       3) allocate the cmd/meta arrays separately instead of
          embedding them into the txq structure
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NReinette Chatre <reinette.chatre@intel.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      c2acea8e
  7. 11 7月, 2009 1 次提交
  8. 12 5月, 2009 1 次提交
  9. 10 2月, 2009 3 次提交
  10. 30 1月, 2009 2 次提交
  11. 20 12月, 2008 1 次提交
  12. 13 12月, 2008 1 次提交
  13. 01 11月, 2008 1 次提交
  14. 12 9月, 2008 1 次提交
  15. 09 9月, 2008 1 次提交
  16. 01 7月, 2008 1 次提交
  17. 15 6月, 2008 2 次提交
  18. 04 6月, 2008 1 次提交
  19. 22 5月, 2008 1 次提交
  20. 08 5月, 2008 3 次提交