1. 05 12月, 2012 1 次提交
    • 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
  2. 04 12月, 2012 1 次提交
  3. 28 11月, 2012 1 次提交
  4. 27 11月, 2012 1 次提交
  5. 27 9月, 2012 1 次提交
  6. 21 6月, 2012 1 次提交
  7. 08 6月, 2012 4 次提交
  8. 06 6月, 2012 1 次提交
  9. 05 6月, 2012 2 次提交
  10. 12 4月, 2012 7 次提交
  11. 10 4月, 2012 1 次提交
    • E
      wl12xx: adaptive sched scan dwell times · 6f407e5b
      Eyal Shapira 提交于
      Set the dwell times for sched scan according to the number
      of probe requests which are going to be transmitted.
      This should fix the too short dwell time problem which
      prevented some of the probe requests from being transmitted
      in cases of high number of SSIDs (10+) to be actively sched scanned.
      However, in the common case of having up to 1-2 SSIDs that
      require active scan, the dwell time would be kept to a minimum
      which should conserve power. This is important as sched scan
      also runs periodically while the host is suspended and there's
      great importance to keep power consumption as low as possible.
      Signed-off-by: NEyal Shapira <eyal@wizery.com>
      [fixed a couple of new strict checkpatch warnings]
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      6f407e5b
  12. 08 3月, 2012 1 次提交
  13. 15 2月, 2012 8 次提交
  14. 08 11月, 2011 1 次提交
  15. 07 10月, 2011 1 次提交
  16. 23 9月, 2011 1 次提交
  17. 14 9月, 2011 1 次提交
  18. 22 8月, 2011 4 次提交
  19. 06 7月, 2011 1 次提交
  20. 27 6月, 2011 1 次提交
    • I
      wl12xx: Support routing FW logs to the host · 95dac04f
      Ido Yariv 提交于
      A recently added feature to the firmware enables the driver to retrieve
      firmware logs via the host bus (SDIO or SPI).
      
      There are two modes of operation:
      1. On-demand: The FW collects its log in an internal ring buffer. This
         buffer can later be read, for example, upon recovery.
      2. Continuous: The FW pushes the FW logs as special packets in the RX
         path.
      
      Reading the internal ring buffer does not involve the FW. Thus, as long
      as the HW is not in ELP, it should be possible to read the logs, even if
      the FW crashes.
      
      A sysfs binary file named "fwlog" was added to support this feature,
      letting a monitor process read the FW messages. The log is transferred
      from the FW only when available, so the reading process might block.
      Signed-off-by: NIdo Yariv <ido@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      95dac04f