diff options
| author | Lukas Wunner <lukas@wunner.de> | 2023-01-27 15:02:00 +0100 |
|---|---|---|
| committer | Kalle Valo <kvalo@kernel.org> | 2023-02-13 18:51:35 +0200 |
| commit | bba047f15851c8b053221f1b276eb7682d59f755 (patch) | |
| tree | ecaea73a05ad2cb00dcf261f37570539dcfb40e0 /lib/ashldi3.c | |
| parent | 36dd7a4c6226133b0b7aa92b8e604e688d958d0c (diff) | |
| download | linux-stable-bba047f15851c8b053221f1b276eb7682d59f755.tar.gz linux-stable-bba047f15851c8b053221f1b276eb7682d59f755.tar.bz2 linux-stable-bba047f15851c8b053221f1b276eb7682d59f755.zip | |
wifi: mwifiex: Support SD8978 chipset
The Marvell SD8978 (aka NXP IW416) uses identical registers as SD8987,
so reuse the existing mwifiex_reg_sd8987 definition.
Note that mwifiex_reg_sd8977 and mwifiex_reg_sd8997 are likewise
identical, save for the fw_dump_ctrl register: They define it as 0xf0
whereas mwifiex_reg_sd8987 defines it as 0xf9. I've verified that
0xf9 is the correct value on SD8978. NXP's out-of-tree driver uses
0xf9 for all of them, so there's a chance that 0xf0 is not correct
in the mwifiex_reg_sd8977 and mwifiex_reg_sd8997 definitions. I cannot
test that for lack of hardware, hence am leaving it as is.
NXP has only released a firmware which runs Bluetooth over UART.
Perhaps Bluetooth over SDIO is unsupported by this chipset.
Consequently, only an "sdiouart" firmware image is referenced, not an
alternative "sdsd" image.
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Signed-off-by: Kalle Valo <kvalo@kernel.org>
Link: https://lore.kernel.org/r/536b4f17a72ca460ad1b07045757043fb0778988.1674827105.git.lukas@wunner.de
Diffstat (limited to 'lib/ashldi3.c')
0 files changed, 0 insertions, 0 deletions