Age | Commit message (Collapse) | Author |
|
tm-qpr3-release
Change-Id: I6334561592145e0a66f07b165f4c0c4e3a98dd90
|
|
Framework invokes wifi_set_voip_mode (hal api) to configure wifi calling (wfc)
state in underlying wlan driver/firmware. Later driver/firmware uses this
information to optimize power, rate adaption etc.
Bug: 251265470
Test: Regression Test
Change-Id: I0858147d932797030e51addb29649e1b6bc67780
CRs:Fixed: 3346100
|
|
This commit updates qca-vendor_copy.h to latest qca-vendor.h as
specified on Nov 25, 2022
https://w1.fi/cgit/hostap/tree/src/common/qca-vendor.h.
Bug: 251265470
Test: Regression Test
Change-Id: I08cecdc58a356471c2d3213375e348db984b7b44
CRs-Fixed: 3346067
|
|
Use another flag to identify which subfolder we
want to include.
Bug: 246974867
Test: Build Pass
Change-Id: If223d5cde7b6248c71094f2f27c1bbdd96eb024c
|
|
|
|
Bug: 246878657
Test: N/A
Change-Id: Ibbee0efc82a20becce19554819ba762727d3c2b8
|
|
Setting the return value to corresponding error before returning
from the APIs.
Bug: 241058906
Test: VTS test
CRs-Fixed: 3264767
Change-Id: Id77b3d64459f4957b6921be8ad8ad4d60f32a4cb
|
|
The patch checks the SAR version from firmware
and adds commands/values to support SAR V2.
Bug: 238570847
Test: haltuil -sar
Change-Id: I531e7f7f685373cfd5566ac6fd3f7fb3540e8219
CRs-Fixed: 3278406
|
|
This commit updates qca-vendor_copy.h to latest qca-vendor.h as
specified on Aug 29, 2022 at
https://w1.fi/cgit/hostap/tree/src/common/qca-vendor.h.
Bug: 238570847
Test: haltuil -sar
Change-Id: I35d54a1932e2d677c62f8d24affbe320624700c1
CRs-Fixed: 3278400
|
|
|
|
VTS test cases SelectTxPowerScenario_1_2_voiceCall and
SelectTxPowerScenario use legacy power scenario
WIFI_POWER_SCENARIO_VOICE_CALL to test the wifihal API.
Bug: 242126285
Test: WifiChipHidlTest
Change-Id: Ief202f3cc3caaf79b8fd12306179789fe30e82ee
|
|
CLs list:
wifi: Fix for compiling issue
WifiHal: Add wifi_get_usable_channels into func pointers table
wpa_supplicant_lib: Avoid double free when nl msg send fail
wpa_supplicant_lib: peer flush tid queue command
wifi_hal: fix potential memory leak
wifi_hal: fix static analysis issues
wpa_supplicant_lib_8: Do not print all parameters in TWT setup failure
Subject: Implement standalone build files
Bug: 241212055
Bug: 241724304
Test: Regression Test
Change-Id: I6e10437ff741d3e4805da4cd3458d1be1c89c8fe
|
|
This commit maps power scenarios to the SAR tables for wcn6740
Bug: 241036959
Test: halutil -sar
Change-Id: Iedc0e8507a5594060173ad9958f5880648ac0bbf
|
|
The original wifi_hal for legacy projects is so old that
we met lots of issues in wcn6740. Create another wifi_hal
for wcn6740 that uses latest code and keep using the old
wifi_hal code for the legacy projects.
Bug: 213413875
Test: Regression Test
Change-Id: Ibb3c748254c3e5472b3218bda34c88f79d343dae
|
|
Due to invalid length in firmware message, the
ring buffer overflows.
Added check for length w.r.t msg headers and
returned error in case of invalid length.
Bug: 231524566
Test: Regression Test
CRs-Fixed: 2975064
Change-Id: I830a111fe2e58e1aa4039f2d9d996ba28632a9e5
|
|
Due to invalid length in firmware message, the
ring buffer overflows.
Added check for length and returned error in
case of invalid length.
Bug: 231524566
Test: Regression Test
Change-Id: I0daeed2335f7fb7661f44bb119776979d51b906d
CRs-Fixed: 2837711
|
|
A Wi-Fi Turn OFF sets clean_up variable, expecting the Wi-Fi
HAL module to exit from its event / socket processing.
However, there were some instances , where Wi-FI HAL ended to
be in a busy while loop though clean_up is set and further
resulted to an improper Wi-Fi OFF. Thereby the further Wi-Fi ON's
have failed till a restart. Address such instances by having
the while loops also check for clean_up before continuing further.
Bug: 231524566
Test: Regression Test
Change-Id: I6af24cc38894d3ba98721acce2b147e4158134a3
CRs-Fixed: 2563190
|
|
Fix issue w.r.t funtion pointer handling so that framework/test
utils can call using funtion pointer table.
Bug: 231866104
Test: halutil -usable_ch
Change-Id: I2d0879d8bc50c8b274d2464468eb73aa937bd929
|
|
Add support to request list of usable channels for the requested
bands, modes and concurrency constraints from the driver.
Bug: 231866104
Test: halutil -usable_ch
Change-Id: I71d7c92fbaefd3f9086972e5981ef76eed90e927
CRs-Fixed: 2971389
|
|
Map wifi restriction iface bit mask to nl iface bit mask while
sending wifi coex unsafe channels to driver.
Bug: 232681785
Test: halutil -coex
CRs-Fixed: 3117432
Change-Id: I9015bcc0a0780fc97c90669eda44649b12bab6bd
|
|
If power cap dbm received by hal is WIFI_COEX_NO_POWER_CAP (0x7FFFFFF)
then don't send it to driver so that driver will not apply any
power cap dbm on the specified channel and keep operating with
currently applied power cap based on regulatory constraints.
Bug: 232681785
Test: halutil -coex
CRs-Fixed: 3112181
Change-Id: I95f20ec3557097ea58d1520f3a02bfddf87e5033
|
|
Support to send coex unsafe channels using vendor subcmd:
QCA_NL80211_VENDOR_SUBCMD_AVOID_FREQUENCY_EXT to restrict the usage of
unsafe channels/frequencies on wifi interfaces.
Bug: 232681785
Test: halutil -coex
Change-Id: I6e6d67d51cd3a1a44b7ede68b2fc819352fa7c9d
CRs-Fixed: 3077786
|
|
This commit updates qca-vendor_copy.h to latest qca-vendor.h as
specified on Dec 23, 2021 at
https://w1.fi/cgit/hostap/tree/src/common/qca-vendor.h.
Bug: 232681785
Test: halutil -coex
Change-Id: I7648c4888d5677a32f59b58984b16cf8c16929fe
CRs-Fixed: 3108043
|
|
NDP_CONFIG_SECURITY is deprecated, use NCS_SK_TYPE/PMK/SCID
instead. Also, recent kernels have the strict rules to specify
the policy for each attribute of NL80211_CMD_VENDOR subcmd's.
Since, this attribute is not used by all variants of host
driver's, it is quite safer to rather remove this.
Bug: 234310602
Test: DataPathTest
Change-Id: Iba515093e125219fb865d05ffcd98ebfca0a0c53
CRs-fixed: 2762504
|
|
Send proper return value in diag_msg_handler, so that
caller would take appropriate action based on return type
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
CRs-Fixed: 3167545
Change-Id: Icbcefb1e45b2d40b0bacc3eb1f849737d2cb0a0f
|
|
Adding void keyword in cld80211_init() argument so as to
avoid type mismatch issue and a resultant crash when
this lib is used by any C++ code.
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
CRs-Fixed: 2545658
Change-Id: Ic4e22316caf04fd41d6e3ed5327d225ef1ae04d4
|
|
CLD80211_ATTR_CMD and CLD80211_ATTR_CMD_TAG_DATA are
new attributes that are allowed for cld80211 family msgs
CLD80211_ATTR_CMD has cld80211 vendor sub command in it,
while CLD80211_ATTR_CMD_TAG_DATA has nested sub attributes
of specified sub command
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
CRs-Fixed: 2637778
Change-Id: I17d820d9e97d316b1c02091e56d669338ec01c3d
|
|
WLAN_NL_MSG_OEM uses CLD80211_ATTR_DATA for storing
binary data. With added support to cld80211 vendor subcmds
wifi hal will receive new attributes in which the data is
packed as nested sub attributes. Wifihal will forward the
new responses to its clients
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
CRs-Fixed: 2637824
Change-Id: If4501d5e873622c254fb84a0d2949568d366f3da
|
|
Post kernel commit ab10c22bc3b2024f0c9eafa463899a071eac8d97,
kernel splits wiphy data in multiple parts. Hence to get
complete wiphy data, user needs to set the split wiphy
attribute. currently wifihal does not set this attribute
hence kernel sends only basic data to wifihal.
As a part of fix, set split wiphy attribute so wifihal
get complete wiphy data.
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
Change-Id: Ie6e70750b73b5fd2b6f3bf4cc0de48966b659a9b
CRs-Fixed: 2954709
|
|
Add support for QCA_NL80211_VENDOR_SUBCMD_NAN_EXT command when issuing
NAN commands. With this NAN extension command, attributes such
as primary channel, secondary channel can be specified along with
other NAN vendor request parameters in NAN commands.
Bug: 220992475
Test: VtsHalWifiNan/VtsHalWifiRtt
Change-Id: I0705c4024c9f74c16454a1da9ffb88ca68c58d88
CRs-fixed: 2313579
|
|
QCA_WLAN_VENDOR_ATTR_CONFIG_LATENCY_LEVEL is supposed to carry u16
value in the request. Modify their type accordingly.
Bug: 222044962
Test: VTS tests
Change-Id: I7f5da5be31845ce214ef283279ec74d41474433b
|
|
1d4632bd80 -s ours am: 7d5267f297 -s ours
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I77d8753a63b44144d5a0190a6ac49a30d20240d0
|
|
-s ours am: 0ff3a30031 -s ours
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I18cc18fffab86c833dc714c1db5eadbd88af941c
|
|
1d4632bd80 -s ours
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I4855ed2587649e6bfe84947fcb351cb2ee787225
|
|
-s ours
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I21ef49da3911398097c44be571da42d6b77a2f39
|
|
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I797dd77c4d70d5e232c72402a238b0dfa17f59a9
|
|
am skip reason: Merged-In I6b94d0ec89496c251349a200fcd1c291ea6ad87f with SHA-1 5f76d7b968 is already in history
Original change: https://android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/2013327
Change-Id: I6b568b8911c27559893956424543a066a86bf42b
|
|
|
|
Bug: 222710654
Merged-In: I6b94d0ec89496c251349a200fcd1c291ea6ad87f
Change-Id: I178c8c41c1878ad8427dbc161b400c525ab6e702
|
|
Implement wifi_set_dtim_config API to send DTIM
configuration to driver/firmware.
Bug: 215653020
Test: DTIM configuration supported
Change-Id: I553447181c69e90d0f69134792ac9fc7c7ad7d8e
CRs-Fixed: 3118522
|
|
5f76d7b968 -s ours am: 50131ebfc4 -s ours
am skip reason: Merged-In I287d19d97970523b0d695e7dcbd606a49fa23f7c with SHA-1 ef79d4cb49 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/16845149
Change-Id: I139631265715f6bce05b7d7113bd2ae2842405b2
|
|
5f76d7b968 -s ours
am skip reason: Merged-In I287d19d97970523b0d695e7dcbd606a49fa23f7c with SHA-1 ef79d4cb49 is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/16845149
Change-Id: Ib4dae1eb3aa4981f5ddab7c58c8164485ef03390
|
|
Bug: 214455710
Merged-In: I287d19d97970523b0d695e7dcbd606a49fa23f7c
Change-Id: I6b94d0ec89496c251349a200fcd1c291ea6ad87f
|
|
Increase MAX allowed number of whitelist SSIDs count to 8
Bug: 215795211
Test: Get roaming capabilities correctly on all related projects
Change-Id: I6ea8ff4f1623607b0180b243e230675f9ff7935c
CRs-Fixed: 2900468
|
|
Per WiFi HAL design, roaming feature should have nothing to do with
Gscan, but in current impl, these two are tightly coupled:
- Roaming capabilities is queried by vendor cmd GSCAN_GET_CAPABILITY.
- Set blacklist bssid returns error if Gscan not supported
So de-couple roaming feature with Gscan by:
- Set default roaming capabilities if Gscan not supported.
- Set blacklist bssid returns error if Roaming not supported.
Bug: 215795211
Test: Get roaming capabilities correctly on all related projects
CRs-Fixed: 2405118
Change-Id: I9f96546538dd4d07a1f930f107c0024436907927
|
|
Host driver does not use the attributes DRIVER_FW_LOCAL_WAKE_CNT_SZ
and CMD_EVENT_WAKE_CNT_SZ.
Also, driver unconditionally sets all of the LEGACY attributes to 0
in the response since they are not supported.
Hence, removing the relevant code.
Bug: 215804926
Test: Device and legacy pixels can get wake reason stats successfully
Change-Id: I63050a5c0645a32e4740342d3e84bd907394c2d7
CRs-Fixed: 2783515
|
|
Overflow may happen if request id is greater than max range of u8
type when trying to request driver/firmware version. Fix the issue by
not allowing request Id cross max range of u8 when trying to put with u8 api.
Bug: 213108298
Test: Device can get drirver version and firmware version
CRs-Fixed: 3107212
Change-Id: Ia42d9280d81f7019af025c4d5e7d4cb2e5ed916e
|
|
QCA_WLAN_VENDOR_ATTR_WIFI_INFO_DRIVER_VERSION and
QCA_WLAN_VENDOR_ATTR_WIFI_INFO_FIRMWARE_VERSION are supposed to carry u8
value in the request. Modify their type accordingly.
Bug: 213108298
Test: Device can get drirver version and firmware version
Change-Id: I78e4c1feeca3fcc3649299c5ad3a6972bf9bd60f
CRs-Fixed: 2755700
|
|
Bug: 213465444
Test: N/A
Change-Id: Ie59c7174c7992655bf9c3925b2b07045d06df3d6
|
|
Original change: https://googleplex-android-review.googlesource.com/c/platform/hardware/qcom/wlan/+/16191795
Change-Id: I79d7182688be17cb6ff2a4a4b137bca72526a82a
|