diff options
| author | Miri Korenblit <miriam.rachel.korenblit@intel.com> | 2024-01-31 10:24:46 +0200 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2024-02-02 14:15:15 +0100 |
| commit | 3bc67e7c18cd69e88b801336cfe2a4dc7b4981a4 (patch) | |
| tree | 0b91e0b6485f9c6afa415206264aa6730f70827c /drivers/acpi | |
| parent | ad5a85d8fdd346ecc34217e3bd713bf0b519912d (diff) | |
| download | linux-stable-3bc67e7c18cd69e88b801336cfe2a4dc7b4981a4.tar.gz linux-stable-3bc67e7c18cd69e88b801336cfe2a4dc7b4981a4.tar.bz2 linux-stable-3bc67e7c18cd69e88b801336cfe2a4dc7b4981a4.zip | |
wifi: iwlwifi: separate TAS 'read-from-BIOS' and 'send-to-FW' flows
Currently the TAS 'read-from-BIOS' flow receives the command struct
and the version of it as read from FW TLVs, and fills the command
accordingly.
This seems wrong, we should have the 'read-from-BIOS' flow
(iwl_acpi_get_tas in iwlwifi) reading/parsing/validating the table from
BIOS, and the 'send-to-FW' flow (iwl_mvm_tas_init) doing
all the FW versioning checks and cmd filling.
Move the cmd filling to the 'send-to-fw' flow.
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Reviewed-by: Gregory Greenman <gregory.greenman@intel.com>
Link: https://msgid.link/20240131091413.24df27772a71.I57b702af4feb3f38dc21d52593c25de4b1999e4b@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers/acpi')
0 files changed, 0 insertions, 0 deletions