- 18 Feb, 2022 40 commits
-
-
Ilan Peer authored
As there is not real need to iterate the active interfaces twice. Signed-off-by:
Ilan Peer <ilan.peer@intel.com> Signed-off-by:
Luca Coelho <luciano.coelho@intel.com> Link: https://lore.kernel.org/r/iwlwifi.20220204122220.940e45167283.I99ddfeda3d4a50d21cb18b826ccf84b21a76c487@changeidSigned-off-by:
-
Johannes Berg authored
There's another field and so W=2 warns about this code, but in general it's nicer to use C99 initializers anyway to make the code easier to read. Signed-off-by:
Johannes Berg <johannes.berg@intel.com> Signed-off-by:
-
Johannes Berg authored
There's no point spelling out the same condition twice, so remove the second one. Signed-off-by:
-
Johannes Berg authored
Found with W=2, remove unused macros in C files. In one case move the macro under the corresponding ifdef. Signed-off-by:
-
Johannes Berg authored
There are two versions of the same definitions, with and without IWL_ prefix. Use the ones with IWL_ prefix, keeping the correct comment (microseconds). Signed-off-by:
-
Johannes Berg authored
There's no good reason to pick the opmode first and load this under the mutex, so just load it before continuing. This will let us load it asynchronously more easily later. Signed-off-by:
-
Matti Gottlieb authored
Adapt rx queue write pointer for Bz family. The register has moved to the same one as Tx. Signed-off-by:
Matti Gottlieb <matti.gottlieb@intel.com> Signed-off-by:
-
Johannes Berg authored
The Bz devices got a new completion descriptor again since we only ever really used 4 out of 32 bytes anyway. Adjust the code to deal with that. Note that the intention was to reduce the size, but the hardware was implemented wrongly. While at it, do some cleanups and remove the union to simplify the code, clean up iwl_pcie_free_bd_size() to no longer need an argument and add iwl_pcie_used_bd_size() with the logic to selct completion descriptor size. Signed-off-by:
-
Ilan Peer authored
Non PSC channels should generally be scanned based on information about collocated APs obtained during scan on legacy bands, and otherwise should not be scanned unless specifically requested so (as there are relatively many non PSC channels, scanning them passively is time consuming and interferes with regular data traffic). Thus, modify the scan logic to avoid passively scanning PSC channels if there is no information about collocated APs and the scan is not a passive scan. Signed-off-by:
-
Ilan Peer authored
The function iwl_mvm_umac_scan_fill_6g_chan_list() always returns 0. Change its return value to 'void'. Signed-off-by:
-
Mukesh Sisodiya authored
The config set TLV setting depend on dram allocation and if allocation failed the data used in config set tlv should not set this. Adding the check if dram fragment is available or not. Signed-off-by:
Mukesh Sisodiya <mukesh.sisodiya@intel.com> Fixes: 1a5daead ("iwlwifi: yoyo: support for ROM usniffer") Signed-off-by:
-
Ilan Peer authored
Currently, fragmented EBS was set for a channel only if the 'hb_type' was set to fragmented or balanced scan. However, 'hb_type' is set only in case of CDB, and thus fragmented EBS is never set for a channel for non-CDB devices. Fix it. Signed-off-by:
-
Abhishek Naik authored
The HE PHY capability - Tx 1024-QAM < 242-tone RU support was not handled for Ms RFs, add the relevant code for it. Signed-off-by:
Abhishek Naik <abhishek.naik@intel.com> Fixes: 1381eb5c ("iwlwifi: correct HE capabilities") Signed-off-by:
-
Johannes Berg authored
These cause extra warnings (at least with W=3), avoid them. Signed-off-by:
-
Johannes Berg authored
Somehow, sparse cannot track the cond_lock() here properly, but if we return directly from the inner basic block then it doesn't complain. Refactor the code a bit to make it not complain. Signed-off-by:
-
Johannes Berg authored
Change a few places to not shadow variables. Signed-off-by:
-
Luca Coelho authored
We haven't used this command for a long time, if ever, so we can remove all related definitions. Signed-off-by:
-
Johannes Berg authored
This function puts a fairly large structure unnecessarily on the stack, and also has a few other very strange things, clean it up a bit. Signed-off-by:
-
Johannes Berg authored
Nobody other than iwlwifi itself should be accessing the symbols that it exports, so make that clear by moving them into a separate new namespace ("IWLWIFI"). Signed-off-by: -
Johannes Berg authored
We never return errors there, so just make it void. Signed-off-by:
-
Andrei Otcheretianski authored
If the device is malfunctioning and reports too short rx descriptor length, iwl_rx_packet_payload_len() will underflow, eventually resulting in accessing memory out of bounds and other bad things. Prevent this. Signed-off-by:
Andrei Otcheretianski <andrei.otcheretianski@intel.com> Signed-off-by:
-
Miri Korenblit authored
In MCC_UPDATE_CMD we get from the FW the number of entries in the channel info array. We used to WARN_ON if this parameter is greater than we expected. Since this is not really a driver bug, and since it might happen in some valid cases too, we shouldn't use a warning here. Fix this by replacing the WARN_ON with a debug print. Signed-off-by:
Miri Korenblit <miriam.rachel.korenblit@intel.com> Signed-off-by:
-
Luca Coelho authored
Sometimes it can be useful to know the OTP minor version, so read it from the register and print it out. Signed-off-by:
-
Mike Golant authored
Add support for BZ-U and BZ-L HW with GF, GF4, MR, FM and FM4 RF modules Signed-off-by:
Mike Golant <michael.golant@intel.com> Signed-off-by:
-
Miri Korenblit authored
A new version was added to the CT-KILL notification API. Add support for it. In addition, print the two fields that was added in this version. Signed-off-by:
-
Rotem Saado authored
Due to preg protection we cannot write to this register while FW is running (when FW in Halt it is ok). since we have some cases that we need to dump this region while FW is running remove this writing from DRV. FW will do this writing. Signed-off-by:
Rotem Saado <rotem.saado@intel.com> Fixes: 89639e06 ("iwlwifi: yoyo: support for new DBGI_SRAM region") Signed-off-by:
-
Johannes Berg authored
This now includes 320 MHz and some other data for EHT, support it, but don't fill in the additional EHT data for now. Signed-off-by:
-
Mukesh Sisodiya authored
Support debug collection of the platform IMR memory region, where data is copied by FW during d3 state Signed-off-by:
-
Rotem Saado authored
number of DBGCs and number of fragments per DBGC is hw family dependency and not capability. Signed-off-by:
-
Yaara Baruch authored
Add MS devices to the driver. For now we are using the same FW image as MR (since they differ only in rfid), but it should change in the future. Signed-off-by:
Yaara Baruch <yaara.baruch@intel.com> Signed-off-by:
-
Johannes Berg authored
Since commit a05829a7 ("cfg80211: avoid holding the RTNL when calling the driver") we're not only holding the RTNL when going in and out of suspend, but also the wiphy->mtx. Add that to the D3 test debugfs in iwlwifi since it's required for various calls to mac80211. Fixes: a05829a7 ("cfg80211: avoid holding the RTNL when calling the driver") Signed-off-by:
-
Luca Coelho authored
We may not have all the interfaces added to the driver when we get the THERMAL_DUAL_CHAIN_REQUEST notification from the FW, so instead of iterating all vifs to update SMPS, iterate only the ones that are already assigned. The interfaces that were not assigned yet, will be updated accordingly when we start using them. Signed-off-by:
-
Mordechay Goodstein authored
Our HE capable HW also supports DCM mode, so broadcast this capability in the HE PHY capabilities. Signed-off-by:
Mordechay Goodstein <mordechay.goodstein@intel.com> Signed-off-by:
-
Mordechay Goodstein authored
Currently we enable DCM if the peer supports RX without checking whether we advertised that we support TX. Fix this by also checking that our TX side is set. Signed-off-by:
-
Rotem Saado authored
DBGI SRAM is new type of monitor, therefore it should be dump as monitor type with ini dump monitor header. Signed-off-by:
-
Mordechay Goodstein authored
Until now function just got a pointer to some buffer and used it as if it's good to use with no boundaries about size left in the buffer. This infra helps for internal functions ops to make sure buffer usage is in bound of allocation. We also add external checks with warnings to verify every internal function didn't exceed usage of the free buffer size. Signed-off-by:
-
Emmanuel Grumbach authored
Those devices have more BAIDs, which is the hardware module that tracks the BA session. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Johannes Berg authored
Due to some rearchitecting inside the firmware, a new BAID allocation command is being introduced. Support it. Note that with it the firmware no longer returns "no space" but will crash instead, so check for that before sending the command to the firmware. Signed-off-by:
-
Johannes Berg authored
Refactor the firmware call in iwl_mvm_sta_rx_agg() out into its own function to be able to change it more easily in the next patch. Signed-off-by:
-
Mordechay Goodstein authored
In order to support 1K aggregations start ba queue with at least double the size, also allocate based on the connecting type to save memory usage. Signed-off-by:
-
