Skip to content

L
linux
An error occurred fetching the project authors.
Switch branch/tag
  1. 01 Dec, 2015 1 commit
  3. 18 Nov, 2015 1 commit
  5. 05 Oct, 2015 1 commit
    • Liad Kaufman's avatar
      iwlwifi: mvm: support using multiple ACs on single HW queue · 4ecafae9
      Liad Kaufman authored 
      "DQA" is shorthand for "dynamic queue allocation", with the
idea of allocating queues per-RA/TID on-demand rather than
using shared queues statically allocated per vif. The goal
of this is to enable future features (like GO PM) and to
improve performance measurements of TX traffic.

When RA/TID streams can't be neatly sorted into different AC
queues, DQA allows sharing queues for the same RA. This means
that DQA allows different ACs may reach the same HW queue.

Update the code to allow such queue sharing by having a mapping
between the HW queue and the mac80211 queues using it (as this
could be more than one queue).
Signed-off-by: default avatarLiad Kaufman <liad.kaufman@intel.com>
Signed-off-by: default avatarLuca Coelho <luciano.coelho@intel.com>
      4ecafae9
  7. 28 Aug, 2015 1 commit
  9. 04 Aug, 2015 3 commits
  11. 03 Jun, 2015 1 commit
    • Johannes Berg's avatar
      iwlwifi: prepare for higher API/CAPA bits · 859d914c
      Johannes Berg authored 
      Currently, loading the firmware fails when it has higher API or CAPA
bits than the driver supports. That's an issue with integration.

At the same time, actually using api[0] and capa[0] will become
confusing when we also have api[1] and capa[1], and it's almost
certain that we'll mix up the bits and use the bits for api[1] with
api[0] by accident.

Avoid all this by translating the API/CAPA bits to the regular kernel
test_bit() format, and also providing wrapper functions. Also use the
__bitwise__ facility of sparse to check that we're testing the right
one.
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      859d914c
  13. 02 Apr, 2015 2 commits
  15. 30 Mar, 2015 1 commit
  17. 12 Mar, 2015 1 commit
  19. 01 Mar, 2015 4 commits
  21. 01 Feb, 2015 2 commits
  23. 22 Jan, 2015 1 commit
  25. 05 Jan, 2015 1 commit
  27. 28 Dec, 2014 1 commit
  29. 29 Oct, 2014 1 commit
  31. 16 Sep, 2014 1 commit
    • Avri Altman's avatar
      iwlwifi: mvm: prepare for scheduler config command · 3edf8ff6
      Avri Altman authored 
      The scheduler is a HW sub-block that directs the work of the Flow
Handler by issuing requests for frame transfers, specifying source
and destination. Its primary function is to allocate flows into the
TX FIFOs based upon a pre-determined mapping.

The driver has some responsibilities to the scheduler, namely
initialising and maintaining the hardware registers. This is
currently done by directly accessing them, which can cause races
with the firmware also accessing the registers.

To address this problem, change the driver to no longer directly
access the registers but go through the firmware for this if the
firmware has support for DQA and thus the new command.
Signed-off-by: default avatarAvri Altman <avri.altman@intel.com>
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      3edf8ff6
  33. 03 Sep, 2014 2 commits
  35. 07 Jul, 2014 2 commits
  37. 06 Jul, 2014 2 commits
  39. 22 May, 2014 1 commit
  41. 19 May, 2014 1 commit
  43. 13 May, 2014 2 commits
  45. 06 May, 2014 2 commits
  47. 13 Apr, 2014 1 commit
  49. 18 Mar, 2014 3 commits
    • Johannes Berg's avatar
      iwlwifi: mvm: ignore unchanged low-latency flag · 3510aea4
      Johannes Berg authored 
      If the low-latency update is called but there's no change then
ignore the update instead of triggering all the required work.
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      3510aea4
    • Alexander Bondar's avatar
      iwlwifi: mvm: configure low latency dependent scan parameters · 50df8a30
      Alexander Bondar authored 
      In case of system low latency configure passive scan to be fragmented.
Set the following scan parameters for both immediate and scheduled scan:
 - passive scan fragment duration = 20ms
 - out-of-channel time = 70ms
 - suspend time = 105ms
Restructure channel's active/passive dwell time configuration to better
suit the above change.

The idea is that under low latency traffic passive scan is fragmented,
i.e. that dwell on a particular channel will be fragmented. Each
fragment dwell time is 20ms and fragments period is 105ms. Skipping to
next channel will be delayed by the same period (105ms). So suspend_time
parameter describing both fragments and channels skipping periods is set
to 105ms. This value is chosen so that overall passive scan duration
will not be too long. Max_out_time in this case is set to 70ms, so for
active scanning operating channel will be left for 70ms while for
passive still for 20ms (fragment dwell).
Signed-off-by: default avatarAlexander Bondar <alexander.bondar@intel.com>
Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      50df8a30
    • Emmanuel Grumbach's avatar
      iwlwifi: mvm: send udev event upon firmware error to dump logs · 1bd3cbc1
      Emmanuel Grumbach authored 
      When the firmware asserts, the driver will dump the firmware
state to an internal buffer. This buffer is kept aside until
it is dumped through debugfs. Once an external application
fetched the data, the buffer is freed and a new buffer can
be allocated in case another assert occurs.

A udev event is sent to trigger an external application.

A simple rule like:
DRIVER=="iwlwifi", ACTION=="change", RUN+="/sbin/dump_sram.sh"

can fetch the data from debugfs.

Here is my dump_sram.sh:

phyname=$(basename ${DEVPATH})
date=$(date +%F_%H_%M)
filename=/var/log/iwl-sram-${phyname}-${date}.bin
cat /sys/kernel/debug/ieee80211/${phyname}/iwlwifi/iwlmvm/fw_error_dump > ${filename}

The current SRAM size is 80KB so, currently:
$ ls -lh iwl-sram-phy0-2014-03-16_13_14.bin
-rw-r--r-- 1 emmanuel emmanuel 81K Mar 16 13:15 iwl-sram-phy0-2014-03-16_13_14.bin

and after compression:
$ ls -lh iwl-sram-phy0-2014-03-16_13_14.bin.xz
-rw-r--r-- 1 emmanuel emmanuel 13K Mar 16 13:15 iwl-sram-phy0-2014-03-16_13_14.bin.xz
Signed-off-by: default avatarEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      1bd3cbc1
  51. 13 Feb, 2014 1 commit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7