diff options
author | Ahmed ElArabawy <arabawy@google.com> | 2019-03-25 10:42:04 -0700 |
---|---|---|
committer | Ahmed ElArabawy <arabawy@google.com> | 2019-03-27 17:19:23 -0700 |
commit | 048e148ea07a4c57d71a44041be8ff3377f3d09f (patch) | |
tree | a95f8238551584beee1c97ce51feb6bdd279e93d /proto/src | |
parent | 9cd1d069d627fdadf1c2c6c395f819c0a50e397b (diff) |
wifi.proto: Add WifiLock statistics
This commit adds WifiLock statistcis to the wifi.proto
Bug: 129273779
Test: Compiles
Test: frameworks/base/wifi/tests/runtests.sh
Change-Id: Ie2424b28d78d668d41da752cdbb7c9eefad35976
Diffstat (limited to 'proto/src')
-rw-r--r-- | proto/src/wifi.proto | 30 |
1 files changed, 30 insertions, 0 deletions
diff --git a/proto/src/wifi.proto b/proto/src/wifi.proto index 1ce0c5292ab8..a79a28412329 100644 --- a/proto/src/wifi.proto +++ b/proto/src/wifi.proto @@ -533,6 +533,9 @@ message WifiLog { // Network Suggestion API surface metrics. optional WifiNetworkSuggestionApiLog wifi_network_suggestion_api_log = 142; + + // WifiLock statistics + optional WifiLockStats wifi_lock_stats = 143; } // Information that gets logged for every WiFi connection. @@ -2451,3 +2454,30 @@ message WifiNetworkSuggestionApiLog { // Histogram for size of the network lists provided by various apps on the device. repeated HistogramBucketInt32 network_list_size_histogram = 4; } + +// WifiLock metrics +message WifiLockStats { + // Amount of time wifi is actively in HIGH_PERF mode (ms) + // This means the lock takes effect and the device takes the actions required for this mode + optional int64 high_perf_active_time_ms = 1; + + // Amount of time wifi is actively in LOW_LATENCY mode (ms) + // This means the lock takes effect and the device takes the actions required for this mode + optional int64 low_latency_active_time_ms = 2; + + // Histogram of HIGH_PERF lock acquisition duration (seconds) + // Note that acquiring the lock does not necessarily mean that device is actively in that mode + repeated HistogramBucketInt32 high_perf_lock_acq_duration_sec_histogram = 3; + + // Histogram of LOW_LATENCY lock acquisition duration (seconds) + // Note that acquiring the lock does not necessarily mean that device is actively in that mode + repeated HistogramBucketInt32 low_latency_lock_acq_duration_sec_histogram = 4; + + // Histogram of HIGH_PERF active session duration (seconds) + // This means the lock takes effect and the device takes the actions required for this mode + repeated HistogramBucketInt32 high_perf_active_session_duration_sec_histogram = 5; + + // Histogram of LOW_LATENCY active session duration (seconds) + // This means the lock takes effect and the device takes the actions required for this mode + repeated HistogramBucketInt32 low_latency_active_session_duration_sec_histogram = 6; +} |