Lines Matching refs:code

16 approach that separates common code from platform-specific code. CHRE is an
18 code as well as CHRE system callbacks. Per the CHRE API, nanoapps can’t execute
25 To get a better understanding of code structure and how it weaves between common
28 everything that happens in each case (for that, refer to the code itself), but
43    link the code.
45 2. Once the nanoapp code is loaded, the platform code calls
55    transition from platform-specific to common code.
64    code can vary by platform, transferring control from the framework to a
87    framework code is only safe to execute from within the main CHRE thread), and
93    nanoapp’s request - we transition to common code here.
112 1. Starting in platform-specific code, likely in a different thread, the
121 3. `SensorRequestManager::handleSensorDataEvent()` is invoked (common code) to
143 of `virtual` functions, while minimizing code size impact on systems with tight
156 While `SensorRequestManager` is fully common code, `PlatformSensorManager` is
159 interface between common code and platform-specific code.
170 resolve include directives appearing in common code but referencing
174 To ensure compatibility across all platforms, common code is restricted in how
175 it interacts with platform-specific code - it must always go through a common
177 platform-specific code is less restricted, and can refer to common code, as well
178 as other platform code directly.
183 code](https://google.github.io/styleguide/cppguide.html), with the exception of
187 Google. Additionally, this project uses clang-format for automatic code
201    extensive or widespread in the embedded environments where this code will