1. 26 4月, 2017 1 次提交
  2. 20 4月, 2017 2 次提交
  3. 11 4月, 2017 1 次提交
    • S
      iwlwifi: mvm: add multicast station · 26d6c16b
      Sara Sharon 提交于
      Currently multicast queue is associated with the broadcast
      station.
      
      This raises quite a few issues:
      
      The multicast queue has a special treatment:
      - It is sent in the MAC context command
      - It is excluded from tfd_queue_mask
      
      In DQA mode we end up enabling two queues - the probe response
      queue and the multicast queue - with the same station (broadcast)
      and TID while in DQA mode it should be unique RA-TID.
      Firmware will enforce it for a000 devices, so this allocation
      will fail.
      
      In addition, in a000 devices the FW will set the FIFO and not
      the driver. So there is a need for FW to know when we enable
      the queue that it is multicast queue so it will be bound to
      the multicast FIFO. There is no such way in current design.
      
      In order to simplify driver and firmware handling of this queue
      create a multicast station.
      This solves the unique RA-TID issue in the short term and serves
      as preparation for the long term.
      
      In the long term we will also add a flag marking this station for
      the FW as the multicast station.
      Once we will do that the FW will know this is the multicast queue
      immediately when it is added and bind it to the correct FIFO.
      It will also enable removing the special treatment of the
      queue in the MAC context command.
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      26d6c16b
  4. 24 3月, 2017 1 次提交
  5. 07 2月, 2017 2 次提交
  6. 26 1月, 2017 1 次提交
  7. 19 10月, 2016 2 次提交
  8. 19 9月, 2016 2 次提交
  9. 01 7月, 2016 1 次提交
  10. 10 5月, 2016 2 次提交
  11. 12 4月, 2016 1 次提交
  12. 06 4月, 2016 1 次提交
  13. 30 3月, 2016 3 次提交
  14. 28 2月, 2016 1 次提交
    • S
      iwlwifi: mvm: update rx_status with mactime flag · 77fe7395
      Sara Sharon 提交于
      When forming IBSS, mac80211 scans in order to find an already
      existing cell to join.
      In case the scan does not find any existing cell a new IBSS
      cell is formed.
      When receiving the beacons of another IBSS cell we should
      merge if the other IBSS cell's TSF is higher than ours.
      However, currently iwlmvm does not set any timestamp flag in
      rx_status so there is no valid rx timestamp to compare the
      beacon's TSF to.
      The reason for that is that TSF as indicated by the firmware
      is at INA time, but up till now mac80211 expected the TSF at
      the beginning or end of the MPDU.
      Set the flag to the newly added RX_FLAG_MACTIME_PLCP_START flag.
      Signed-off-by: NSara Sharon <sara.sharon@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      77fe7395
  15. 01 2月, 2016 2 次提交
  16. 08 1月, 2016 2 次提交
  17. 21 12月, 2015 1 次提交
  18. 20 12月, 2015 1 次提交
  19. 02 12月, 2015 1 次提交
  20. 18 11月, 2015 1 次提交
  21. 25 10月, 2015 1 次提交
  22. 05 10月, 2015 3 次提交
  23. 28 8月, 2015 1 次提交
  24. 04 8月, 2015 1 次提交
  25. 10 6月, 2015 1 次提交
    • J
      mac80211: convert HW flags to unsigned long bitmap · 30686bf7
      Johannes Berg 提交于
      As we're running out of hardware capability flags pretty quickly,
      convert them to use the regular test_bit() style unsigned long
      bitmaps.
      
      This introduces a number of helper functions/macros to set and to
      test the bits, along with new debugfs code.
      
      The occurrences of an explicit __clear_bit() are intentional, the
      drivers were never supposed to change their supported bits on the
      fly. We should investigate changing this to be a per-frame flag.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      30686bf7
  26. 02 4月, 2015 1 次提交
    • J
      iwlwifi: mvm: do string formatting in debug triggers · 5d4f929e
      Johannes Berg 提交于
      The current code has a lot of duplicates of printing into a buffer
      (while having to make sure it's NUL-filled and -terminated) and
      then passing that to the debug trigger collection.
      
      Since that's error-prone, instead make the debug trigger collection
      function take a format string and format arguments (with compiler
      validity checking) and handle the buffer internally.
      
      This makes one behavioural change -- instead of sending the whole
      buffer to userspace (clearing is needed to not leak stack data) it
      just passes the actual string (including NUL-terminator.)
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      5d4f929e
  27. 30 3月, 2015 1 次提交
  28. 02 3月, 2015 1 次提交
  29. 01 3月, 2015 1 次提交