1. 25 3月, 2015 1 次提交
  2. 09 1月, 2015 2 次提交
  3. 20 10月, 2014 1 次提交
  4. 16 7月, 2014 1 次提交
  5. 14 2月, 2014 5 次提交
  6. 23 10月, 2013 3 次提交
  7. 27 9月, 2013 1 次提交
  8. 25 3月, 2013 1 次提交
  9. 08 2月, 2013 1 次提交
    • L
      wlcore: remove if_ops from platform_data · afb43e6d
      Luciano Coelho 提交于
      We can't pass pointers from the platform data to the modules, because
      with DT it cannot be done.  Those pointers are not set by the board
      files anyway.  It's the bus modules that set them, so they can be
      safely removed from the platform data without changing any board
      files.
      
      Create a new structure that the bus modules pass to wlcore.  This
      structure contains the if_ops pointers and a pointer to the actual
      platform data.
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      Reviewed-by: NFelipe Balbi <balbi@ti.com>
      afb43e6d
  10. 11 12月, 2012 4 次提交
    • I
      wlcore: Always pass DMA-able buffers to mmc functions · 2e07d028
      Ido Yariv 提交于
      Some of the mmc drivers initiate DMA transfers with buffers passed from
      higher layers. This means that the driver shouldn't ever pass non
      DMA-able buffers, such as ones that are unaligned, allocated on the
      stack or static.
      
      Fix a couple of calls to the mmc layer in which buffers which weren't
      necessarily DMA-able were passed.
      
      [Use sizeof(*wl->buffer_32) instead of sizeof(u32) -- Luca]
      Signed-off-by: NIdo Yariv <ido@wizery.com>
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      2e07d028
    • A
      wlcore/wl18xx: change priority calculations for links · f1626fd8
      Arik Nemtsov 提交于
      Update the 18xx FW status private part to include Tx related link
      priorities. Introduce new HW ops to determine link priority per chip
      family.
      
      For 18xx the changes are:
      - Suspended links are at most low priority and Tx for them is stopped
        beyond the suspend threshold.
      - Active links now get their thresholds directly from FW
      - There's a new "stop" threshold for active links, at which point a link
        stops receiving new packets.
      
      Update the min 18xx FW version required to make sure suspended links
      bitmap is advertised by the FW.
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      f1626fd8
    • E
      wlcore: increase scan dwell times if no activity · 5d3a1603
      Eyal Shapira 提交于
      There's a limit on scan dwell times of max 30ms in order
      to avoid degrading voip traffic which could be going on
      while scanning. However these dwell times increase the
      chance of missing out on nearby APs leading to partial
      scan results. Allow configuration of longer dwell times
      in case there no active interface (i.e. no STA associated
      or AP up).
      
      [Arik - count started vifs using an in-driver function]
      
      [Fixed some new checkpatch warnings regarding comments in the
      networking subsystem. -- Luca]
      Signed-off-by: NEyal Shapira <eyal@wizery.com>
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      5d3a1603
    • E
      wlcore: add ACX_PEER_CAP command · 530abe19
      Eliad Peller 提交于
      ACX_PEER_CAP command is just ACX_PEER_HT_CAP, but allows
      configuring the peer's support rates as well.
      
      this is needed because we start the station role when
      the remote rates are not known yet.
      
      the two commands should be unified in future fw versions,
      but for now add a new set_peer_cap per-hw op, that will
      use ACX_PEER_CAP for 18xx, and ACX_PEER_HT_CAP for 12xx.
      Signed-off-by: NEliad Peller <eliad@wizery.com>
      Signed-off-by: NArik Nemtsov <arik@wizery.com>
      Signed-off-by: NLuciano Coelho <coelho@ti.com>
      530abe19
  11. 07 12月, 2012 1 次提交
  12. 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
  13. 04 12月, 2012 6 次提交
  14. 28 11月, 2012 1 次提交
  15. 27 11月, 2012 5 次提交
  16. 27 9月, 2012 6 次提交