1. 29 6月, 2018 1 次提交
    • O
      cfg80211: use BIT_ULL for NL80211_STA_INFO_* attribute types · 397c657a
      Omer Efrat 提交于
      The BIT macro uses unsigned long which some architectures handle as 32 bit
      and therefore might cause macro's shift to overflow when used on a value
      equals or larger than 32 (NL80211_STA_INFO_RX_DURATION and afterwards).
      
      Since 'filled' member in station_info changed to u64, BIT_ULL macro
      should be used with all NL80211_STA_INFO_* attribute types instead of BIT
      to prevent future possible bugs when one will use BIT macro for higher
      attributes by mistake.
      
      This commit cleans up all usages of BIT macro with the above field
      in cfg80211 by changing it to BIT_ULL instead. In addition, there are
      some places which don't use BIT nor BIT_ULL macros so align those as well.
      Signed-off-by: NOmer Efrat <omer.efrat@tandemg.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      397c657a
  2. 15 6月, 2018 4 次提交
  3. 23 5月, 2018 5 次提交
  4. 22 5月, 2018 1 次提交
    • D
      nl80211: Fix compilation · ba8f566a
      Denis Kenzior 提交于
      Commit 7ea3e110 seems to have
      introduced:
      
      net/wireless/nl80211.c: In function ‘nl80211_get_station’:
      net/wireless/nl80211.c:4802:34: error: incompatible type for argument 1 of ‘cfg80211_sinfo_release_content’
         cfg80211_sinfo_release_content(sinfo);
                                        ^~~~~
      In file included from net/wireless/nl80211.c:24:0:
      ./include/net/cfg80211.h:5721:20: note: expected ‘struct station_info *’ but argument is of type ‘struct station_info’
       static inline void cfg80211_sinfo_release_content(struct station_info *sinfo)
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      Fixes: 7ea3e110 ("cfg80211: release station info tidstats where needed")
      Signed-off-by: NDenis Kenzior <denkenz@gmail.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      ba8f566a
  5. 18 5月, 2018 4 次提交
  6. 08 5月, 2018 3 次提交
    • T
      cfg80211: Expose TXQ stats and parameters to userspace · 52539ca8
      Toke Høiland-Jørgensen 提交于
      This adds support for exporting the mac80211 TXQ stats via nl80211 by
      way of a nested TXQ stats attribute, as well as for configuring the
      quantum and limits that were previously only changeable through debugfs.
      
      This commit adds just the nl80211 API, a subsequent commit adds support to
      mac80211 itself.
      Signed-off-by: NToke Høiland-Jørgensen <toke@toke.dk>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      52539ca8
    • B
      cfg80211: average ack rssi support for data frames · 81d5439d
      Balaji Pothunoori 提交于
      Average ack rssi will be given to userspace via NL80211 interface
      if firmware is capable. Userspace tool ‘iw’ can process this
      information and give the output as one of the fields in
      ‘iw dev wlanX station dump’.
      
      Example output :
      
      localhost ~ #iw dev wlan-5000mhz station dump Station
      34:f3:9a:aa:3b:29 (on wlan-5000mhz)
              inactive time:  5370 ms
              rx bytes:       85321
              rx packets:     576
              tx bytes:       14225
              tx packets:     71
              tx retries:     0
              tx failed:      2
              beacon loss:    0
              rx drop misc:   0
              signal:         -54 dBm
              signal avg:     -53 dBm
              tx bitrate:     866.7 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 2
              rx bitrate:     866.7 MBit/s VHT-MCS 9 80MHz short GI VHT-NSS 2
              avg ack signal: -56 dBm
              authorized:     yes
              authenticated:  yes
              associated:     yes
              preamble:       short
              WMM/WME:        yes
              MFP:            no
              TDLS peer:      no
              DTIM period:    2
              beacon interval:100
             short preamble: yes
             short slot time:yes
             connected time: 203 seconds
      
      Main use case is to measure the signal strength of a connected station
      to AP. Data packet transmit rates and bandwidth used by station can vary
      a lot even if the station is at fixed location, especially if the rates
      used are multi stream(2stream, 3stream) rates with different bandwidth(20/40/80 Mhz).
      These multi stream rates are sensitive and station can use different transmit power
      for each of the rate and bandwidth combinations. RSSI measured from these RX packets
      on AP will be not stable and can vary a lot with in a short time.
      Whereas 802.11 ack frames from station are sent relatively at a constant
      rate (6/12/24 Mbps) with constant bandwidth(20 Mhz).
      So average rssi of the ack packets is good and more accurate.
      Signed-off-by: NBalaji Pothunoori <bpothuno@codeaurora.org>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      81d5439d
    • H
      nl80211: Add wmm rule attribute to NL80211_CMD_GET_WIPHY dump command · 50f32718
      Haim Dreyfuss 提交于
      This will serve userspace entity to maintain its regulatory limitation.
      More specifcally APs can use this data to calculate the WMM IE when
      building: beacons, probe responses, assoc responses etc...
      Signed-off-by: NHaim Dreyfuss <haim.dreyfuss@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      50f32718
  7. 20 4月, 2018 1 次提交
  8. 29 3月, 2018 8 次提交
  9. 21 3月, 2018 1 次提交
    • D
      cfg80211/nl80211: add DFS offload flag · 13cf6dec
      Dmitry Lebed 提交于
      Add wiphy EXT_FEATURE flag to indicate that HW or driver does
      all DFS actions by itself.
      User-space functionality already implemented in hostapd using
      vendor-specific (QCA) OUI to advertise DFS offload support.
      Need to introduce generic flag to inform about DFS offload support.
      For devices with DFS_OFFLOAD flag set user-space will no longer
      need to issue CAC or do any actions in response to
      "radar detected" events. HW will do everything by itself and send
      events to user-space to indicate that CAC was started/finished, etc.
      Signed-off-by: NDmitrii Lebed <dlebed@quantenna.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      13cf6dec
  10. 19 2月, 2018 3 次提交
  11. 31 1月, 2018 5 次提交
  12. 19 1月, 2018 1 次提交
  13. 15 1月, 2018 1 次提交
  14. 04 1月, 2018 1 次提交
  15. 19 12月, 2017 1 次提交