| /system/bt/gd/packet/parser/ |
| D | size.h | 33 Size(std::string dynamic) { in Size() argument
35 dynamic_.push_back(dynamic); in Size()
38 Size(int bits, std::string dynamic) { in Size() argument
41 dynamic_.push_back(dynamic); in Size()
|
| /system/tools/aidl/tests/lazy_test/ |
| D | README | 9 This will run tests on the test service (described below), the goal being to test the dynamic
36 to be a dynamic service). The server then joins the thread pool.
42 lines are only required for dynamic services.
|
| /system/bt/gd/l2cap/fuzz/ |
| D | fuzz_l2cap.cc | 90 bool dynamic = fdp.ConsumeBool(); in LLVMFuzzerTestOneInput() local
96 if (dynamic) { in LLVMFuzzerTestOneInput()
|
| /system/chre/build/variant/ |
| D | google_arm64_android.mk | 28 TARGET_BIN_LDFLAGS += -pie -laaudio -llog -ldl -Wl,--export-dynamic
|
| D | google_x86_linux.mk | 42 TARGET_BIN_LDFLAGS += -lpthread -lrt -ldl -Wl,--export-dynamic
|
| /system/media/camera/docs/ |
| D | CaptureResultKeys.mako | 17 <%include file="CameraMetadataKeys.mako" args="java_class='CaptureResult', xml_kind='dynamic'" />
|
| D | CaptureResultTest.mako | 27 % if entry.kind == 'dynamic' and entry.visibility in ("public", "java_public"):
|
| /system/sepolicy/prebuilts/api/29.0/public/ |
| D | kernel.te | 92 # dynamic linker when it re-executes /init to switch into the second stage.
93 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed
95 # domain (the source domain) to execute the dynamic linker (system_file type).
99 # The label for the dynamic linker is rootfs in the recovery partition. This is because
|
| /system/sepolicy/public/ |
| D | kernel.te | 100 # dynamic linker when it re-executes /init to switch into the second stage.
101 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed
103 # domain (the source domain) to execute the dynamic linker (system_file type).
107 # The label for the dynamic linker is rootfs in the recovery partition. This is because
|
| D | ueventd.te | 48 # the dynamic linker and shared libraries.
|
| /system/sepolicy/prebuilts/api/30.0/public/ |
| D | kernel.te | 95 # dynamic linker when it re-executes /init to switch into the second stage.
96 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed
98 # domain (the source domain) to execute the dynamic linker (system_file type).
102 # The label for the dynamic linker is rootfs in the recovery partition. This is because
|
| D | ueventd.te | 44 # the dynamic linker and shared libraries.
|
| /system/sepolicy/prebuilts/api/31.0/public/ |
| D | kernel.te | 100 # dynamic linker when it re-executes /init to switch into the second stage.
101 # Until Linux 4.8, the program interpreter (dynamic linker in this case) is executed
103 # domain (the source domain) to execute the dynamic linker (system_file type).
107 # The label for the dynamic linker is rootfs in the recovery partition. This is because
|
| /system/core/fs_mgr/libfiemap/ |
| D | README.md | 15 because it uses the same logic from dynamic partitions.
23 This is a super partition header that allows first-stage init to create dynamic
31 mounted, so first-stage init has no issues mapping dynamic partitions from
|
| /system/core/fs_mgr/ |
| D | README.overlayfs.md | 11 Limited memory systems use read-only types of file systems or dynamic
81 right-sizing of images and requires more free dynamic partition space.
96 - If a dynamic partition runs out of space, making a logical partition larger
100 - For implementation simplicity on retrofit dynamic partition devices,
|
| /system/chre/build/sys_support/qcom/ |
| D | uimage_v2.lcs | 114 .dynamic : { *(.dynamic) } : dynamic1 : phdr2
|
| D | uimage.lcs.toolv80 | 107 .dynamic : { *(.dynamic) } : phdr1 : dynamic1
|
| /system/chre/doc/ |
| D | nanoapp_overview.md | 51 before dynamic loading functionality is enabled. For example, the FeatureWorld
100 At the binary level, a preloaded nanoapp and fully dynamic nanoapp are
104 and `.so` file for the actual binary, a fully dynamic nanoapp has the header
107 can be used to create a fully dynamic nanoapp file from these components.
109 Instead of being stored on the device filesystem, fully dynamic nanoapps can be
|
| D | porting_guide.md | 114 include enabling dynamic loading (described in its own section below), and the
170 which is suitable for use as a binary interface, for example between two dynamic
214 If a PAL implementation is provided as a dynamic module in binary form, it can
249 While dynamic loading is a responsibility of the platform implementation and may
|
| /system/sepolicy/prebuilts/api/30.0/private/ |
| D | dumpstate.te | 53 # For dumping dynamic partition information.
|
| D | otapreopt_chroot.te | 14 # This is required for dynamic partitions.
|
| /system/chre/platform/shared/include/chre/platform/shared/ |
| D | loader_util.h | 166 typedef struct dynamic { struct
|
| /system/bt/main/ |
| D | BUILD.gn | 39 # Configure libbluetooth as either dynamic or static library
|
| /system/sepolicy/prebuilts/api/29.0/private/ |
| D | otapreopt_chroot.te | 14 # This is required for dynamic partitions.
|
| /system/security/keystore2/ |
| D | Android.bp | 123 // dynamic dependencies of rlibs to the device. This section should
|