[CrOS Multidevice] Integrate SecureChannel API into ProximityAuthMonitor.
This injects a ClientChannel into ProximityAuthMonitor, which is used if the chromeos::features::kMultiDeviceApi is enabled. The ClientChannel is used to get the current RSSI of the connected remote device. In the future, the "rolling average RSSI" that is calculated in ProximityAuthMonitor will be moved to the SecureChannel API, and returned by it. However, to reduce immediate migration work, that logic is kept in ProximityAuthMonitor for now. R=jhawkins@chromium.org, khorimoto@chromium.org Bug: 824568, 752273 Change-Id: I8d6485a5a0018fe43595b880c25a2fa9af5a1b75 Reviewed-on: https://chromium-review.googlesource.com/1106616 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:James Hawkins <jhawkins@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#569425}
Showing
This diff is collapsed.
Please register or sign in to comment