History log of /device/google/contexthub/contexthubhal/nanohubhal.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
227914e6d74b7d2ae1738dfd372e54944c64f84f 05-Feb-2018 Ben Fennema <fennema@google.com> contexthubhal: update to handle chre messaging interface

use new chre messaging interface
start apps that were loaded via hal on reset
cache apps loaded via the hal
when receiving an app, if the app is already present on nanohub
verify if the app is the same and just start the present app if
it is. (compare new app to one on disk and compare stored crc to
crc of app on nanohub)
Handle upload error due to out of space by doing a commanded erase
and then re-uploading the app
Add debug commands to load/unload/enable/disable apps via lshal debug

Bug: 69980445
Test: run CHQTS
Change-Id: Ief60123353b503c44c5b19570c50492b380c2c04
Signed-off-by: Ben Fennema <fennema@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
f378cb36e45cbfd402a26982a284dbd2933d5ef8 04-Jan-2018 Ben Fennema <fennema@google.com> contexthubhal: add nanohub contexthub impl and service

For now, maintain legacy context_hub.default.so support.

Bug: 70933028
Test: verify messages still successfully passed back to contexthub service
Change-Id: I9a36b4f6d581243b9de3a5e6d742d17c1aa49f88
Signed-off-by: Ben Fennema <fennema@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
0791225a0cff01e426b0f8778d9f5d43f8393dd4 27-Dec-2017 Ben Fennema <fennema@google.com> nanohub: add endpoint support

Pass endpoint from nanohub to the hal.
(hal currently has no way to pass the endpoint any further)

Bug: 70933028
Test: verify messages still successfully passed back to contexthub service
Change-Id: I8731de32c9d77a0d67d8ee8440e35a4c9853a97c
Signed-off-by: Ben Fennema <fennema@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
404a713d9313ff660bfc65e06b07da4267aceed1 12-Jul-2017 Ben Fennema <fennema@google.com> nanohub: add CHRE 1.1 support to fix CHQTS build errors

Pull in chre headers from system/chre
Bug: 63626848
Test: Build CHQTS nanohub test apps and verify they pass
Change-Id: Ibc6861b21ab3f1d0cde6f774b5c38c20c01a720d
Signed-off-by: Ben Fennema <fennema@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
679ee8dd0d6f535da9062ddef53cf9b8b00bc3c2 30-Dec-2016 Brian Duddie <bduddie@google.com> nanohubhal: Perform graceful shutdown in destructor

When destroying the NanoHub HAL singleton, perform graceful shutdown
including clean exit of the poll and app threads. This is the equivalent
cleanup done when a null callback is passed to subscribe_messages.

This fixes a crash seen during VTS testing where tests pass, but then
the default std::thread destructor is called for the NanoHub HAL
threads, which invokes std::terminate and causes the test to be marked
as failing.

Test: Context Hub VTS (currently under development)
Change-Id: Iaec2cad037ba81eaa19243d3019d81e433c9a2f8
/device/google/contexthub/contexthubhal/nanohubhal.h
672acdeb3c63987a9a778dbcc84fe74e0fb4a5db 03-Dec-2016 Stephen Hines <srhines@google.com> Refactor to eliminate taking the address of a packed member.

Bug: http://b/31532493

NanoHub::doRun() was previously taking the address of msg.hdr.app_name,
which isn't allowed, as it could possibly be misaligned. In fact,
looking at the data structure layout of the packed, nested structs,
app_name (a struct containing only a single uint64_t) will always be
packed immediately after a uint32_t. No matter what alignment we want to
apply to the main struct, we will never end up with an aligned uint64_t.
To address this, we merely switch to copying the uint64_t directly,
rather than passing it as a pointer.

Test: Built successfully with latest compilers.

