Home
last modified time | relevance | path

Searched refs:nanoapps (Results 1 – 25 of 32) sorted by relevance

12

/aosp12/system/chre/doc/
H A Dnanoapp_overview.md11 low-power hardware. Typically, nanoapps integrate with a component on the
14 as the nanoapp’s “client”. Since nanoapps are not limited to the same power
29 nanoapps. In other words, the system only runs nanoapps that possess a digital
52 nanoapps (described later) are typically built as static nanoapps.
56 (using the `--gc-sections` option, or equivalent). Static nanoapps are
80 the list of nanoapps that should be automatically loaded.
115 also be used for production nanoapps.
139 nanoapps is given below:
159 These nanoapps help stress test the CHRE framework. They include:
186 unloading all other nanoapps in the system (which can be done via
[all …]
H A Dvendor_extensions.md11 framework code and vendor-specific nanoapps.
13 2. Expose the new APIs from the framework to nanoapps, and connect them to a new
68 To expose the new functionality to nanoapps, it’s recommended to create a single
71 nanoapps should include in their Makefile prior to including
78 conditions due to multiple nanoapps calling into APIs, and likewise nanoapps do
96 **after** `chre::init` is called, but **before** loading any static nanoapps or
97 invoking `EventLoop::run()` to ensure that nanoapps don’t begin interacting with
120 milliseconds are discouraged, as these can prevent other nanoapps from
127 (`Nanoapp::getInstanceId()`), or broadcast to all nanoapps registered for the
133 nanoapps, depending on what error handling is desired in the case that the event
H A Dframework_testing.md37 ## FeatureWorld nanoapps
39 Located under the `apps/` directory, FeatureWorld nanoapps interact with the set
46 These apps are usually built into the CHRE framework binary as static nanoapps
48 information on static nanoapps.
54 and interact with test nanoapps which then exercise the CHRE API. While this
H A Dnanoapp_developer_guide.md5 Since CHRE is an open platform, anyone can write nanoapps. However, deploying to
42 CHRE guarantees support for nanoapps written in C99 or C++11, though not all
86 * Restart CHRE to reload all nanoapps, including the new one
90 While not strictly enforced, nanoapps are recommended to follow the convention
101 `chre_api/include`, as well as usage of the APIs by sample nanoapps. The CHRE
112 by nanoapps.
168 nanoapps within CHRE. Similar to how nanoapps communicate with the host by
169 passing *messages*, nanoapps can communicate with one another by passing
267 following standard library features are not meant to be used by nanoapps:
315 When running on CHRE v1.4+, nanoapps can also append information to the CHRE
[all …]
H A Dcompatibility.md11 cross-device compatibility for all nanoapps which are written in a supported
130 Similar to how Android apps have a “target SDK” attribute, nanoapps have a
140 CHRE implementation to reject compatibility with nanoapps compiled against an
152 maintained with nanoapps, by choosing a design that provides this property. For
157 nanoapps to be recompiled to be able to work with an updated CHRE
187 used to break compilation of nanoapps using the deprecated function, forcing
195 CHRE must continue to provide the deprecated function to support nanoapps
199 the function is made compilation-breaking for nanoapps, since forward
215 possible for CHRE and/or the NSL to detect only nanoapps that use the deprecated
216 functionality, then it is permissible to block loading of only those nanoapps,
[all …]
H A Dnanoapp_clients.md6 as the *client* of the nanoapp. There are two ways to interact with nanoapps
14 Interaction between nanoapps and clients occur through a flexible message
60 advantages, like being able to interact with system nanoapps that are not
H A Dframework_overview.md18 code as well as CHRE system callbacks. Per the CHRE API, nanoapps can’t execute
49 does not get delivered to any nanoapps. Instead, the purpose is to invoke the
59 Abstractions section), includes it in the collection of loaded nanoapps to
122 distribute the data to nanoapps.
125 sensor data to all nanoapps registered for the broadcast event type
H A Dporting_guide.md9 underlying subsystems to nanoapps.
82 CHRE provides various test nanoapps in `apps/` that exercise a particular
132 from nanoapps, as well as device-specific functionality as needed. Some examples
136 * Loading preloaded nanoapps at startup
193 possible for the associated CHRE APIs to be called by nanoapps without crashing
243 * Makes it possible to update nanoapps without requiring a system reboot,
H A Dframework_debugging.md12 for printf-style debugging. This capability is also exposed to nanoapps via
54 dumps from the CHRE framework and nanoapps. Refer to the associated
/aosp12/system/chre/
H A DREADME.md5 applications, called *nanoapps*. CHRE runs in a vendor-specific processor that
7 enables CHRE and its nanoapps to be more power-efficient for use cases that
31 * Documentation related to nanoapps:
48 - ``apps/``: Public nanoapp source code, including sample nanoapps intended to
49 showcase how to use the CHRE APIs, and test nanoapps used to validate API
52 supports building the CHRE framework and nanoapps using a configurable
65 - ``java/``: Java test code used in conjunction with test nanoapps
80 core framework implementation. Includes code that is usable by nanoapps.
90 APIs used by privileged apps to interact with CHRE and nanoapps
/aosp12/hardware/interfaces/contexthub/1.1/default/
H A DContexthub.cpp42 std::vector<HubAppInfo> nanoapps; in queryApps() local
43 mCallback->handleAppsInfo(nanoapps); in queryApps()
/aosp12/hardware/interfaces/contexthub/1.2/default/
H A DContexthub.cpp67 std::vector<V1_2::HubAppInfo> nanoapps; in queryApps() local
68 mCallback->handleAppsInfo(nanoapps); in queryApps()
/aosp12/system/chre/apps/test/chqts/
H A DREADME.md1 The subdirectories here contain the source code for nanoapps used for Context
/aosp12/system/chre/apps/tflm_demo/
H A DREADME10 aware of this when developping nanoapps using flatbuffer.
/aosp12/system/chre/platform/shared/idl/
H A Dhost_messages.fbs84 /// not show up in the list of nanoapps in the context hub HAL. System
85 /// nanoapps are typically used to leverage CHRE for some device functionality
97 nanoapps:[NanoappListEntry] (required);
188 /// Set to true to allow this request to unload nanoapps identified as "system
189 /// nanoapps", i.e. ones with is_system set to true in NanoappListResponse.
/aosp12/system/chre/std_overrides/
H A DREADME.md3 CHRE provides nanoapps with a minimal list of overrides to standard library
/aosp12/system/chre/apps/test/pts/proto/
H A Dpts_chre.proto8 // The message types used in PTS test nanoapps. Some of them are H2C
/aosp12/system/chre/platform/shared/include/chre/platform/shared/generated/
H A Dhost_messages_generated.h827 const flatbuffers::Vector<flatbuffers::Offset<chre::fbs::NanoappListEntry>> *nanoapps() const {
833 verifier.VerifyVector(nanoapps()) &&
834 verifier.VerifyVectorOfTables(nanoapps()) &&
843 …tbuffers::Offset<flatbuffers::Vector<flatbuffers::Offset<chre::fbs::NanoappListEntry>>> nanoapps) {
844 fbb_.AddOffset(NanoappListResponse::VT_NANOAPPS, nanoapps);
861 …fers::Offset<flatbuffers::Vector<flatbuffers::Offset<chre::fbs::NanoappListEntry>>> nanoapps = 0) {
863 builder_.add_nanoapps(nanoapps);
869 const std::vector<flatbuffers::Offset<chre::fbs::NanoappListEntry>> *nanoapps = nullptr) {
870 …auto nanoapps__ = nanoapps ? _fbb.CreateVector<flatbuffers::Offset<chre::fbs::NanoappListEntry>>(*…
/aosp12/system/chre/build/sys_support/qcom/
H A Dchre.scons49 # Configure testing nanoapps
52 # CHRE provides several nanoapps that can be used to verify that APIs are
53 # working as expected. To use these nanoapps, set 1 or more of the following
55 # nanoapps
/aosp12/system/chre/host/common/test/
H A Dchre_test_client.cc116 LOGI("Got nanoapp list response with %zu apps:", response.nanoapps.size()); in handleNanoappListResponse()
118 response.nanoapps) { in handleNanoappListResponse()
/aosp12/hardware/interfaces/contexthub/1.0/
H A DIContexthub.hal24 * Native applications that run within a context hub are known as nanoapps, and
166 * be returned. A non-modifiable nanoapps must not be
/aosp12/hardware/interfaces/contexthub/1.2/
H A DIContexthub.hal31 * support for nanoapps to enforce host
H A DIContexthubCallback.hal43 * currently loaded and active nanoapps on the hub.
/aosp12/system/chre/platform/android/
H A Dhost_link.cc128 response->nanoapps.push_back(std::move(nanoappListEntry)); in handleNanoappListRequest()
/aosp12/hardware/google/pixel/pixelstats/
H A DDropDetect.cpp119 for (const std::unique_ptr<fbs::NanoappListEntryT> &nanoapp : response.nanoapps) { in handleNanoappListResponse()

12