1. 28 1月, 2017 2 次提交
  2. 01 12月, 2016 2 次提交
  3. 23 11月, 2016 4 次提交
  4. 31 8月, 2016 2 次提交
  5. 06 7月, 2016 1 次提交
    • A
      nl80211: support beacon report scanning · 1d76250b
      Avraham Stern 提交于
      Beacon report radio measurement requires reporting observed BSSs
      on the channels specified in the beacon request. If the measurement
      mode is set to passive or active, it requires actually performing a
      scan (passive or active, accordingly), and reporting the time that
      the scan was started and the time each beacon/probe was received
      (both in terms of TSF of the BSS of the requesting AP). If the
      request mode is table, this information is optional.
      In addition, the radio measurement request specifies the channel
      dwell time for the measurement.
      
      In order to use scan for beacon report when the mode is active or
      passive, add a parameter to scan request that specifies the
      channel dwell time, and add scan start time and beacon received time
      to scan results information.
      
      Supporting beacon report is required for Multi Band Operation (MBO).
      Signed-off-by: NAssaf Krauss <assaf.krauss@intel.com>
      Signed-off-by: NDavid Spinadel <david.spinadel@intel.com>
      Signed-off-by: NAvraham Stern <avraham.stern@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      1d76250b
  6. 12 5月, 2016 1 次提交
  7. 26 4月, 2016 1 次提交
    • M
      wil6210: prevent deep sleep of 60G device in critical paths · 349214c1
      Maya Erez 提交于
      In idle times 60G device can enter deep sleep and turn off
      its XTAL clock.
      Host access triggers the device power-up flow which will hold
      the AHB during XTAL stabilization until device switches from
      slow-clock to XTAL clock.
      This behavior can stall the PCIe bus for some arbitrary period
      of time.
      In order to prevent this stall, host can vote for High Latency
      Access Policy (HALP) before reading from PCIe bus.
      This vote will wakeup the device from deep sleep and prevent
      deep sleep until unvote is done.
      Signed-off-by: NMaya Erez <qca_merez@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      349214c1
  8. 12 4月, 2016 1 次提交
  9. 07 3月, 2016 5 次提交
  10. 02 2月, 2016 1 次提交
    • M
      wil6210: protect synchronous wmi commands handling · fe5c271e
      Maya Erez 提交于
      In case there are multiple WMI commands with the same reply_id,
      the following scenario can occur:
      - Driver sends the first command to the device
      - The reply didn’t get on time and there is timeout
      - Reply_id, reply_buf and reply_size are set to 0
      - Driver sends second wmi command with the same reply_id as the first
      - Driver sets wil->reply_id
      - Reply for the first wmi command arrives and handled by wmi_recv_cmd
      - As its ID fits the reply_id but the reply_buf is not set yet it is
      handled as a reply with event handler, and WARN_ON is printed
      
      This patch guarantee atomic setting of all the reply variables and
      prevents the above scenario.
      Signed-off-by: NMaya Erez <qca_merez@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      fe5c271e
  11. 26 1月, 2016 1 次提交
    • M
      wil6210: handle multiple connect/disconnect events · 0916d9f2
      Maya Erez 提交于
      In the current solution wil6210 configures the vring in a worker
      and holds only one pending CID. This implementation may lead to
      race conditions between connect and disconnect events of multiple
      stations or fast connect/disconnect events of the same station.
      
      In order to allow the removal of the connect worker and handling of
      WMI_VRING_CFG_DONE_EVENTID in the connect event, the WMI replies
      that provide the reply in a given buffer needs to be handled
      immediately in the WMI event interrupt thread.
      To prevent deadlocks, WMI replies that requires additional
      handling are still handled via the events list.
      Signed-off-by: NMaya Erez <qca_merez@qca.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      0916d9f2
  12. 08 12月, 2015 1 次提交
  13. 29 10月, 2015 2 次提交
  14. 09 10月, 2015 1 次提交
  15. 17 8月, 2015 1 次提交
    • N
      wil6210: match wait_for_completion_timeout return type · f4bbb829
      Nicholas Mc Guire 提交于
      Return type of wait_for_completion_timeout is unsigned long not int.
      As remain is exclusively used for wait_for_completion_timeout here its
      type is simply changed to unsigned long.
      
      API conformance testing for completions with coccinelle spatches are being
      used to locate API usage inconsistencies:
      ./drivers/net/wireless/ath/wil6210/wmi.c:827
      	int return assigned to unsigned long
      
      Patch was compile tested with x86_64_defconfig + CONFIG_ATH_CARDS=m,
      CONFIG_WIL6210=m
      
      Patch is against 4.1-rc3 (localversion-next is -next-20150514)
      Signed-off-by: NNicholas Mc Guire <hofrat@osadl.org>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      f4bbb829
  16. 06 8月, 2015 5 次提交
  17. 09 6月, 2015 2 次提交
  18. 05 5月, 2015 2 次提交
  19. 20 3月, 2015 2 次提交
  20. 27 2月, 2015 2 次提交
  21. 29 1月, 2015 1 次提交