Home
last modified time | relevance | path

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

/bionic/libc/kernel/uapi/linux/
Dedd.h93 __u8 device; member
100 __u8 device; member
135 __u8 device; member
150 __u8 device; member
Dx25.h54 char device[200 - sizeof(unsigned long)]; member
67 char device[200]; member
Dnetrom.h34 char device[16]; member
Dsoundcard.h265 short device; member
271 int device; member
300 int device; member
674 …_MIDIOUT(device,byte) { _SEQ_NEEDBUF(4); _seqbuf[_seqbufptr] = SEQ_MIDIPUTC; _seqbuf[_seqbufptr + … argument
Drose.h71 char device[16]; member
Dptp_clock.h72 struct ptp_clock_time device; member
Dblktrace_api.h100 __u32 device; member
Dfd.h51 unsigned int device, head, track; member
Dmedia.h89 __u32 device; member
/bionic/libc/tools/
Dndk_missing_symbols.py36 device = (symbols.GetFromElf(os.path.join(tmp_dir, 'libc.so')) |
40 missing_symbols = current - device
/bionic/docs/
Dlibc_assembler.md16 When benchmarking, it's best to verify on the latest Pixel device supported.
39 and pushed on to the device. The commands below show how to do this.
94 that if the device does not get up to the maximum cpu frequency, the results
99 Another potential issue is that the device can overheat when running the
100 benchmarks. To avoid this, you can run the device in a cool environment,
101 or choose a device that is less likely to overheat. To detect these kind
119 on device. If you are trying to run this using adb directly from a host
Ddefines.md20 of the OS and needs to behave differently on the host than on the device.
Dnative_allocator.md19 `device/<DEVICE_NAME>/` or in a sub directory.
126 to specify a device.
/bionic/libfdtrack/
DAndroid.bp25 test_suites: ["device-tests"],
/bionic/tests/
Dutils.h106 dev_t device; member
142 record.device = makedev(dev_major, dev_minor); in parse_maps()
DAndroid.bp761 // Tests for the device using bionic's .so. Run with:
1026 // Tests for the device linked against bionic's static library. Run with:
/bionic/libc/kernel/uapi/sound/
Dasound.h80 unsigned int device; member
273 unsigned int device; member
575 unsigned int device; member
633 int device; member
795 unsigned int device; member
Demu10k1.h244 unsigned int device; member
/bionic/
DREADME.md186 Note that if you're actually just trying to expose device-specific headers to
187 build your device drivers, you shouldn't modify bionic. Instead use
203 required for the device. Tests, additional developer tools, and various other
284 ### Coverage from device tests
294 `acov` will pull all coverage information from the device, push it to the right
Dandroid-changes-for-ndk-developers.md298 it is not present in that exact location on the device.
302 cannot be found on the device.
316 device. There are broken third-party toolchains/build systems that use
321 libraries as the location may change from device to device.
/bionic/libc/malloc_debug/
DREADME_marshmallow_and_earlier.md17 run as root on the device.
52 might cause timeouts when trying to start a device.
DREADME.md611 inner layer of quoting is sent to the device, to make 'backtrace guard'
647 If you do have a rooted device, you can enable malloc debug for a specific
711 using the path the .so file would have on the device. So if your .so file
712 is at `/data/app/.../lib/arm/libx.so` on the device, it will need to be at
/bionic/benchmarks/
DAndroid.bp77 // Build benchmarks for the device (with bionic's .so). Run with:
DREADME.md86 (e.g. Toybox's `true` and `sh -c true`). Run it on a device like so:
145 `taskset` utility. e.g. A Pixel 3 device has 4 Kryo 385 Silver cores followed by 4 Gold cores:
/bionic/libc/
DAndroid.bp1763 "//device/generic/goldfish-opengl:__subpackages__",