1. 22 8月, 2011 2 次提交
  2. 06 7月, 2011 1 次提交
  3. 27 6月, 2011 2 次提交
  4. 08 6月, 2011 1 次提交
  5. 13 5月, 2011 3 次提交
  6. 02 5月, 2011 1 次提交
  7. 29 4月, 2011 1 次提交
    • A
      wl12xx: support FW TX inactivity triggers · 47684808
      Arik Nemtsov 提交于
      In AP mode we register for the MAX_TX_RETRY and INACTIVE_STA events.
      Both are reported to the upper layers as a TX failure in the offending
      stations.
      
      In STA mode we register only for the MAX_TX_RETRY event. A TX failure is
      interpreted as a loss of connection.
      
      Support for IEEE80211_HW_REPORTS_TX_ACK_STATUS has been removed to avoid
      the inherent race condition of a mac80211 TX failure counter in addition
      to the FW counter.
      
      This patch depends on "mac80211: allow low level driver to report packet
      loss"
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      47684808
  8. 19 4月, 2011 2 次提交
    • E
      wl12xx: rearrange some ELP wake_up/sleep calls · c1b193eb
      Eliad Peller 提交于
      ELP (Extremely/Enhanced Low Power, or something like that ;)) refers to
      the powerstate of the 12xx chip, in which very low power is consumed,
      and no commands (from the host) can be issued until the chip is woken up.
      
      Wakeup/sleep commands must be protected by a wl->mutex, so it's generally
      a good idea to call wakeup/sleep along with the mutex lock/unlock (where
      needed). However, in some places the wl12xx driver calls wakeup/sleep in
      some "inner" functions. This result in some "nested" wakeup/sleep calls
      which might end up letting the chip go to sleep prematurely (e.g. during
      event handling).
      
      Fix it by rearranging the elp calls to come along with mutex_lock/unlock.
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NIdo Yariv <ido@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      c1b193eb
    • S
      wl12xx: 1281/1283 support - Add dummy packet support · ae47c45f
      Shahar Levi 提交于
      Support sending dummy packet to wl128x FW as results of
      dummy packet event. That is part of dynamic TX mem blocks mechanism.
      
      Only send dummy packet when not in AP mode.
      
      [Even though the DUMMY_PACKET_EVENT_ID and the
      STA_REMOVE_COMPLETE_EVENT_ID events are defined to the same value, we
      need to treat them separately in the code.  Keep the check and enable
      STA_REMOVE_COMPLETE_EVENT_ID for AP mode and DUMMY_PACKET_EVENT_ID for
      STA.  Moved one warning to a cleaner place.  Use WL1271_TID_MGMT for
      dummy packets -- Luca]
      Signed-off-by: NShahar Levi <shahar_levi@ti.com>
      Reviewed-by: NLuciano Coelho <coelho@ti.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      ae47c45f
  9. 09 2月, 2011 1 次提交
  10. 25 1月, 2011 1 次提交
  11. 22 11月, 2010 1 次提交
  12. 16 11月, 2010 1 次提交
  13. 28 9月, 2010 3 次提交
  14. 09 7月, 2010 5 次提交
  15. 03 6月, 2010 1 次提交
  16. 10 4月, 2010 1 次提交
  17. 07 4月, 2010 1 次提交
  18. 01 4月, 2010 3 次提交
  19. 24 3月, 2010 1 次提交
  20. 10 3月, 2010 1 次提交
  21. 20 2月, 2010 3 次提交
  22. 29 12月, 2009 4 次提交