1. 01 10月, 2013 1 次提交
  2. 27 9月, 2013 1 次提交
  3. 23 8月, 2013 1 次提交
    • J
      mac80211: move setting WIPHY_FLAG_SUPPORTS_SCHED_SCAN into drivers · 1fb90260
      Johannes Berg 提交于
      mac80211 currently sets WIPHY_FLAG_SUPPORTS_SCHED_SCAN based on whether
      the start_sched_scan operation is supported or not, but that will not
      be correct for all drivers, we're adding scheduled scan to the iwlmvm
      driver but it depends on firmware support.
      
      Therefore, move setting WIPHY_FLAG_SUPPORTS_SCHED_SCAN into the drivers
      so that they can control it regardless of implementing the operation.
      
      This currently only affects the TI drivers since they're the only ones
      implementing scheduled scan (in a mac80211 driver.)
      Acked-by: NLuciano Coelho <luca@coelho.fi>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      1fb90260
  4. 16 7月, 2013 1 次提交
  5. 17 6月, 2013 6 次提交
  6. 04 6月, 2013 1 次提交
  7. 26 3月, 2013 1 次提交
  8. 25 3月, 2013 9 次提交
  9. 19 3月, 2013 1 次提交
  10. 06 3月, 2013 1 次提交
  11. 12 2月, 2013 1 次提交
  12. 08 2月, 2013 3 次提交
  13. 19 1月, 2013 1 次提交
  14. 14 1月, 2013 1 次提交
  15. 03 1月, 2013 1 次提交
    • J
      mac80211: split TX aggregation stop action · 18b559d5
      Johannes Berg 提交于
      When TX aggregation is stopped, there are a few
      different cases:
       - connection with the peer was dropped
       - session stop was requested locally
       - session stop was requested by the peer
       - connection was dropped while a session is stopping
      
      The behaviour in these cases should be different, if
      the connection is dropped then the driver should drop
      all frames, otherwise the frames may continue to be
      transmitted, aggregated in the case of a locally
      requested session stop or unaggregated in the case of
      the peer requesting session stop.
      
      Split these different cases so that the driver can
      act accordingly; however, treat local and remote stop
      the same way and ask the driver to not send frames as
      aggregated packets any more.
      
      In the case of connection drop, the stop callback the
      driver is otherwise supposed to call is no longer
      required.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      18b559d5
  16. 11 12月, 2012 7 次提交
  17. 07 12月, 2012 1 次提交
  18. 05 12月, 2012 2 次提交
    • A
      wlcore: improved Tx scheduling algorithm · 0e810479
      Arik Nemtsov 提交于
      Prioritize EDCA by choosing the AC before anything else. Use the
      fast/slow link bitmap in FW to improve the scheduling algorithm for
      the multi-link scenario.
      
      Set packet thresholds to determine if a given link is high or low
      priority according to its speed. A slow link will be given high priority
      if the amount of packets queued for it in the FW is lower than the
      slow-threshold. Similarly, a fast link will be given high priority if
      the number of its packets queued in FW is smaller than the high-threshold.
      
      The improved algorithm:
      1. Choose optimal AC according to FW utilization
      2. Traversing the VIFs in a round-robin fashion, try to choose a high
         priority link. Links are traversed in a round-robin fashion inside a
         VIF.
      3. If no high priority links are found, choose the first non-empty
         (low priority) link found in the round robin.
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      0e810479
    • A
      wlcore: track FW-allocated packets per link · 9ebcb232
      Arik Nemtsov 提交于
      Move FW-allocation tracking code to the fw_status function and track
      allocations made by all links. These will be incorporated in the
      improved Tx scheduling algorithm.
      
      Manually zero the system link counters on op_stop, as this link is not
      allocated the normal way.
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      9ebcb232