Enhance the API to support multiple WIFI chips.
Each WIFI chip is represented by a separate and independent
vendor HAL library providing its own function table
(wifi_hal_fn structure).
New functions added to the function table in order to
better support multiple WIFI chips:
1. In the existing hardware/interfaces/wifi implementation,
WIFI chip modes and concurrency combinations are hard-coded.
Since each WIFI chip can have its own concurrency
combinations, it is no longer possible to hard-code the
modes/combinations.
Add new function wifi_get_chip_modes for reporting
chip modes/concurrency combinations. For backward compatibility,
if the vendor HAL does not implement this function,
the previous hard-coded chip modes and concurrency combinations
will be used.
2. In the existing hardware/interfaces/wifi implementation,
when creating a new interface, it will use a fixed name
such as wlan0 or wlan1. This does not extend well to
multiple WIFI chips, as different WIFI chips may want
to use their own interface names, or the suggested interface
name may have been pre-created by another chip.
In order to better support interface creation on multiple
WIFI chips, add a function wifi_get_supported_interface_name
that allows the vendor HAL to specify its own interface
name for upcoming interface creation. If the vendor HAL returns
an interface name, it should be passed to
wifi_virtual_interface_create to create the interface
with the provided name.
3. In the existing hardware/interfaces/wifi implementation,
wifi_initialize is only called when creating the first
interface (typically when enabling WIFI). However some
chips may want to perform early initialization and provide
some functionality while WIFI is still disabled. One example
is reporting chip-global capabilities that may affect
the UI even before WIFI is enabled.
In order to support this, add a new function
wifi_early_initialize which will perform early initialization.
The function should be called as soon as possible after
loading the vendor HAL, and if it returns a failure, the vendor
HAL should not be considered usable and no WIFI chip should
be created based on it.
4. In some cases it is needed to query chip features before
creating any interfaces. For example, for trying to start
a SoftAP on the 60GHz band, it is needed to detect a chip
which supports the 60GHz band, and only if such chip was detected,
then an AP interface can be created on it.
The wifi_get_supported_feature_set function only works on
a created interface so it is not suitable for this scenario.
To support such scenarios, add a new function
wifi_get_chip_feature_set which returns a set of chip-global
features which are independent of any created interface.
Bug: 146922967
Test: atest VtsHalWifiV1_0TargetTest VtsHalWifiNanV1_0TargetTest VtsHalWifiApV1_0TargetTest \
VtsHalWifiV1_1TargetTest \
VtsHalWifiV1_2TargetTest VtsHalWifiNanV1_2TargetTest \
VtsHalWifiV1_3TargetTest \
VtsHalWifiApV1_4TargetTest VtsHalWifiNanV1_4TargetTest VtsHalWifiRttV1_4TargetTest
Change-Id: If0b4934002c5687024c9fc2e65e15c466f94acd2
This commit adds a method to set the handler for wifi subsystem
restart callback.
Bug: 159367026
Test: force a firmware restart and make sure Wifi is recovered.
Change-Id: Id125b85a697a0cdd5cf2677abb0006c85053fd43
Repositories containing third-party code need a METADATA and a
license_type. Repositories containing only first-party code no longer
need a MODULE_LICENSE_* file.
Bug: 68860345
Bug: 69058154
Bug: 151953481
Test: no code changes
Change-Id: I95a3e4f05aab09276311fcc6cc4363eebc4f77f8
This commit adds the needed enum and methods to handle the mapping
of DSCP into wifi access categories.
Bug: 141500691
Bug: 141550272
Test: Manual
Change-Id: If532a6dc34f4a2c61fc4601cb1b83d2fec053ea5
global handle instead of interface handle as thermal
mitigation is not interface specific.
Bug: 112471991
Test: atest FrameworksWifiTests
Change-Id: I40b8d85156b7a4561a4ef6db9e4655824c10b5ba
It was decided to base device capability for support of 6GHz band
on overlay configs rather than HAL capability bitmask.
Hence, this commit removes the 6GHz feature flag.
Bug: 145936758
Bug: 139354972
Test: Manual
Change-Id: I0c72161a31452bd0fab226f9f92f0aa859d3f5e4
This commit forces the features and feature_set to be 64 bit
for better portability.
Bug: 144576287
Test: Builds passes successfully
Change-Id: I93c74d9f1802520c9bd0aa7f8f15cec4e30ce2ba
This commit implements support of checking whether device supports 6GHz band.
To accomodate the new feature as well as any future features, feature_set type
was changed from int (32 bits) to long (64 bits).
Bug: 139354972
Test: Manual
Change-Id: If002d8efb854d50af314794926fbdfdc4fb08a5e
Bug: 143284916
Test: ./block_suspend; dumpsys suspend_control shows that wakelocks are
created as expected
Change-Id: Ifacb4f476632e0c36f7ec4f59164f91e89faf1f1
This CL makes modidfication to support Wifi 802.11ax to RTT procedures.
This includes adding support for the 11ax preamble
Bug: 139354972
Test: Manual
Change-Id: I2aca64edcb4bc2ee267db4e4011da246c540a4b8
am: 9d1dd12c34 -s ours
am skip reason: change_id Ife2ba92f4c3c2bad08db288db184ba25bf52e4ad with SHA1 1fd1efbd2e is in history
Change-Id: I9b2979bcdbbfbc78d5ac2da34b5014bb311ed566
am: fc94ff1e86 -s ours
am skip reason: change_id Ife2ba92f4c3c2bad08db288db184ba25bf52e4ad with SHA1 1fd1efbd2e is in history
Change-Id: I27db65e7d4587d8a9e6497d7c6eb368fa7425b08
am: d784d83f2b -s ours
am skip reason: change_id Ife2ba92f4c3c2bad08db288db184ba25bf52e4ad with SHA1 1fd1efbd2e is in history
Change-Id: I70de5e1edfa94765755a99529ae32bfc01467215
am: 0ed99eca92 -s ours
am skip reason: change_id Ife2ba92f4c3c2bad08db288db184ba25bf52e4ad with SHA1 1fd1efbd2e is in history
Change-Id: I48408dc078cd0c7e0cd2451a9a3739bcbe9db0f2
