1. 07 2月, 2017 1 次提交
    • L
      iwlwifi: mvm: release static queues on bcast release · df88c08d
      Liad Kaufman 提交于
      A few of the static queues are enabled along with the bcast
      STA. Make sure they are removed along with it, rather than
      waiting for the mac ctxt release.
      
      This is needed because we sometimes have a STA being removed
      and then added again (either with the same sta_id or a
      different one). If we wait for the mac ctxt release we will
      try to allocate the queues again (as this is currently done
      in the STA allocation and not in the MAC init) although
      they weren't freed, and even if the sta_id of the STA has
      changed.
      Signed-off-by: NLiad Kaufman <liad.kaufman@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      df88c08d
  2. 26 1月, 2017 1 次提交
  3. 19 10月, 2016 2 次提交
  4. 19 9月, 2016 2 次提交
  5. 01 7月, 2016 1 次提交
  6. 10 5月, 2016 2 次提交
  7. 12 4月, 2016 1 次提交
  8. 06 4月, 2016 1 次提交
  9. 30 3月, 2016 3 次提交
  10. 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
  11. 01 2月, 2016 2 次提交
  12. 08 1月, 2016 2 次提交
  13. 21 12月, 2015 1 次提交
  14. 20 12月, 2015 1 次提交
  15. 02 12月, 2015 1 次提交
  16. 18 11月, 2015 1 次提交
  17. 25 10月, 2015 1 次提交
  18. 05 10月, 2015 3 次提交
  19. 28 8月, 2015 1 次提交
  20. 04 8月, 2015 1 次提交
  21. 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
  22. 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
  23. 30 3月, 2015 1 次提交
  24. 02 3月, 2015 1 次提交
  25. 01 3月, 2015 1 次提交
  26. 01 2月, 2015 1 次提交
  27. 22 1月, 2015 2 次提交
  28. 29 12月, 2014 1 次提交
  29. 01 12月, 2014 1 次提交
  30. 24 11月, 2014 1 次提交
    • A
      iwlwifi: mvm: Handle failed beacon transmissions during CSA · 7ef0aab6
      Andrei Otcheretianski 提交于
      The spec requires to decrement the CSA counters based on TBTT,
      regardless if the beacon was actually transmitted. Previously, the fw
      would send beacon notifications only for successfully transmitted
      beacons. This behavior resulted in inaccurate CSA countdown. In order
      to address this issue, the fw was changed to send beacon
      notifications also for not transmitted beacons. Such notifications
      have TX_STATUS_INTERNAL_ABORT (0x92).
      Don't start the CSA countdown before first successfully transmitted
      beacon, in order to guarantee that the CSA is announced for a
      required period.
      Signed-off-by: NAndrei Otcheretianski <andrei.otcheretianski@intel.com>
      7ef0aab6