Lines Matching refs:platform

6 interfaces that the platform needs to implement. These interfaces provide
7 dependencies for the common CHRE code that are necessarily platform-specific.
8 Additionally, platform code calls into common code to ferry events from
12 new platform in the CHRE reference implementation.
16 CHRE platform code can be broadly categorized as follows.
20 Files under `platform/include` serve as the interface between common code in
21 `core/` and other platform-specific code in `platform/<platform_name>`.  These
23 supporting an individual platform.
27 Located in `platform/shared/`, the code here is part of the platform layer’s
28 responsibilities, but is not necessarily specific to only one platform. In other
30 strictly necessary for a given platform to use it.
34 Files under `platform/<platform_name>` are specific to the underlying software
35 of a given platform, for example the APIs which are used to access functionality
36 like sensors, the operating system, etc. To permit code reuse, the CHRE platform
45   `platform/<platform_name>/<file_name>.cc`, but may appear in a subdirectory
48   `platform/<platform_name>/include/chre/target_platform/<file_name>.h`, and are
49   included by *Platform Interfaces* found in `platform/include` and provide
53 * **Fully platform-specific headers**: these typically appear at
54   `platform/<platform_name>/include/chre/platform/<platform_name/<file_name>.h`
55   and may only be included by other platform-specific code
59 Partners who add support for a new platform are recommended to upstream their
62 This helps ensure that details of your platform are considered by the team that
68 If some parts of a platform’s CHRE implementation must be kept closed source,
76 When starting to add support for a new platform in the CHRE framework, it’s
79 platform implementation can be referenced to create empty stubs, and then
83 feature that the platform provides. These are selectively compiled into the
88 1. Create a new platform with only empty stubs, with optional features (like
95 3. Implement base primitives from `platform/include`, including support for
102    from another platform)
127 host messaging protocol defined under `platform/shared` (platform
145 When adding support for a new platform, a new HAL implementation and/or daemon
169 included in the `shared` platform directory may be used. PALs provide a C API
171 modules/libraries, and it also allows for the main CHRE to platform-specific
185 a platform implementation is included in AOSP, then it is possible for the
195   support (refer to `platform/shared/chre_api_<name>.cc` for examples).
200 from platform-specific code at compile time by inheriting through
205 `Platform<Module>` header file found in `platform/include`, and implementation
228 2. Assuming the platform PAL implementations utilize CHPP and can communicate
249 While dynamic loading is a responsibility of the platform implementation and may