1. 10 8月, 2017 1 次提交
  2. 09 8月, 2017 1 次提交
  3. 01 8月, 2017 2 次提交
    • L
      iwlwifi: mvm: refactor beacon template command code · 09856582
      Luca Coelho 提交于
      We currently support 3 different versions of the beacon template
      command and the code does some tricks in order to reuse what is
      possible across these versions.  But it is a bit complicated to read
      and soon there will be one more variation that the driver needs
      implement, which would complicate it even further.
      
      Refactor the way we send beacon template commands, which increases the
      code size a bit, but makes it much easier to read.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      09856582
    • J
      iwlwifi: reorganize firmware API · d172a5ef
      Johannes Berg 提交于
      Apart from DVM, all firmware uses the same base API, and there's
      code outside iwlmvm that needs to interact with it. Reflect this
      in the source better and reorganize the firmware API to a new
      fw/api/ directory.
      
      While at it, split the already pretty large fw-api.h file into a
      number of smaller files, going from almost 3k lines in there to
      a maximum number of lines less than 1k.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      d172a5ef
  4. 29 6月, 2017 3 次提交
  5. 23 6月, 2017 3 次提交
  6. 06 6月, 2017 1 次提交
    • G
      iwlwifi: mvm: rs: start using LQ command color · ea42d1cb
      Gregory Greenman 提交于
      Up until now, the driver was comparing the rate reported by the FW and
      the rate of the latest LQ command to avoid processing data belonging
      to the old LQ command. Recently, FW changed the meaning of the initial
      rate field in tx response and it holds the actual rate (which is not
      necessarily the initial rate of LQ's rate table). Use instead LQ cmd
      color to be able to filter out tx responses/BA notifications which
      where sent during earlier LQ commands' time frame.
      
      This fixes some throughput degradation in noisy environments.
      Signed-off-by: NGregory Greenman <gregory.greenman@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      ea42d1cb
  7. 02 6月, 2017 5 次提交
  8. 20 4月, 2017 3 次提交
  9. 11 4月, 2017 1 次提交
  10. 07 2月, 2017 1 次提交
  11. 27 9月, 2016 2 次提交
  12. 16 9月, 2016 1 次提交
  13. 30 8月, 2016 1 次提交
  14. 06 7月, 2016 1 次提交
    • A
      iwlwifi: mvm: add support for GCMP encryption · 2a53d166
      Ayala Beker 提交于
      Newer hardware supports GCMP and GCMP 256-bit ciphers.
      Add support for adding/setting GCMP key for TX mode.
      
      In the TX command handling GCMP-256 is handled in a different
      way as the key size should be up to 128-bits:
      Set the key value to the key index in the key table,
      and specify that this key should be taken form the key table
      instead of from the TX command.
      
      While at it - convert security control flags to an enum.
      Signed-off-by: NAyala Beker <ayala.beker@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      2a53d166
  15. 01 7月, 2016 1 次提交
  16. 30 3月, 2016 1 次提交
  17. 26 1月, 2016 1 次提交
    • G
      iwlwifi: mvm: rs: fix TPC statistics handling · 69c7fda4
      Gregory Greenman 提交于
      FW behaviour changed and now updates driver about the used TPC
      reduction in the following cases:
      1. In tx response, which is used mostly for a single frame case
      2. In BA notification
      
      When tx aggregation fails with the initial rate, FW will send
      to the driver BA notification and will try to transmit with the
      next rate, but this time without tx power reduction. Thus, in case
      of a failure with the initial rate, driver will get two BA notifications,
      the first one with reduced tx power as in the LQ command and the second
      one with 0 power reduction.
      
      This patch adapts the TPC statistics according to the description above:
      1. Use BA notifications instead of Tx response
      2. For TPC only, drop the optimization which considers empty BA as one
      MPDU. The reason is that with TPC we want to recover very quickly from
      a bad power reduction and, therefore we'd like the success ratio to get
      an immediate hit when failing to get a BA, so we'd switch back to a
      lower or zero power reduction
      Signed-off-by: NGregory Greenman <gregory.greenman@intel.com>
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      69c7fda4
  18. 02 12月, 2015 1 次提交
  19. 18 11月, 2015 1 次提交
  20. 05 8月, 2015 1 次提交
  21. 22 1月, 2015 1 次提交
  22. 16 9月, 2014 1 次提交
  23. 06 7月, 2014 1 次提交
  24. 25 6月, 2014 1 次提交
  25. 10 4月, 2014 1 次提交
  26. 12 3月, 2014 1 次提交
  27. 01 1月, 2014 1 次提交
  28. 18 12月, 2013 1 次提交