Lines Matching refs:platform

16 approach that separates common code from platform-specific code. CHRE is an
26 and platform-specific components, it is helpful to trace the flow through a few
39    processor where CHRE is running using a platform-specific method. While the
41    CHRE via the platform-specific HostLink implementation, then verify its
45 2. Once the nanoapp code is loaded, the platform code calls
53 3. The (platform-specific) callback finalizes the newly constructed `Nanoapp`
55    transition from platform-specific to common code.
58    common and platform-specific data and functions, as described in the Platform
64    code can vary by platform, transferring control from the framework to a
65    nanoapp is considered part of the platform layer. So
77 2. The Nanoapp Support Library (NSL) and/or the platform's dynamic linking
79    nanoapp binary to the CHRE framework. This can vary by platform, but we'll
81    `platform/shared/chre_api_sensor.cc`.
97    requested from the platform, and the nanoapp is registered to receive
112 1. Starting in platform-specific code, likely in a different thread, the
115    the fully platform-specific `PlatformSensorManagerBase` class.
149 composed with platform-specific functionality at compile-time. Using the
152 single request made to the platform through the `PlatformSensorManager` class,
157 defined in a common header file (under `platform/include/chre/platform`), but
158 implemented in a platform-specific source file. In other words, it defines the
159 interface between common code and platform-specific code.
162 defined in a platform-specific header file, which allows for extending
163 `PlatformSensorManager` with platform-specific functions and data. This pattern
171 platform-specific headers, like `#include
175 it interacts with platform-specific code - it must always go through a common
176 interface with platform-specific implementation, as described above. However,
177 platform-specific code is less restricted, and can refer to common code, as well
178 as other platform code directly.
203    favor of simple platform abstractions that can be implemented directly with