Unset mIsTransactionPending before invoking handleTxnResult
to allow service to start a new transaction.
Bug: 70387233
Test: Run a sample application that concurrently loads and unloads 2
nanoapps, verify both transactions succeed.
Change-Id: I465882dd8fd8fdd89b959642f6fdc2e452ce61a6
Bug: 70158191
Bug: 70339559
Test: Compile and flash on sailfish-userdebug, run CHQTS and verify pass
Change-Id: I3f59560e25faa3627dcd803e3cc6d9cbc30c2645
Changes to Java HIDL at ContextHubService caused empty messages with
sendMessageToHub to be populated with null pointers. Work around this by
creating a dummy pointer in this case.
Bug: 69065562
Test: Compile on sailfish-userdebug, run CHQTS and verify pass
Change-Id: I763cbf9696f6dc04637add3ed1da01f9c32d458b
To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in http://go/treble-sysprop-compatibility.
Test: succeeded building and tested on a walleye device
Bug: 36796459
Change-Id: I4e8fbee791ec917a8f627a1366f4d44ec7e6febc
Update default implementation to use the new fields defined explicitly
for passing in target CHRE API version information, rather than adding
this data into the reserved area.
Bug: 64852297
Test: run CHQTS on Nanohub, rebuild test app targeting 1.2 and confirm
it's interpreted correctly
Change-Id: Id11f9b510a2d239d285436e119b7b8dbece4c5df
Register for notification of service death for callbacks registered with
the context hub HAL. Upon this notification, unregister the callback to
avoid crashing if an event occurs prior to the service coming back up.
Bug: 36202367
Test: adb shell stop, confirm death notification received via log;
vts-tradefed run commandAndExit vts --module VtsHalContexthubV1_0Target
Change-Id: I3c25229806cb9f2a116007939c752841edbf0985
android-base macros was being transitively included from MQDescriptor.h
Test: links
Bug: 37791060
Change-Id: I2433462aae3d68a0d90cd6817338ba70d343b833
(cherry picked from commit 56b4c24bb7)
We need google shims on the vendor partition because they are providing
an implementation of a vendor defined interface. They were written by
google just as a courtesy/to make the transition easier. They're
basically a set for vendors to assemble their hal implementations
from.
Bug: 34135607
Test: marlin persist.hal.binderization on/off
Change-Id: I2e2af5af39264cf290259755bb9b2eb9827a21f5
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds
Bug: 33844934
Change-Id: I5640441f5cfc7846e854f7ea23abb76ab3628d52
Parse the nanoapp binary header in the framework and pass the relevant
data to the HAL explicitly in the NanoAppBinary structure. Note that not
all fields from the header are carried forward into NanoAppBinary, as
they are either implied by the HAL API (version, magic), or inherent in
the implementation-specific data (hwHubType), or unused and will only be
added via a future HAL version bump (second reserved field).
Also, convert the flags field in struct MemRange to a bitmask, which is
the proper representation for its use.
Bug: 34182159
Test: run hello world context hub GTS test
Change-Id: I13da9883b851e978d760548ec4265094ce81510a
Adds the default context hub hal implementation and service.
Test: Context Hub GTS tests still pass.
Change-Id: I7416ce9ec8efca7f98d2bb63606f030f4e8c8ead
