for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
If STA and NAN share the same iface wlan0, Wi-Fi vendor HAL service
sends eventDisabled to NAN framework when STA setMacAddress to wlan0.
This disables NAN when STA is turned on.
Since NAN always uses its own random MAC instead of using MAC of STA,
this action is not necessary and gets NAN kicked off for no benefits.
We add a build time configuration to optionally disable this behavior.
Bug: 273426515
Test: manually test
Change-Id: Ifc71b7e8d09eac1b66b9e18c70e0e6d202683ff6
we changed to store event information in bitmap format
so that overlapping events can be handled.
Bug: 270650316
Test: startPublishRequest_1_6
Change-Id: I6f3cb8026d54dfa692bfd6eb64b24005ba663a1f
Signed-off-by: dheda.shin <dheda.shin@samsung.com>
Create a snapshot of hardware_legacy for legacy HIDL, to avoid any build breakage due to new hardware_legacy for the new AIDL. Should be removed with the HIDL when we finish the switch
Bug: 205044134
Test: build and CtsWifiTest
Change-Id: Ib1068112f6c90f2a41b68e20027d959c95798120
When device supports two AP interfaces (i.e. {AP, 2}. not a bridged case),
the AP interface name might be observed from the getPredefinedApIfaceNames.
Check if the interface name is used or not when creating a new interface.
Bug: 244387442
Test: Manual test by commands
adb shell cmd wifi start-softap tetheredAp open -b 2
adb shell cmd wifi start-lohs lohs open -b 5
Change-Id: I59b3796895ee09452a9650c4dc138ad9e143282e
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Merged-In: I5353ab1561622eae12e2dff87eb0f17b47c3773d
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
(cherry picked from commit 3ab5c90104)
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Merged-In: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
(cherry picked from commit c4ac3355a6)
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
While appending the newly received buffer to ring buffer list,
check the size of the first buffer in the ring buffer list.
If it is invalid(zero size or exceeding the max allowed size),
return failure & clear all the ring buffers.
Bug: 232477451
Test: vts test - 1.6/default/tests/runtests.sh
Test: Manual - Ran basic wifi tests & checked bugreports
Change-Id: Iaa41262f534914b971fe178053f1974248a46e70
To lower the instantaneous battery current draw of WiFi, we provide
a way to allow PowerManager to enable/disable Tx power limits.
In the legacy HAL, we call the API in Broadcom HAL to
enable/disable WiFi TX power limits.
Bug: 215193418
Test: New APIs work fine
Change-Id: I1fbe71c3380514e2eba96adc5902d2028a55e006
Allocate memory in heap for carrying radio combinations matrix
from driver/firmware to wifi HAL.
Bug: 225764376
Bug: 225762955
Test: atest WifiChipHidlTest
Change-Id: I1049f7ab9f16a35a87b7cda34ba31797fde046e3
This change added,
1. VTS test for getSupportedRadioCombinationsMatrix()
2. Skip test for getUsableChannels_1_6 if vendor doesn't
support
Bug: 220201314
Bug: 221389141
Bug: 220225758
Test: atest WifiChipHidlTest
Change-Id: I5ddbd4be68d74f1fa26584c94d5b10211261cc1a
When the HAL support dual STAs, AP should start with idx 2.
Bug: 220338166
Test: atest -c android.hardware.wifi@1.0-service-tests
Change-Id: Ic3780ea346417cf878b94e4ead8fc3eff22baf8f
This commit adds the VTS tests for the Wifi Vendor HAL 1.6
Bug: 220014236
Test: atest VtsHalWifiV1_6TargetTest
Test: atest VtsHalWifiNanV1_6TargetTest
Test: atest VtsHalWifiRttV1_6TargetTest
Change-Id: Id9f034c25029ef7a7f437185082abef67776ac8f
IWifiChip.getAvailableModes() is needed as a dependency for VTS tests.
Reinstate the API to avoid breaking old tests, ignoring the new
AP_BRIDGED concurrency type.
Bug: 219617823
Test: atest VtsHalWifiV1_0TargetTest VtsHalWifiV1_1TargetTest
VtsHalWifiV1_2TargetTest VtsHalWifiV1_3TargetTest
VtsHalWifiV1_4TargetTest VtsHalWifiV1_5TargetTest
Change-Id: Ide5b251b20f1ea56a76c2ce3b04c4e28fc29624c
Add IfaceConcurrencyType to represent Iface implementations that
have different concurrency implications for the same IfaceType, such as
Bridged AP and Single AP for IWifiApIface. Add a new IWifiChip HAL API,
getAvailableModes_1_6 to return the new concurrency type combos.
Bug: 207055799
Test: 1.6/default/tests/runtests.sh
Change-Id: Iad20a3d95d54dd8b624db912fd3153c2a3372f45
1. Add new APIs to enable/disable CHRE NAN RTT
2. Add a new API to register callback.
This callback should report events from WLAN driver for CHRE.
Test: New APIs work fine
Bug: 206614765
Change-Id: I8c8ab002064a9556be2e7d3972703bb3255a3a41
Added API to get the supported radio combinations
of the chip. This is mainly to check if the chip is
capable of multi band simultaneous operation.
For Example in case of a chip which has two radios, where one radio is
capable of 2.4GHz 2X2 only and another radio which is capable of either
5GHz or 6GHz 2X2, number of possible radio combinations in this case
are 5 and possible combinations are:
{{{2G 2X2}}, //Standalone 2G
{{5G 2X2}}, //Standalone 5G
{{6G 2X2}}, //Standalone 6G
{{2G 2X2}, {5G 2X2}}, //2G+5G DBS
{{2G 2X2}, {6G 2X2}}} //2G+6G DBS
Bug: 208877624
Test: vts test
Change-Id: I4c90f80002ca138133a575bca80dfdef2a593ab2
We want to fill in more fields in our conversion method, so we
let the logic proceed to all of them.
Test: TreeHugger
Bug: 203220137
Change-Id: Ia7a9c978ec778eebd17b9ce74f43cc320e92b971
If set, it indicates that the device is operating
in an indoor environment. When driver receives this
indication, it can safely enable WFD GO operation
on indoor channels.
Bug: 207671411
Test: Manual basic wifi tests
Change-Id: I4cc4c22444f0796c280220534d43c4ae8cae0899
This commit adds the implementation for the HAL API changes
to enable 11be support.
Bug: 198746544
Test: Build Succeeds
Test: VTS test
Change-Id: I2d1f296856698951c2c0111200e7c7bf661da132
This commit adds the required changes for the support of
802.11be (WiFi-7) support to the wifi vendor hal API.
Bug: 198746544
Test: Build Succeeds
Test: VTS test
Change-Id: I1f631aaa247ce4240dd398230b57c7edae55c141
