Searched refs:low (Results 1 – 6 of 6) sorted by relevance
| /chre-3.4.0/doc/ |
| D | nanoapp_overview.md | 11 low-power hardware. Typically, nanoapps integrate with a component on the
120 example low-power tightly coupled memory (TCM, usually SRAM), versus a
125 purpose is to accomplish some low-level, device-specific functionality that is
|
| D | nanoapp_clients.md | 61 exposed at the Java level, and it can be used with other low-level beneath-HAL
|
| D | nanoapp_developer_guide.md | 7 security-sensitive trusted environment, similar to other low-level firmware, and
207 Even though CHRE aims to provide an environment for low-power and low-latency
|
| /chre-3.4.0/platform/shared/idl/ |
| D | host_messages.fbs | 246 /// Request from CHRE to enable direct access to data from the low-power
252 /// Notification from CHRE that it no longer needs direct access to low-power
|
| /chre-3.4.0/external/flatbuffers/include/flatbuffers/ |
| D | flatbuffers.h | 68 inline bool IsOutRange(const T &v, const T &low, const T &high) { in IsOutRange() argument
69 return (v < low) || (high < v); in IsOutRange()
74 inline bool IsInRange(const T &v, const T &low, const T &high) { in IsInRange() argument
75 return !IsOutRange(v, low, high); in IsInRange()
|
| /chre-3.4.0/chpp/ |
| D | README.md | 5 …ART, SPI) and enables an Android Context Hub (CHRE) running on a dedicated low-power processor to …
|
