Home
last modified time | relevance | path

Searched refs:configuration (Results 1 – 25 of 179) sorted by relevance

12345678

/system/core/rootdir/
Dinit.usb.rc3 # USB configuration common for all android devices
37 # adb only USB configuration
38 # This is the fallback configuration if the
39 # USB manager fails to set a standard configuration
49 # USB accessory configuration
58 # USB accessory configuration, with adb
68 # audio accessory configuration
77 # audio accessory configuration, with adb
87 # USB and audio accessory configuration
96 # USB and audio accessory configuration, with adb
[all …]
Dinit.usb.configfs.rc21 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "adb"
27 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "mtp"
36 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "mtp_adb"
43 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "ptp"
52 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "ptp_adb"
59 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "accessory"
68 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "accessory_adb"
75 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "audiosource"
84 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "audiosource_adb"
91 write /config/usb_gadget/g1/configs/b.1/strings/0x409/configuration "accessory_audiosource"
[all …]
/system/linkerconfig/
DREADME.md5 Linkerconfig is a program to generate linker configuration based on the runtime
8 configuration file(s) to find out link relationship between libraries and
18 Linker configuration file can be used to add extra information while linkerconfig
19 creates linker configuration with the module. This module can be defined as
23 A linker configuration file(linker.config.json) is compiled into a protobuf at build time
25 For example, `/apex/com.android.art/etc/linker.config.pb` is a configuration for the `com.android.a…
DAndroid.bp85 "contents/configuration/*.cc",
204 "contents/tests/configuration/include",
207 "contents/tests/configuration/*_test.cc",
/system/teeui/test/example_config/
DREADME5 your test from. These files would be referred to as the configuration files.
40 configuration parameters set within this file.
43 configured with the values specific to the device. If no configuration is
85 test configuration directory you will run the test from.
93 It is possible to run the test as a binary and pass in configuration
/system/netd/server/
DTrafficController.cpp334 auto configuration = mConfigurationMap.readValue(CURRENT_STATS_MAP_CONFIGURATION_KEY); in tagSocket() local
335 if (!configuration.ok()) { in tagSocket()
337 strerror(configuration.error().code()), mConfigurationMap.getMap().get()); in tagSocket()
338 return -configuration.error().code(); in tagSocket()
340 if (configuration.value() != SELECT_MAP_A && configuration.value() != SELECT_MAP_B) { in tagSocket()
341 ALOGE("unknown configuration value: %d", configuration.value()); in tagSocket()
346 (configuration.value() == SELECT_MAP_A) ? mStatsMapA : mStatsMapB; in tagSocket()
972 auto configuration = mConfigurationMap.readValue(key); in dump() local
973 if (configuration.ok()) { in dump()
974 dw.println("current ownerMatch configuration: %d%s", configuration.value(), in dump()
[all …]
/system/core/rootdir/etc/
Dld.config.txt2 # Please update linker configuration generator instead.
Dld.config.legacy.txt2 # Please update linker configuration generator instead.
Dld.config.vndk_lite.txt2 # Please update linker configuration generator instead.
Dld.config.recovery.txt2 # Please update linker configuration generator instead.
/system/extras/simpleperf/demo/
D.clang-format1 # This clang-format configuration may be included in subdirectories to disable
/system/extras/
D.clang-format-none1 # This clang-format configuration may be included in subdirectories to disable
/system/sepolicy/tools/
DREADME17 property_contexts configuration file. Used as part of the policy
38 configuration and the device-specific one, and simultaneously
40 policy build process to merge and validate the configuration.
/system/extras/simpleperf/demo/SimpleperfExamplePureJava/
Dbuild.gradle1 // Top-level build file where you can add configuration options common to all sub-projects/modules.
/system/netd/libnetdbpf/
DBpfNetworkStats.cpp202 auto configuration = configurationMap.readValue(CURRENT_STATS_MAP_CONFIGURATION_KEY); in parseBpfNetworkStatsDetail() local
203 if (!configuration.ok()) { in parseBpfNetworkStatsDetail()
205 configuration.error().message().c_str()); in parseBpfNetworkStatsDetail()
206 return -configuration.error().code(); in parseBpfNetworkStatsDetail()
208 const char* statsMapPath = STATS_MAP_PATH[configuration.value()]; in parseBpfNetworkStatsDetail()
/system/extras/simpleperf/demo/SimpleperfExampleWithNative/
Dbuild.gradle1 // Top-level build file where you can add configuration options common to all sub-projects/modules.
/system/extras/simpleperf/demo/SimpleperfExampleOfKotlin/
Dbuild.gradle1 // Top-level build file where you can add configuration options common to all sub-projects/modules.
/system/update_engine/cros/
Dp2p_manager.cc118 P2PManagerImpl(Configuration* configuration,
210 P2PManagerImpl::P2PManagerImpl(Configuration* configuration, in P2PManagerImpl() argument
219 configuration_.reset(configuration != nullptr ? configuration in P2PManagerImpl()
720 P2PManager* P2PManager::Construct(Configuration* configuration, in Construct() argument
725 return new P2PManagerImpl(configuration, in Construct()
Dp2p_manager.h175 Configuration* configuration,
/system/extras/simpleperf/demo/JavaApi/app/
Dproguard-rules.pro2 # You can control the set of applied configuration files using the
/system/extras/simpleperf/demo/CppApi/app/
Dproguard-rules.pro2 # You can control the set of applied configuration files using the
/system/core/fastboot/fuzzy_fastboot/
DREADME.md6 configuration file to auto-generate device-specific tests for any device.
35 XML configuration file that is provided to Fuzzy Fastboot supports the necessary
40 Without a provided device XML configuration, Fuzzy Fastboot can only perform
52 With a provided XML device configuration, Fuzzy Fastboot will be able to generate
202 Here is a basic example configuration. This can also be found in the 'example' folder
275 - **--config=**: Specify the name of the configuration XML file. If omitted, only the generic tests…
347 ### Step 3: Create a device XML configuration
348 Without a device specific configuration file, Fuzzy Fastboot will have poor test
350 configuration file. Use the guide above to generate a configuration for your device.
351 Make sure to be as thorough as possible, and list everything in the configuration
[all …]
/system/sepolicy/
DREADME1 This directory contains the core Android SELinux policy configuration.
82 a mac_permissions.xml file(s) and configuration file in order to operate.
83 Details of the configuration file (keys.conf) can be found in the subsection
90 pem files. The configuration file is processed via m4.
/system/tools/hidl/
DAndroid.bp48 // This configuration is inherited by all hidl-gen-generated modules.
67 // This configuration is inherited by all hidl-gen-java modules
/system/sepolicy/prebuilts/api/26.0/public/
Dwificond.te25 # wificond writes out configuration files for wpa_supplicant/hostapd.

12345678