Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 27 3月, 2020 7 次提交
  3. 18 3月, 2020 12 次提交
  5. 04 1月, 2020 3 次提交
    • L
      iwlwifi: add device name to device_info · 0b295a1e
      由 Luca Coelho 提交于 
      We have a lot of mostly duplicated data structures that are repeated
only because the device name string is different.  To avoid this, move
the string from the cfg to the trans structure and add it
independently from the rest of the configuration to the PCI mapping
tables.
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      0b295a1e
    • L
      iwlwifi: implement a new device configuration table · 2a612a60
      由 Luca Coelho 提交于 
      Add a new device table that contains information that can be checked
at runtime in order to decide which configuration to use.  This allows
us to map the full cfg independently from the tran-specific
configuration.

This is the first step in creating the new table.  Subsequent patches
will add the possibility of checking different values at runtime in
order to make the decision.
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      2a612a60
    • L
      iwlwifi: assume the driver_data is a trans_cfg, but allow full cfg · b3bd6416
      由 Luca Coelho 提交于 
      With the new concept of separating the trans-specific (trans_cfg) data
from the rest of the cfg, we will start mapping only the trans_cfg
part to the PCI device ID/subsystem device ID.  So we can assume that
the data passed to the probe function contains the trans_cfg, but
since the full cfg still contains the trans_cfg at the beginning, we
can allow a full cfg to be passed as well.  This makes it easier to
convert the existing tables one by one.
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      b3bd6416
  7. 23 12月, 2019 3 次提交
    • L
      iwlwifi: remove CSR registers abstraction · 6dece0e9
      由 Luca Coelho 提交于 
      We needed this abstraction for some CSR registers for
IWL_DEVICE_22560, but that has been removed, so we don't need the
abstraction anymore.  Remove it.
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      6dece0e9
    • L
      iwlwifi: remove some outdated iwl22000 configurations · b81b7bd0
      由 Luca Coelho 提交于 
      A few configuration structures were either not referenced anymore or
assigned to devices IDs that were not in use anymore.  Remove them.
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      b81b7bd0
    • J
      iwlwifi: allocate more receive buffers for HE devices · c042f0c7
      由 Johannes Berg 提交于 
      For HE-capable devices, we need to allocate more receive buffers as
there could be 256 frames aggregated into a single A-MPDU, and then
they might contain A-MSDUs as well. Until 22000 family, the devices
are able to put multiple frames into a single RB and the default RB
size is 4k, but starting from AX210 family this is no longer true.
On the other hand, those newer devices only use 2k receive buffers
(by default).

Modify the code and configuration to allocate an appropriate number
of RBs depending on the device capabilities:

 * 4096 for AX210 HE devices, which use 2k buffers by default,
 * 2048 for 22000 family devices which use 4k buffers by default,
 * 512 for existing 9000 family devices, which doesn't really
   change anything since that's the default before this patch,
 * 512 also for AX210/22000 family devices that don't do HE.

Theoretically, for devices lower than AX210, we wouldn't have to
allocate that many RBs if the RB size was manually increased, but
to support that the code got more complex, and it didn't really
seem necessary as that's a use case for monitor mode only, where
hopefully the wasted memory isn't really much of a concern.

Note that AX210 devices actually support bigger than 12-bit VID,
which is required here as we want to allocate 4096 buffers plus
some for quick recycling, so adjust the code for that as well.
Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
Signed-off-by: NLuca Coelho <luciano.coelho@intel.com>
      c042f0c7
  9. 10 12月, 2019 1 次提交
  11. 23 10月, 2019 4 次提交
  13. 09 10月, 2019 1 次提交
  15. 06 9月, 2019 9 次提交