ath10k: Add support to provide higher range mem chunks in wmi init command
authorSurabhi Vishnoi <svishnoi@codeaurora.org>
Mon, 25 Feb 2019 12:48:46 +0000 (18:18 +0530)
committerKalle Valo <kvalo@codeaurora.org>
Mon, 23 Sep 2019 07:53:30 +0000 (10:53 +0300)
commit40f4ef5e92326ab127bdeb6f024855c8c91de608
tree90e1778b2d040c810922d4b4301a5a157bd7a208
parentc0e33fe6fb0fe392ebfab14127d210679c413192
ath10k: Add support to provide higher range mem chunks in wmi init command

With the current implementation of wmi init command,
there is no provision for the host driver to provide mem
chunks addresses with more than 32-bit, to the firmware.
WCN3990 is a 35-bit target and can accept mem chunks addresses
which are above 32-bit.

If firmware supports address range more than 32 bit, it
advertises the support by setting the WMI_SERVICE_EXTEND_ADDRESS
service. Based on this service fill the upper bits of paddr while
providing the mem chunks in the wmi init command.

Tested HW: WCN3990
Tested FW: WLAN.HL.3.1-00784-QCAHLSWMTPLZ-1

Signed-off-by: Surabhi Vishnoi <svishnoi@codeaurora.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
drivers/net/wireless/ath/ath10k/wmi-tlv.c
drivers/net/wireless/ath/ath10k/wmi-tlv.h
drivers/net/wireless/ath/ath10k/wmi.h