1. 05 2月, 2021 3 次提交
  2. 10 12月, 2020 6 次提交
  3. 09 10月, 2020 2 次提交
  4. 02 10月, 2020 9 次提交
  5. 08 5月, 2020 1 次提交
  6. 24 4月, 2020 1 次提交
  7. 27 3月, 2020 1 次提交
  8. 24 12月, 2019 2 次提交
  9. 20 12月, 2019 1 次提交
  10. 15 11月, 2019 3 次提交
  11. 30 10月, 2019 1 次提交
  12. 25 10月, 2019 4 次提交
  13. 06 9月, 2019 6 次提交
    • J
      iwlwifi: mvm: handle BAR_FRAME_RELEASE (0xc2) notification · fe69b7d1
      Johannes Berg 提交于
      In prior hardware generations (e.g. 9000 series), we received the BAR
      frame with fake NSSN information to handle releasing frames from the
      reorder buffer for the default queue, the other queues were getting
      the FRAME_RELEASE notification in this case.
      
      With multi-TID block-ack, the firmware no longer sends us the BAR
      frame because the fake RX is quite big (just the metadata is around
      48 bytes or so). Instead, it now sends us one (or multiple) special
      release notifications (0xc2). The hardware consumes these as well,
      but only generates the FRAME_RELEASE (0xc3) for queues other than
      the default queue. We thus need to handle them in the same way we
      handle the normal FRAME_RELEASE.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      fe69b7d1
    • J
      iwlwifi: mvm: drop BA sessions on too many old-SN frames · 0968fbfa
      Johannes Berg 提交于
      Certain APs (I think a certain Broadcom model) interact badly with our
      full state BA bitmap handling, and if triggered badly with many powersave
      transitions they keep sending frames from before the window, which our
      hardware then doesn't appear to ACK (to them) since it has moved on and
      is sending ACKs for higher SNs now.
      
      Try to detect this situation and if this keeps happening, disable the
      aggregation session.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      0968fbfa
    • L
      iwlwifi: always access the trans configuration via trans · 7d34a7d7
      Luca Coelho 提交于
      Stop accessing the trans configuration via the iwl_cfg structure and
      always access it via the iwl_trans structure.  This completes the
      requirements to disassociate the trans-specific configuration from the
      rest of the configuration.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      7d34a7d7
    • L
      iwlwifi: add a pointer to the trans_cfg directly in trans · 286ca8eb
      Luca Coelho 提交于
      Add a pointer to the iwl_trans structure and point it to the trans
      part of the cfg.  This is the first step in disassociating the trans
      configuration from the rest of the configuration.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      286ca8eb
    • L
      iwlwifi: separate elements from cfg that are needed by trans_alloc · 79b6c8fe
      Luca Coelho 提交于
      In order to be able to select the cfg depending on the HW revision or
      on the RF ID, we need to set up the trans before selecting the cfg.
      To do so, move the elements from cfg that are needed by
      iwl_trans_alloc() to a separate struct at the top of the cfg, so it
      can be used by other cfg types as well, before selecting the rest of
      the configuration.
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      79b6c8fe
    • G
      iwlwifi: support per-platform antenna gain · 6ce1e5c0
      Gil Adam 提交于
      TX power limits as defined in the OTP assume the worst case scenario
      in terms of the platform's atenna gain, but most platforms are below
      that value so they can use more TX power without passing the regulatory
      limit. If the platform indicates in the BIOS that it indeed has lower
      gain, and the geographic location allows it, higher TX power can be
      used. The driver reads the PPAG (Per-Platform Antenna Gain) data from
      BIOS (if it exists), validates it and sends the appropriate command to
      the FW. This flow happens once at FW init, in case of suspend/resume
      there is no need to read again from BIOS as we save those values during
      init, so just send the PPAG command again to FW.
      Signed-off-by: NGil Adam <gil.adam@intel.com>
      Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      6ce1e5c0