Home
last modified time | relevance | path

Searched refs:platform (Results 1 – 25 of 321) sorted by relevance

12345678910>>...13

/system/chre/platform/
Dplatform.mk24 SLPI_CFLAGS += -I$(SLPI_PREFIX)/platform/inc
25 SLPI_CFLAGS += -I$(SLPI_PREFIX)/platform/inc/HAP
26 SLPI_CFLAGS += -I$(SLPI_PREFIX)/platform/inc/a1std
27 SLPI_CFLAGS += -I$(SLPI_PREFIX)/platform/inc/stddef
28 SLPI_CFLAGS += -I$(SLPI_PREFIX)/platform/rtld/inc
39 SLPI_SEE_CFLAGS += -I$(SLPI_PREFIX)/chre/chre/src/system/chre/platform/slpi
91 SLPI_SRCS += platform/shared/assert.cc
92 SLPI_SRCS += platform/shared/chre_api_audio.cc
93 SLPI_SRCS += platform/shared/chre_api_core.cc
94 SLPI_SRCS += platform/shared/chre_api_gnss.cc
[all …]
/system/chre/
DAndroid.bp52 "platform/shared/include",
59 "platform/shared/host_protocol_common.cc",
276 "platform/shared/pal_system_api.cc",
277 "platform/linux/assert.cc",
278 "platform/linux/fatal_error.cc",
279 "platform/linux/memory.cc",
280 "platform/linux/pal_gnss.cc",
281 "platform/linux/pal_wifi.cc",
282 "platform/linux/pal_wwan.cc",
283 "platform/linux/platform_log.cc",
[all …]
DREADME.md4 Runtime Environment (CHRE), which is Android’s platform for developing always-on
58 - ``core/``: Common CHRE framework code, which is applicable to every platform
59 (contrast to ``platform/``)
67 and tests (these PALs may optionally be used by the platform implementation)
68 - ``platform/``: Code related to the implementation of CHRE on a particular
69 platform/device (compare to ``core/``), divided into sub-folders as follows:
70 - ``platform/include``: The interface between common code in ``core/`` and
71 platform-specific code implemented elsewhere in ``platform/``
72 - ``platform/shared``: Code that may apply to multiple platforms, but is not
75 folder contains source files translating from the C++ platform abstractions
[all …]
DAndroid.mk65 platform/shared/host_protocol_common.cc
72 system/chre/platform/shared/include \
73 system/chre/platform/slpi/include \
/system/chre/build/sys_support/qcom/
Dchre.scons167 "${BUILD_ROOT}/chre/chre/src/system/chre/platform/include",
168 "${BUILD_ROOT}/chre/chre/src/system/chre/platform/shared/include",
169 "${BUILD_ROOT}/chre/chre/src/system/chre/platform/slpi",
170 "${BUILD_ROOT}/chre/chre/src/system/chre/platform/slpi/include",
171 "${BUILD_ROOT}/chre/chre/src/system/chre/platform/slpi/see/include",
188 env.RequirePublicApi(platform_public_apis, area='platform')
289 # CHRE platform-specific implementation
290 "${BUILDPATH}/system/chre/platform/shared/chre_api_audio.cc",
291 "${BUILDPATH}/system/chre/platform/shared/chre_api_core.cc",
292 "${BUILDPATH}/system/chre/platform/shared/chre_api_gnss.cc",
[all …]
/system/chre/doc/
Dporting_guide.md6 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
[all …]
Dframework_overview.md16 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
[all …]
/system/sepolicy/prebuilts/api/31.0/private/
Dplatform_app.te2 ### Apps signed with the platform key.
35 # This is a performance optimization that allows platform apps to bypass the FUSE layer
71 # Allow platform apps to log via statsd.
82 # allow platform apps to use UDP sockets provided by the system server but not
87 # allow platform apps to connect to the property service
90 # allow platform apps to read keyguard.no_require_sim
93 # allow platform apps to read qemu.hw.mainkeys
96 # allow platform apps to create symbolic link
102 # Allow platform apps to act as Perfetto producers.
/system/sepolicy/private/
Dplatform_app.te2 ### Apps signed with the platform key.
35 # This is a performance optimization that allows platform apps to bypass the FUSE layer
71 # Allow platform apps to log via statsd.
82 # allow platform apps to use UDP sockets provided by the system server but not
87 # allow platform apps to connect to the property service
90 # allow platform apps to read keyguard.no_require_sim
93 # allow platform apps to read qemu.hw.mainkeys
96 # allow platform apps to create symbolic link
102 # Allow platform apps to act as Perfetto producers.
/system/sepolicy/prebuilts/api/29.0/private/
Dplatform_app.te2 ### Apps signed with the platform key.
35 # This is a performance optimization that allows platform apps to bypass the FUSE layer
73 # Allow platform apps to interact with gpuservice
76 # Allow platform apps to log via statsd.
87 # allow platform apps to use UDP sockets provided by the system server but not
92 # allow platform apps to connect to the property service
95 # allow platform apps to create symbolic link
/system/sepolicy/prebuilts/api/30.0/private/
Dplatform_app.te2 ### Apps signed with the platform key.
35 # This is a performance optimization that allows platform apps to bypass the FUSE layer
72 # Allow platform apps to interact with gpuservice
75 # Allow platform apps to log via statsd.
86 # allow platform apps to use UDP sockets provided by the system server but not
91 # allow platform apps to connect to the property service
94 # allow platform apps to create symbolic link
/system/chre/chpp/
DAndroid.bp88 "platform/pal_api.c",
89 "platform/linux/link.c",
90 "platform/linux/memory.c",
91 "platform/linux/notifier.c",
92 "platform/shared/crc.c",
95 "platform/linux/include",
DQUICKSTART.md3 This guide focuses on integrating and porting CHPP to your desired platform. For implementation det…
9 Implement the platform-specific functionality utilized by CHPP. These can be found in chpp/platform…
16 1. CRC32 (a half-byte algorithm is provided in platform/shared, but it is recommended to use a plat…
33 In addition, the system must implement and initialize the platform-specific linkParams data structu…
41 1. Initialize the platform-specific linkParams struct (part of the transport struct)
54 1. Deallocate the transportContext, appContext, and the platform-specific linkParams structs
/system/extras/module_ndk_libs/libnativehelper/
Dlibnativehelper.map.txt8 # JNI Invocation methods available to platform and apps.
17 LIBNATIVEHELPER_PLATFORM { # platform-only
/system/bt/gd/proto/
DAndroid.bp21 "//apex_available:platform",
38 "//apex_available:platform",
56 "//apex_available:platform",
/system/tools/aidl/build/
Dmessage_check_equality_release.txt2 # ERROR: AIDL API change detected on a released platform #
4 Above AIDL file(s) has changed and this is NEVER allowed on a release platform
/system/libartpalette/
DAndroid.bp17 // libartpalette-system is the implementation of the platform
74 // Definition of the extended SDK offered by the platform for mainline modules.
80 name: "platform-mainline-sdk",
108 name: "platform-mainline-test-exports",
/system/core/libprocessgroup/
DAndroid.bp24 "//apex_available:platform",
71 "//apex_available:platform",
/system/sepolicy/prebuilts/api/28.0/private/
Dseapp_contexts102 user=_app seinfo=platform name=com.android.traceur domain=traceur_app type=app_data_file levelFrom=…
103 user=system seinfo=platform domain=system_app type=system_app_data_file
104 user=bluetooth seinfo=platform domain=bluetooth type=bluetooth_data_file
105 user=nfc seinfo=platform domain=nfc type=nfc_data_file
106 user=secure_element seinfo=platform domain=secure_element levelFrom=all
107 user=radio seinfo=platform domain=radio type=radio_data_file
109 user=shell seinfo=platform domain=shell name=com.android.shell type=shell_data_file
113 user=_app seinfo=platform domain=platform_app type=app_data_file levelFrom=user
Dplatform_app.te2 ### Apps signed with the platform key.
35 # This is a performance optimization that allows platform apps to bypass the FUSE layer
72 # allow platform apps to use UDP sockets provided by the system server but not
77 # allow platform apps to connect to the property service
/system/extras/simpleperf/scripts/
Dsimpleperf_utils.py40 return sys.platform == 'win32' or sys.platform == 'cygwin'
44 return sys.platform == 'darwin'
131 elif sys.platform == 'darwin': # OSX
172 lambda platform: 'toolchains/llvm/prebuilt/%s-x86_64/bin/llvm-objdump' % platform,
177 lambda platform: 'toolchains/llvm/prebuilt/%s-x86_64/bin/llvm-readelf' % platform,
182 … lambda platform: 'toolchains/llvm/prebuilt/%s-x86_64/bin/llvm-symbolizer' % platform,
208 platform = get_platform()
209 sdk_path = os.path.join(home, cls.DEFAULT_SDK_PATH[platform].replace('/', os.sep))
235 def _get_binutils_path_in_ndk(cls, toolname: str, arch: Optional[str], platform: str
249 path = 'toolchains/llvm/prebuilt/%s-x86_64/bin/%s' % (platform, name)
[all …]
/system/timezone/
DOWNERS1 include platform/libcore:/OWNERS
/system/hardware/interfaces/
DOWNERS1 include platform/hardware/interfaces:/OWNERS
/system/core/libnetutils/
DOWNERS1 include platform/system/netd:/OWNERS
/system/logging/rust/
DOWNERS1 include platform/prebuilts/rust:/OWNERS

12345678910>>...13