Lines Matching refs:nanoapp

17 event-based system, so CHRE is built around an event loop which executes nanoapp
31 ## Loading a nanoapp via the HAL
33 There are multiple ways by which a nanoapp can be loaded (see the relevant
35 loading a nanoapp that has been passed in via the Context Hub HAL's
38 1. The nanoapp binary reaches the HAL implementation, and it is loaded into the
45 2. Once the nanoapp code is loaded, the platform code calls
47    (if needed), so it can complete loading and starting the nanoapp.
61    nanoapp it's about to execute, and calls into `PlatformNanoapp::start()`.
65    nanoapp is considered part of the platform layer. So
67    into the `nanoappStart()` function defined in the nanoapp binary.
69 ## Invoking a CHRE API from a nanoapp
71 Let's assume the nanoapp we've loaded in the previous section calls the
74 1. The nanoapp invokes `chreSensorConfigure()` with parameters to enable the
79    nanoapp binary to the CHRE framework. This can vary by platform, but we'll
84    function is being called from the context of a nanoapp being executed within
85    the event loop (since associating the API call with a specific nanoapp is a
93    nanoapp’s request - we transition to common code here.
95 5. The request is validated and combined with other nanoapp requests for the
97    requested from the platform, and the nanoapp is registered to receive
104 7. Assuming success, the return value propagates back up to the nanoapp, and it
107 ## Passing an event to a nanoapp
110 sample has been generated and is delivered to the nanoapp for processing.
134    nanoapp that should receive the event.
136 7. Once the event has been processed by each nanoapp, the free callback