Lines Matching refs:chre
23 * interface for the Context Hub Runtime Environment (CHRE). This interface is
31 #include <chre/audio.h>
32 #include <chre/common.h>
33 #include <chre/event.h>
34 #include <chre/gnss.h>
35 #include <chre/nanoapp.h>
36 #include <chre/re.h>
37 #include <chre/sensor.h>
38 #include <chre/version.h>
39 #include <chre/wifi.h>
40 #include <chre/wwan.h>
44 * CHRE is the Context Hub Runtime Environment. CHRE is used in Android to run
46 * other than the applications processor that runs Android itself. The CHRE
48 * compatible CHRE implementation. The CHRE API provides the ability for
49 * creating nanoapps that are code-compatible across different CHRE
51 * a discussion on some important details of CHRE that aren't explicitly exposed
56 * The following entry points are used to bind a nanoapp to the CHRE system, and
57 * all three must be implemented by any nanoapp (see chre/nanoapp.h):
62 * The CHRE implementation must also ensure that it performs these functions
71 * A CHRE implementation is free to choose among many different
74 * underlying choice. However, the CHRE implementation must ensure that time
76 * interfere with other functions of the system in which CHRE is implemented,
83 * must be FIFO, but the CHRE implementation may choose to violate total
87 * This version of the CHRE API does require that all nanoapps are treated as
94 * For example, if a nanoapp is currently in nanoappHandleEvent(), the CHRE is
97 * callback, the CHRE is not allowed to call nanoappHandleEvent(), or invoke
103 * where otherwise a CHRE implementation is likely to leak memory. Similarly,
105 * directly, whether it returns 'true' or 'false'. This is because the CHRE
114 * [1]: Note to CHRE implementers: A future version of the CHRE platform may
124 * CHRE and possibly other services as well.
127 * Also, as noted in the Threading Model section, a CHRE implementation may
133 * prior to returning control to the CHRE implementation. A CHRE implementation
148 * The C type 'float' is used in this API, and thus a CHRE implementation
152 * CHRE implementation. Note that if a CHRE decides to support them, unlike
156 * If a CHRE implementation choses not to support 'double' or
160 * @section compat CHRE and Nanoapp compatibility
162 * CHRE implementations must make affordances to maintain binary compatibility
164 * to both running a nanoapp compiled for a newer version of the API on a CHRE
182 * Note that the CHRE API only specifies the software interface between a
183 * nanoapp and the CHRE system - the binary interface (ABI) between nanoapp and
184 * CHRE is necessarily implementation-dependent. Therefore, the recommended
186 * Library (NSL) that is specific to the CHRE implementation into the nanoapp
188 * In addition, to accomplish forwards compatibility, the CHRE implementation is
189 * expected to recognize the CHRE API version that a nanoapp is targeting and
193 * compatibility. Therefore, a CHRE implementation must not attempt to load a
