| 47a99dc3cacacb0418548609c0e2d3b2b70d821e |
|
27-Mar-2017 |
Brian Duddie <bduddie@google.com> |
Implement dynamic loading of nanoapps
Add support for loading a dynamic shared object containing a nanoapp
that has been received over the communications link with the host.
Test: use chre_test_client to load activity recognition on SLPI
Change-Id: I76da777ec19283ee67120b4b024133c556edf6e2
/system/chre/host/common/include/chre_host/host_protocol_host.h
|
| f685db3a6b34f8dd6942964ae99836bda87c8134 |
|
21-Mar-2017 |
Brian Duddie <bduddie@google.com> |
Support unicast messages from CHRE to host
Tag messages sent to CHRE with the client ID of the sender. Populate
this same value in the response to discriminate the addressee so that
responses are only delivered to the client who sent the request.
Test: run multiple instances of chre_test_client
Change-Id: I60d52944cf4e6cb2bb1fb21e9806eadd7f74b6c2
/system/chre/host/common/include/chre_host/host_protocol_host.h
|
| 07da7d6425058577d477074f99bafd4b8e81bb83 |
|
20-Mar-2017 |
Brian Duddie <bduddie@google.com> |
Use FlatBuffers object API on host
Generate and use the FlatBuffers object API to interact with messages
from CHRE on host-side code. Although it involves some more overhead,
this API is a bit cleaner to use.
Test: run chre_test_client
Change-Id: If48d18999fc2743425bd1ba425a05b8fc5df8efe
/system/chre/host/common/include/chre_host/host_protocol_host.h
|
| a2f5add27054c406f36528cf8a5cbc6d4c79d246 |
|
20-Mar-2017 |
Brian Duddie <bduddie@google.com> |
Add support for querying the list of apps
Add a new FlatBuffers message to encapsulate the list of loaded apps,
and add code to CHRE to populate it. Update the reference HAL
implementation to pass the request and response through the HAL.
Test: run chre_test_client
Change-Id: I7b470daa2f051280fdb5415cdab7297de6ab4d59
/system/chre/host/common/include/chre_host/host_protocol_host.h
|
| 7621b3267fd2ff1068d7aa7d75441d68646226ab |
|
19-Mar-2017 |
Brian Duddie <bduddie@google.com> |
Reorganize HostProtocol, add hub info query
Split HostProtocol into three classes: one for the host, one for CHRE,
and one that's shared. Since the protocol is not fully symmetric (e.g.
messages to/from nanoapps are the same in both directions, but only one
side will ever request hub info, and only CHRE will ever construct the
response), this avoids pulling in unneeded code.
Also, add support for querying hub information from CHRE to be used in
the HAL, and rework the HostLink pending outbound message queue to be
more generic.
Test: run chre_test_client
Change-Id: Id88485b8c5a085eb886d4059840ac640c0383c88
/system/chre/host/common/include/chre_host/host_protocol_host.h
|