Change-Id: Iecf67cb10a0f5e2b8ceb6363e0c4a9b927d1bfa9
/device/google/contexthub/contexthubhal/nanohubhal.h
53d7164c9e25b417d597c102d92bae3050c149ae 26-Sep-2016 Alexey Polyudov <apolyudov@google.com> nanohub HAL: abort outstanding sessions on FW reboot

Bug: 31361942
Change-Id: Iace48661521cd262c6b674a181e616bea38f6426
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
0ce3d053b7c75d4759e047653868cb1079e32252 16-Sep-2016 Alexey Polyudov <apolyudov@google.com> nanohub HAL: add support for new message format (CHRE)

Bug: 31393280
Change-Id: Ic7613294b09dd5be054fbf1e259a6063433350a8
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
c8e09a8dc0eecf2e0fb473ff8d8c0574f7fbfa9c 12-Sep-2016 Alexey Polyudov <apolyudov@google.com> nanohub: move common definitions to common header and adjust code

this is a no-op change;
it moves definitions from os-specific to project-wide generic
header, to allow both HAL and FW use the same data structures.

There are minor code changes to ensure correct type handling.
Some changes done to source formatting as well

Bug: 31393280
Change-Id: I29d3034e1956ea6bc89b92424425894d408a95e0
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
7adb1a0b7ba0f6c2ef0c3e44979a382314f0ab0c 13-Sep-2016 Alexey Polyudov <apolyudov@google.com> nanohub HAL: use STL thread model

Change-Id: I8114d1b4cd46399b4ca2cca02667488853846d8a
/device/google/contexthub/contexthubhal/nanohubhal.h
e96ece71fbd610603074755303e1d6cc3e505b00 29-Jul-2016 Zhengyin Qian <qianzy@google.com> contexthubhal: use AOSP header.

BUG: 30503963
Change-Id: Ie96dfa8ab08e3cf7f45fdf9725aac5a657a6719b
/device/google/contexthub/contexthubhal/nanohubhal.h
70ab6271e35d78b86a68b00b663c177230697fb5 28-Apr-2016 Alexey Polyudov <apolyudov@google.com> nanohub HAL: support for new firmware

plus improved message logging

Bug: 28265099
Change-Id: I3a3b2f3abfd59bfce273dbedc10942d2efc21f5e
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
96177b03ab7915a8abce9fcb14f61be2edab918f 12-Apr-2016 Alexey Polyudov <apolyudov@google.com> make nanohub HAL c++ aware

Change-Id: I383f0ca68874908ec7d75b834264cac05f6831f3
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
fd9c05e653cf9de55c72afb85af849f5d932e1a1 08-Apr-2016 Alexey Polyudov <apolyudov@google.com> contexthubhal: redefine hal_app_name_t

Bug: 28086503
Change-Id: Ife021bb59afcfb3efae1c8b85c6a415c33756817
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
/device/google/contexthub/contexthubhal/nanohubhal.h
b143f602214a5b711b5c9b1c3a11c8bd49f84764 23-Mar-2016 Greg Kaiser <gkaiser@google.com> contexthubhal: Fix compiler warning, minor rework.

While fixing a compiler warning about a comparison between signed
and unsigned types, we rework our constants a little. We no longer
hardcode 1 for the length required to store the packet length.
And instead of adding together our event id, app name, and packet
length lengths in multiple areas, we create a constant for it.

We also give more detailed log messages in error cases, and avoid
reading uninitialized memory from the 'header' if we failed to
read as many bytes as we expected.

Change-Id: I3ce246f9c4bf08f590bb2d250005d5fd7f93bbc5
/device/google/contexthub/contexthubhal/nanohubhal.h
fe2188fa871f1d4470378c004ad44d4216202641 03-Mar-2016 Ben Fennema <fennema@google.com> Revert "Revert "HAL: first pass at a nanohub HAL""

This reverts commit ebacef28451fa916940da2283d21fa813400512c.

Change-Id: I3bf641750e66769476f878128248c5d42b734c94
/device/google/contexthub/contexthubhal/nanohubhal.h