in the WifiChip constructor.
gTest suite currently cannot mock the legacy HAL
call for getSupportedIfaceConcurrencyMatrix.
If we set using_dynamic_iface_combination_ to true
in the unit tests, we can avoid making this call.
Bug: 271914366
Test: ./runtests.sh # gTest
Test: atest VtsHalWifiChipTargetTest # VTS
Change-Id: Ic43daab6ff5fdc5f78af614ad775f436fbbe8726
APF is support is mandatory since VSR 14. Before that, the APF
requirement is optional. Vendors can opted into upgrading their
HAL to AIDL, so the VTS need to check if vendor API level on the device
and only mandate the APF capability check if the vendor API level is
greater or equal to 14.
Bug: 283181837
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I21513187d4ca99d721d0e9dc5e243adad77ab8c6
Update the aidl API documentation to describe how setDtimMultiplier API
is supposed to work, i.e. we can call this API to set a maximum DTIM
multiplier value to use in driver, any larger value must not be accepted
and meanwhile it allows to set a specific multiplier by OEMs. Try to
make the description clear and avoid the ambiguity.
Bug: 266256943
Test: m
Change-Id: Ic7d2284a25e32d1b0752cf2bc832c069f646fcea
dump method is called.
This should prevent a race condition
between stop() and dump().
stop() already acquires the global lock
when it calls validateAndCall().
Bug: 274641043
Test: adb shell dumpsys wifi # validates dump()
Change-Id: Ie2df0861308954cd2e399c9604d4ae0dcddf95fb
VTS test for IWifiChip#getFeatureSet.
Some implementations of the legacy HAL,
such as Goldfish, do not have any
supported features.
Bug: 273886122
Test: atest VtsHalWifiChipTargetTest
(tested on Cuttlefish)
Change-Id: I3ca22187cab0e77d36a28908e57ff4970535e4ae
Since Android U, VSR 5.3.12 mentioned the Android Packet Filtering must
be supported by CHIPSETs and DEVICEs launching on Android 14 or higher.
This VTS was added to check if APF is supported properly.
Given the limitation of the VTS testing environment, the first version
of the test case only checks: if the APF is supported by WiFi chips with
version 4 and more than 1024 bytes of usable memory.
Bug: 259309511
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I3ee2a980a4440db232738a23c1633aaff3562d95
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
Use a new structure to passdown:
- AFC information queried based on frequency
- AFC information queried based on channel number
- expiration time
This change is per chip vendor request. Based on AFC server support,
either frequency based information or channel based information may be
empty. If both are empty, then it indicate the driver should not allow
any standard power transmission on 6Ghz.
Bug: 262791660
Test: compile
Test: Manually verified information is passed down with local framework
change
Change-Id: Id1d014a6113f6863b98ef8239a5a52d3863aa758
explain why the linter is disabled.
If the linter were enabled, we would run into a
build failure because fixed-size arrays are not
supported on SDK Level < 33. The interface indicates
min_sdk_version 30 due to mainline requirements,
but the interface will only be accessed by devices
running Android U.
Bug: 267819850
Test: m
Change-Id: Ifed2223d1c5f4bf46329ed72fa622b730e99cde1
in IWifiChip and IWifiStaIface.
Main purpose is to distinguish between
the 2 capability methods in IWifiChip:
- getCapabilities (renamed here)
- getWifiChipCapabilities
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest \
VtsHalWifiStaIfaceTargetTest
Change-Id: I03c15d652d02aef99b219c2d630b69acb4d9e43c
Re-assign the value according to the Wifi Aware R4.0 section 9.5.21.1
Also correct several comments.
Bug: 269440402
Test: build
Change-Id: Ib3dd6365b2a28f871ec6ae3775ee8b9e9481475f
types in the Vendor HAL interface.
Specs should be included in the
relevant places.
Bug: 267819850
Test: m
Change-Id: I1f213774ebf5dc297225a5cabb757d2956d67bf4
* changes:
Update usages of WifiRadioCombinationMatrix in the Vendor HAL service.
Remove the WifiRadioCombinationsMatrix type from the Vendor HAL interface.
Vendor HAL interface.
We can return a list of WifiRadioCombinations instead.
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest
Change-Id: I0f57df6262d36917dfd8cc3e27d6781e9b7c8dbf
XML parsing logic.
Fixes a minor memory leak that results from
not freeing that buffer.
Bug: 269520490
Test: Manual test
1. Create several XML files under
/vendor/etc/wifi/vendor_hals
2. Modify the codepath to run the
initVendorHalsDescriptorList method
(does not run by default on Pixel).
3. Check that the XML parsing logic is
working as intended.
Change-Id: I42944169b70c759998d94e8523d2aa55d0366ffd
Interface combinations in legacy-hal is predefined with
'WIFI_HAL_INTERFACE_COMBINATIONS' build flag. This change
allows the WiFi HAL to request all the possible interface
concurrency combinations via vendor HAL API,
wifi_get_supported_iface_concurrency_matrix(). Thus build time
dependency can be removed by querying the combination at runtime.
Bug: 249351396
Change-Id: I3bc85ac013490949aab71a00f60028bf5daee68c
Merged-In: I3bc85ac013490949aab71a00f60028bf5daee68c
Test: Build successfully
Signed-off-by: Purushottam Kushwaha <quic_pkushwah@quicinc.com>
(cherry picked from commit f68b9a2709)
