diff options
| author | Anthony Stange <stange@google.com> | 2022-04-18 21:42:47 +0000 |
|---|---|---|
| committer | Anthony Stange <stange@google.com> | 2022-04-19 17:57:00 +0000 |
| commit | caa0d250f243dccc562837dba59447d8d3f58c92 (patch) | |
| tree | be9b813dec98e74b7215ab5d3fbb59fe0432f3a6 | |
| parent | 474803cf6b97d360016357b7babeb554e006fdc3 (diff) | |
| download | chre-caa0d250f243dccc562837dba59447d8d3f58c92.tar.gz | |
Support NAN ranging async result on CHPP client
Technically, the NAN ranging async notifiaction should come in as a
normal ranging notification because they are mapped through the same
callback, but to limit confusion, we should map them both to the same
method to avoid mixups.
Bug: 229629371
Test: run PTS
Change-Id: Id02b6cc1ebf887b2c109606bf9c0c16ecde133cc
| -rw-r--r-- | chpp/clients/wifi.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/chpp/clients/wifi.c b/chpp/clients/wifi.c index fcda4026..18ace6d5 100644 --- a/chpp/clients/wifi.c +++ b/chpp/clients/wifi.c @@ -278,7 +278,8 @@ static enum ChppAppErrorCode chppDispatchWifiNotification(void *clientContext, break; } - case CHPP_WIFI_REQUEST_RANGING_ASYNC: { + case CHPP_WIFI_REQUEST_RANGING_ASYNC: + case CHPP_WIFI_REQUEST_NAN_RANGING_ASYNC: { chppWifiRangingEventNotification(wifiClientContext, buf, len); break; } |