summaryrefslogtreecommitdiff
path: root/wifi/1.1/default
AgeCommit message (Collapse)Author
2017-09-14[WIFI][TREBLE] Uprev Wi-Fi HAL 1.2Etan Cohen
In preparation for new feature development - uprev the Wi-Fi Treble HAL revision from 1.1 to 1.2. This CL does not contain any functional changes to the HAL itself. Only updating the revision. Bug: 65647646 Test: builds and Wi-Fi runs Change-Id: I8e80e866562a508bf481104a3dbcf2bd8f8015b4
2017-09-12Add 'vendor.' prefix to a vendor HAL service nameJaekyun Seok
To prevent property name collisions between properties of system and vendor, 'vendor.' prefix must be added to a vendor HAL service name. You can see the details in http://go/treble-sysprop-compatibility. Test: succeeded building and tested on a walleye device Bug: 36796459 Change-Id: I4e8fbee791ec917a8f627a1366f4d44ec7e6febc
2017-08-28wifi(implementation): Remove unnecessary local variableRoshan Pius
Bug: 65058323 Test: Compiles Change-Id: Ib268234837f5b381572c8038e7900a145fb32249
2017-08-28wifi(implementation): Make WifiLegacyHal.stop() blockingRoshan Pius
IWifi::stop() is currently non-blocking which makes it hard for the client to determing when the stop is fully complete. This for example causes wificond to disable the wlan0 interface while the legacy HAL stop is being processed. So, add a timed wait to let the legacy HAL complete processing of the stop before we unblock the IWifi::stop() HIDL call. Bug: 64611487 Test: Manual tests by wifi state toggling and verifying the order of events in logs: 08-15 19:17:53.302 796 796 I android.hardware.wifi@1.0-service: Stopping legacy HAL 08-15 19:17:53.302 796 796 I WifiHAL : Sent msg on exit sock to unblock poll() 08-15 19:17:53.302 796 4793 E CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Could not find group host_logs, errno: 0 id: -2 08-15 19:17:53.302 796 4793 E CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Could not find group fw_logs, errno: 0 id: -2 08-15 19:17:53.302 796 4793 E CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Could not find group per_pkt_stats, errno: 0 id: -2 08-15 19:17:53.302 796 4793 E CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Could not find group diag_events, errno: 0 id: -2 08-15 19:17:53.302 796 4793 E CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Could not find group fatal_events, errno: 0 id: -2 08-15 19:17:53.302 796 4793 I CLD80211: /vendor/bin/hw/android.hardware.wifi@1.0-service: Sent msg on exit sock to unblock poll() 08-15 19:17:53.302 796 4793 I android.hardware.wifi@1.0-service: Legacy HAL stop complete callback received 08-15 19:17:53.304 802 838 D CHRE : @ 151.328: [Platform] wifi: has 0, enabled 0 08-15 19:17:53.321 796 4793 I android.hardware.wifi@1.0-service: Legacy HAL event loop terminated 08-15 19:17:53.321 796 796 I android.hardware.wifi@1.0-service: Legacy HAL stop complete 08-15 19:17:53.522 796 796 I android.hardware.wifi@1.0-service: Wifi HAL stopped Test: Will send for regression tests. Change-Id: I394c11724e9459a4b9a6b970e2bcb4e0ad65fefc
2017-08-15wifi(implementation): Reduce logging severityRoshan Pius
IE elements should not be present in the batched scan results, but it being there doesn't cause any problems. The IE elements will be ignored when we send it over the HIDL interface, so reduce the log level to prevent log spamming. Bug: 64448186 Test: None Change-Id: Ia0d0312a113c907bb0992bb8f41e734fe9d05114
2017-08-08wifi(vts): Ignore IWifi.stop() returning ERROR_NOT_AVAILABLERoshan Pius
am: 8c216524a3 Change-Id: I1bf9be99d4e673209edb893040483bf772ee3ca0
2017-08-08wifi(vts): Ignore IWifi.stop() returning ERROR_NOT_AVAILABLERoshan Pius
When IWifi.stop() is invoked back to back (happens in the ConfigureChip vts test), the HAL would return ERROR_NOT_AVAILABLE if the previous stop is still being processed. This is not an error that needs to fail the test, but a legitimate status for stop. We have a retry mechanism to handle this in both the VTS test and framework for the case where IWifi.start() is invoked while the previous stop is being processed. While there, corrected a few log messages emitted by the HAL to debug such startup/stop issues better. Bug: 63971806 Test: `vts-tradefed run commandAndExit vts --skip-all-system-status-check --primary-abi-only --skip-preconditions --module VtsHalWifiV1_0Target -l INFO` Change-Id: I5e3470ac97541a6ea10aceec9b737e5d03ed5206
2017-07-28Merge "wifi(hidl): Modify the SAR power levels interface" into oc-dr1-devRoshan Pius
am: dda74bcf77 Change-Id: I504fe9096b855c6270c50c1e46b4e5ee26b9ea67
2017-07-27wifi(hidl): Modify the SAR power levels interfaceRoshan Pius
Modifying the interface used to lower the tx power level for meeting SAR requirements based on recommendation from the nexus hardware team. The previous interface passed in a single power value in dBm for meeting SAR requirements. However, the SAR requirements are more complex than that. Based on the connection mode (802.11 a,b,g,n,ac) and the number of streams that are active (MIMO), the SAR power levels are very different. Using the previous interface would mean that we will have to use the lowest power level among all the connection modes to meet the SAR requirements. This would however result in us lowering the power much more than needed (~2 dBm) for many connection modes. Instead, we're switching to a more generic interface where the framework informs the wifi chip that we're entering a special tx power mode scenario (today, there is only 1 for voice call). The chip can then lookup the extensive table of power levels for different connection modes which are pre-populated by the OEM's in the BDF file to set the power level (depending on the scenario framework sends and the active connection mode). Bug: 62437848 Test: Manual tests Change-Id: I5ee3f0d2c130958dbeb352e3b5ad9407f432624f
2017-07-21Merge "wifi: Add owners" into oc-mr1-devTreeHugger Robot
2017-07-20wifi: Add ownersRoshan Pius
Change-Id: If5a9a7da36b86f968bd32768d61e5d181573d30a
2017-07-20[HAL] Invalidate chip before shutting down legacy HALEtan Cohen
Change the order of shutdown to invalidate chips before shutting down the legacy HAL. Allows pre-shutdown commands to be sent down. Bug: 63704506 Test: NAN tests passing Test: full regression suite Change-Id: I03d237d732b4e3482b1e1639848342dfdde9fcb7
2017-07-19[HAL] Invalidate chip before shutting down legacy HALEtan Cohen
Change the order of shutdown to invalidate chips before shutting down the legacy HAL. Allows pre-shutdown commands to be sent down. Bug: 63704506 Test: NAN tests passing Test: full regression suite Change-Id: I03d237d732b4e3482b1e1639848342dfdde9fcb7
2017-07-17wifi: Add the missing RTT capabilitiesRoshan Pius
These feature flags are defined in the legacy HAL, but were not exposed in the HIDL interface. Updated the hash in current.txt using 'hidl-gen -L hash -r android.hardware.wifi@1.1:hardware/interfaces -r android.hardware:hardware/interfaces -r android.hidl:system/libhidl/transport android.hardware.wifi@1.1::IWifiChip' Bug: 63545934 Test: Manual testing Change-Id: Ia196e0fc1c5e305210ec95eb8a54b1a1204ebf20
2017-07-11wifi(implementation): Set/Reset TX power limitRoshan Pius
Hookup the HIDL method calls to the respective newly added legacy HAL functions for setting/resetting TX power limits for SAR requirements. Bug: 62437848 Test: VTS test fails because of a bug in Qcom implementation. Working with Qcom to fix their implementation. Change-Id: Ia619f5558e44d44fd77d037e72dfc1f6863b51e0
2017-07-06wifi(implementation): Create 1.1 interface packageRoshan Pius
1. Move the implementation in 1.0/default to 1.1/default. 2. Move all of the implementation to android::hardware::V1_1::implementation namespace. 3. All of the header files include the android::hardware::V1_0 namespace so that it can access the types from 1.0 package. ("using namespace" is against Google style guide though :(). The other option to prefix each 1.0 type with the namespace name. For example: V1_0::WifiStatus. 4. Added the implementation of the new 1.1 method IWifiChip.setTxPowerLimit(). 4. The executable name and the .rc still has 1.0 name in it to avoid changing all the device.mk files. TODO: Hookup to the new legacy HAL API. Bug: 62437848 Test: mmm -j128 hardware/interfaces/wifi/1.1/default/ Test: Device boots up and able to connect to wifi networks. Test: New VTS tests passes Change-Id: Ib36282939e70b064f246041a03d8870f5cb6410e