- 06 Jun, 2023 36 commits
-
-
Alon Giladi authored
Change the field pnvm_dram to an array that describes many regions and add a counter to the number of pnvm regions that were allocated in DRAM. Signed-off-by:
Alon Giladi <alon.giladi@intel.com> Signed-off-by:
Gregory Greenman <gregory.greenman@intel.com> Link: https://lore.kernel.org/r/20230606103519.bb206d71bf45.I627640701757bb2f234f8e18a3afbd6af1206658@changeidSigned-off-by:
Johannes Berg <johannes.berg@intel.com>
-
Alon Giladi authored
Change iwl_pnvm_parse so it will only save the information into the iwl_pnvm_image struct. This enables to use the parsing code for the power reduce tables in the future. Signed-off-by:
-
Alon Giladi authored
Take the part that is copying the pnvm image into DRAM, out of the the method that sets the prph_scratch. Makes the code cleaner since those 2 operations don't always happen together (loading should happen only once while setting can happen more than once). In addition, each operation will get more complex in the future when it will support also larger pnvm images. Signed-off-by:
-
Alon Giladi authored
Generalize iwl_pnvm_parse(). This saves us from copying each payload twice (first in the parsing and later when copying it to the dram). Moreover, its more compatible for handling larger pnvm tables in the future (in which payloads won't be concatenated). The main changes are: 1. Take out the concatenating of the payloads from the parsing level 2. Start using iwl_pnvm_image structure that will hold pointers to payloads that should be delivered to fw, their sizes and number. Signed-off-by:
-
Johannes Berg authored
Some of the kernel-doc links are outdated due to other changes, fix that. Signed-off-by:
-
Johannes Berg authored
Some commands are no longer used and have broken kernel-doc links, so just remove them. Signed-off-by:
-
Johannes Berg authored
Even for reserved values we shouldn't use u16, that's just error prone. Fix this to __le16. Signed-off-by:
-
Johannes Berg authored
This is clearer in kernel-doc than spelling out the prefix. It also lets us generate better tracing data. Signed-off-by:
-
Johannes Berg authored
Indicate to the firmware for each station whether or not MFP is used with this station. Note that we indicate MFP for it before authorized since we don't know yet, and that will make the firmware not handle should-be-protected management frames without being able to check them. Signed-off-by:
-
Johannes Berg authored
If there's no peer configured then there's no point in sending the command down to the firmware with an invalid peer address. Fixes: cf85123a ("wifi: iwlwifi: mvm: support enabling and disabling HW timestamping") Signed-off-by:
-
Johannes Berg authored
This warning is sometimes happening if we force a FW error while disconnecting, which is annoying but harmless. However, it's also pointless to throw a warning here, since the stack and driver state doesn't really help, so just remove that so the driver will ignore the error if any. Signed-off-by:
-
Mukesh Sisodiya authored
Remove the check for the IMR debug data size which leads to dead code. Signed-off-by:
Mukesh Sisodiya <mukesh.sisodiya@intel.com> Signed-off-by:
-
Alon Giladi authored
Add 2 new entries for Dell in PPAG approved list. Signed-off-by:
-
Avraham Stern authored
When checking if the initiator is associated to the responder, iterate over all active links. Signed-off-by:
Avraham Stern <avraham.stern@intel.com> Signed-off-by:
-
Johannes Berg authored
The 100ms shouldn't be needed, only 10ms. However after reset we should have 10ms as well for these devices. Signed-off-by:
-
Haim Dreyfuss authored
There are mainly two types of BTM (BSS Transition Management) requests, recommendations and notifications. For the first type, a response is needed otherwise, most probably the STA will be disconnected. Since we don't want to wake up the host on it, set the BTM to reject offload flag (if the device supports it) and rely on the FW to take care of it. The FW will reject the BTM request and in case the AP sends DEAUTH the FW can wake up the host to let it decide on the next steps. Signed-off-by:
Haim Dreyfuss <haim.dreyfuss@intel.com> Signed-off-by:
-
Benjamin Berg authored
DRAM buffers that are not defined in the TLVs (or are unused in the preset) would cause a log message. To avoid confusion, skip processing buffers with an invalid (i.e. uninitialized) DRAM path. This further reduces the noise of the message in cases where it is unlikely to be helpful. Also update a related debug log string to better describe what is happening. Signed-off-by:
Benjamin Berg <benjamin.berg@intel.com> Signed-off-by:
-
Golan Ben Ami authored
Add two new vendors to the PPAG approved vendor list as Google OEMs. Signed-off-by:
Golan Ben Ami <golan.ben.ami@intel.com> Signed-off-by:
-
Johannes Berg authored
Calling this IWL_RX_PHY_DATA1_EHT_B0 is just confusing, it's the RU allocation bit 0. Also then align the name for B1-B7 accordingly. Signed-off-by:
-
Johannes Berg authored
Supporting controlling the frame rate during injection, HT/VHT are supported in addition to legacy rates. Signed-off-by:
-
Alon Giladi authored
Allows vendors to use the time average sar feature. Signed-off-by:
-
Avraham Stern authored
The feature is still disabled (depends on BROKEN), but the code had a compilation error after one of the merges. Fix that. Signed-off-by:
-
Abhishek Naik authored
Add support for the MCC update response version 8. Versions 5-6 are already covered by the existing flags conversion, and 7 isn't used. The capabilities field in iwl_mcc_update_resp is 32 bits wide now, and the flags moved, so some more changes are needed. While at it, convert the flags to bool (to avoid having to deal with BIT(16) specially etc.) and use the struct_size() macro for the memory allocation. Signed-off-by:
Abhishek Naik <abhishek.naik@intel.com> Signed-off-by:
-
Alon Giladi authored
Allows the China bit in the ppag flags to turn on also when FW cmd version is 1 (if FW has the capability). Signed-off-by:
-
Johannes Berg authored
Setting the station to -EBUSY was originally done under this lock, and the comment still refers to it. But this no longer happens because that was removed when DQA was removed. Remove the leftover code as well. Signed-off-by:
-
Gregory Greenman authored
Some devices, like step A0 of GL FM device doesn't support RX STBC for VHT/HE. Add a workaround to remove it from capabilities in this case. Signed-off-by:
-
Ariel Malamud authored
Add new oem/odm pair to ppag approved vendors list when specified by platform. Signed-off-by:
Ariel Malamud <ariel.malamud@intel.com> Signed-off-by:
-
Gregory Greenman authored
In the following notifications and commands mac_id was replaced with link_id: * CANCEL_CHANNEL_SWITCH_CMD * CHANNEL_SWITCH_START_NOTIF * CHANNEL_SWITCH_ERROR_NOTIF The logic around was not changed, so only adjust handling mac/link id. Signed-off-by:
-
Emmanuel Grumbach authored
The firmware added new fields to be able to pass the link_id as the AP knows it and the esr_transition_timeout. For now, pass only the link_id since we don't have access to the esr_transition_timeout yet. Signed-off-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
-
Miri Korenblit authored
This function is MLO related, so it should iterate over all the links, and not only on deflink. Signed-off-by:
Miri Korenblit <miriam.rachel.korenblit@intel.com> Signed-off-by:
-
Haim Dreyfuss authored
In case the driver doesn't implement suspend or resume operations on the transport layer, notify the driver's upper layer. Otherwise, we might access d3_status uninitialized. Signed-off-by:
-
Avraham Stern authored
When adding a PASN station, the non MLD API was used. This results in assert when operating as MLD. Fix it to use the MLD API when operating as MLD. For now, the default link is used for the added station. Signed-off-by:
-
Johannes Berg authored
This wasn't really common anymore, so dissolve it, it has a pretty strange calling convention that's confusing. Signed-off-by:
-
Johannes Berg authored
There's no need for these to be writable, so they can be const (and static). Signed-off-by:
-
Yedidya Benshimol authored
This new version of missed beacon notification uses link_id instead of mac_id. Also add an option to use link id for retrieving vif. Signed-off-by:
Yedidya Benshimol <yedidya.ben.shimol@intel.com> Signed-off-by:
-
Golan Ben Ami authored
FW version is now frozen for 22500 devices. Don't allow newer versions in the driver. Signed-off-by:
-
- 01 Jun, 2023 2 commits
-
-
Juhee Kang authored
pktq_empty was added in commit 5b435de0 ("net: wireless: add brcm80211 drivers") but it is currently not being utilized in some areas. This commit replaces the open code with the pktq_empty() function. Signed-off-by:
Juhee Kang <claudiajkang@gmail.com> Reviewed-by:
Simon Horman <simon.horman@corigine.com> Signed-off-by:
Kalle Valo <kvalo@kernel.org> Link: https://lore.kernel.org/r/20230527114954.3281-2-claudiajkang@gmail.com
-
Juhee Kang authored
Although rtl_get_hdr was added in commit 3dad618b ("rtlwifi: Change wifi.h for rtl8192se and rtl8192de"), it is currently not being utilized in some areas. This commit replaces the open code with the rtl_get_hdr() function. Signed-off-by:
-
- 27 May, 2023 2 commits
-
-
Sascha Hauer authored
When receiving more rx packets than the kernel can handle the driver drops the packets and issues an error message. This is bad for two reasons. The logs are flooded with myriads of messages, but then time consumed for printing messages in that critical code path brings down the device. After some time of excessive rx load the driver responds with: rtw_8822cu 1-1:1.2: failed to get tx report from firmware rtw_8822cu 1-1:1.2: firmware failed to report density after scan rtw_8822cu 1-1:1.2: firmware failed to report density after scan The device stops working until being replugged. Fix this by lowering the priority to debug level and also by ratelimiting it. Fixes: a82dfd33 ("wifi: rtw88: Add common USB chip support") Signed-off-by:
Sascha Hauer <s.hauer@pengutronix.de> Reviewed-by:
Ping-Ke Shih <pkshih@realtek.com> Signed-off-by:
-
Dongliang Mu authored
The ray_config uses ray_release as its unified error handling function. However, it does not know if local->sram/rmem/amem succeeds or not. Fix this by adding sanity check on local->sram/rmem/amem in the ray_relase. Signed-off-by:
Dongliang Mu <dzm91@hust.edu.cn> Signed-off-by:
-
