Home
last modified time | relevance | path

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

12345678910>>...15

/external/autotest/server/site_tests/platform_ExternalUsbPeripherals/
Dcontrol.detect.unplug_login_plug9 PURPOSE = "Servo based USB peripherals detection test"
19 This test uses servo to connect/disconnect servo USB hub before and
25 - USB detected peripherals are different than expected
27 - USB peripherals checks(usb_checks below) on command line fail
30 Set of four USB peripherals plugged
31 - USB headset
32 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
34 - USB mouse
35 - USB 3G modem
[all …]
Dcontrol.detect.login_unplug_closelid_openlid_plug9 PURPOSE = "Servo based USB boot stress test"
20 This test uses servo to connect/disconnect servo USB hub before and
26 - USB detected peripherals are different than expected
28 - USB peripherals checks(usb_checks below) on command line fail
31 Set of four USB peripherals plugged
32 - USB headset
33 - USB HD Webcam - should be Logitech HD Pro Webcam C920
34 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
35 - USB mouse
36 - USB 3G modem
[all …]
Dcontrol.detect9 PURPOSE = "Servo based USB boot stress test"
19 This test uses servo to connect/disconnect servo USB hub before and
25 - USB detected peripherals are different than expected
27 - USB peripherals checks(usb_checks below) on command line fail
30 Set of four USB peripherals plugged
31 - USB headset
32 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
34 - USB mouse
35 - USB 3G modem
[all …]
Dcontrol.detect.lid_close_open_short9 PURPOSE = "Servo based USB boot stress test"
19 This test uses servo to connect/disconnect servo USB hub before and
25 - USB detected peripherals are different than expected
27 - USB peripherals checks(usb_checks below) on command line fail
30 Set of four USB peripherals plugged
31 - USB headset
32 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
53 "\"USB PnP Sound Device: USB Audio|C-Media Electronics, Inc.* Audio\"",
56 # USB Audio Output devices
[all …]
Dcontrol.detect.crash_check_short9 PURPOSE = "Servo based USB boot stress test"
19 This test uses servo to connect/disconnect servo USB hub before and
25 - USB detected peripherals are different than expected
27 - USB peripherals checks(usb_checks below) on command line fail
30 Set of four USB peripherals plugged
31 - USB headset
32 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
52 "\"USB PnP Sound Device: USB Audio|C-Media Electronics, Inc.* Audio\"",
55 # USB Audio Output devices
[all …]
Dcontrol.detect.long_cycle9 PURPOSE = "Servo based USB peripheral detection test"
19 This test uses servo to connect/disconnect servo USB hub before and
25 - USB detected peripherals are different than expected
27 - USB peripherals checks(usb_checks below) on command line fail
30 Set of four USB peripherals plugged
31 - USB headset
32 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB stick with four partitions named ExFAT Ext4 FAT NTFS
57 "\"USB PnP Sound Device: USB Audio|C-Media Electronics, Inc.* Audio\"",
60 # USB Audio Output devices
[all …]
/external/autotest/server/site_tests/kernel_ExternalUsbPeripheralsDetectionTest/
Dcontrol9 PURPOSE = "Kernel USB detection test"
19 This test uses servo to connect USB devices.
20 This test verifies if drivers are created for each USB device or not.
23 - if USB device is not detected in lsusb command
24 - if driver for USB device is not created
25 - USB detected peripherals are different than expected
28 Set1 is set of four USB peripherals plugged
30 - USB 3G dongle
31 - USB HD Webcam - should be Logitech HD Pro Webcam C920
33 - USB Headphone
[all …]
Dcontrol.printer_hp9 PURPOSE = "Kernel USB detection test"
18 This test uses servo to connect USB devices.
19 This test verifies if drivers are created for each USB device or not.
22 - if USB device is not detected in lsusb command
23 - if driver for USB device is not created
24 - USB detected peripherals are different than expected
27 USB peripherals plugged
28 - USB printer
38 # Epson or HP USB printer
Dcontrol.printer_epson9 PURPOSE = "Kernel USB detection test"
18 This test uses servo to connect USB devices.
19 This test verifies if drivers are created for each USB device or not.
22 - if USB device is not detected in lsusb command
23 - if driver for USB device is not created
24 - USB detected peripherals are different than expected
27 USB peripherals plugged
28 - USB Epson XP-610 Series printer
/external/walt/docs/
DDevelopment.md3 … WALT usually takes up the only available USB connector on the phone, the typical development usin…
6 #### Using a USB hub and a USB Ethernet adapter
8 …reported to work much better with ADB. Android will recognize and use most USB-Ethernet adapters o…
10 1. With the phone connected you computer via USB, run `adb tcpip 5555` (you can replace 5555 with a…
11 1. Disconnect the phone from USB
12 1. Connect a USB hub (preferably powered) to the phone using a [USB-C to USB-A-female adapter](http…
13 or a USB-OTG adapter.
14 1. Use the hub to connect WALT, Ethernet adapter and whatever other USB peripherals you might want …
23 Since Android on ChromeOS has no access to USB, it requires a TCP bridge script implemented in [wal…
/external/autotest/docs/
Dfaft-pd.md3 PD FAFT is another set of firmware tests (FAFT), which targets testing USB-C and
10 The USB-C and PD stack is complex that involves multiple hardware/firmware:
12 * TCPM (USB Type-C Port Manager),
14 * TCPC (USB Type-C Port Controller), usually using proprietary firmware, in
20 The USB-C path also has other functions, like:
25 Many USB-C bugs are mysterious or flaky, like CCD not being detected, USB
34 power adapter, a USB-C hub, a USB-C debug accessory, a USB-C protocol converter,
35 a USB-C monitor, etc. The first version of PD FAFT uses
101 * If DUT passes the same test on a USB-C debug accessory
120 ### Multiple USB-C ports {#multiple-usb-c-ports}
[all …]
Dfaft-how-to-run-doc.md12 - [Installing Test Image onto USB Stick](#image-onto-usb)
30 - Real test of physical hardware, like USB plug-in, Ctrl-D key press
40 software (on a USB drive).
70 - USB type-A to USB micro cable for DUT connection (~ 2' in length)
71 - USB type-A to USB micro cable for test controller connection (~ 4' - 6' in length)
73 - USB drive (flashed with the appropriate OS image)
86 1. Connect one end (micro USB) of the servo micro to servoV4 using a micro USB to USB cable.
88 3. Connect the USB type A cable of the servoV4 to the DUT.
89 4. Prepare a USB flash drive with valid Chrome OS image and plug into the USB port of the servo as …
90 5. Connect the micro USB port of the servo to the host machine (typically your workstation).
[all …]
/external/autotest/server/site_tests/audio_AudioRoutingUSB/
Dcontrol9 PURPOSE = 'Verify audio is routed to USB headset correctly.'
11 After a USB headset is plugged in, CRAS should route the audio
12 to the new device. After the USB headset is unplugged, the audio
22 This test uses servo to simulate plugging/unplugging a USB headset. Before
23 running the test, a USB headset should be plugged into DUT_USB (TYPE A/J4),
24 and DUT_IN (TYPE MICRO-B/J5) should be connected to a USB port on the device.
/external/autotest/server/site_tests/firmware_SelfSignedBoot/
Dcontrol14 3. A USB disk should be plugged-in, which contains a Chrome OS Test Image.
17 1. Ctrl-U boots to USB image with recovery keys.
18 2. Enabling rec mode, if it doesnt boot to USB image.
19 3. Ctrl-U doesnt boot to USB image after it resigned with SSD keys.
30 This test requires a USB disk plugged-in, which contains a Chrome OS test
33 pressing Ctrl-U on developer screen should not boot the USB disk. On resigning
35 boot the USB disk. More details: Refer to chrome-os-partner issue 5954(#37).
/external/arm-trusted-firmware/docs/plat/
Dpoplar.rst19 USB Two USB 2.0 ports One USB 3.0 ports
20 CONSOLE USB-micro port for console support
82 - Copy l-loader/fastboot.bin to a FAT partition on a USB pen drive.
84 - Plug the USB pen drive to any of the USB2 ports
162 starting USB...
163 USB0: USB EHCI 1.00
164 scanning bus 0 for devices... 1 USB Device(s) found
165 USB1: USB EHCI 1.00
166 scanning bus 1 for devices... 4 USB Device(s) found
170 USB device 0:
/external/autotest/server/site_tests/firmware_InvalidUSB/
Dcontrol9 PURPOSE = "Servo based booting an invalid USB image test"
10 CRITERIA = "This test will fail if the invalid USB boots successfully"
20 This test requires a USB disk plugged-in, which contains a Chrome OS test
22 USB image and tries to boot into it. A failure is expected. It then
23 restores the USB image and boots into it again.
/external/autotest/server/site_tests/firmware_DevBootUSB/
Dcontrol9 PURPOSE = "Press Ctrl-U on developer screen to boot USB disk"
10 CRITERIA = "This test will fail if firmware does not boot USB disk"
20 This test requires a USB disk plugged-in, which contains a Chrome OS test
23 screen should not boot the USB disk. When dev_boot_usb=1, pressing Ctrl-U
24 should boot the USB disk.
/external/autotest/server/site_tests/power_USBHotplugInSuspend/
Dcontrol13 PURPOSE = "Tests USB hot-plugging during suspend."
14 CRITERIA = "Fails if hotplug of a USB device during suspend is not detected."
22 This tests both hotplug insertion and removal of a USB device while the DUT
24 Servo is then used to power on/off the USB key. After the client resumes, it
/external/autotest/client/site_tests/suite_HWQual/
DREADME.txt46 - Install the Chrome OS test image on the DUT. The USB test image is
53 - Plug a USB storage device into the Autotest server. Note that all
54 data on your USB stick will be destroyed.
56 - Unmount any mounts on the USB device.
58 - Copy the USB image to a USB storage device by executing:
63 - where /dev/sdX is your USB device.
65 - Plug the USB device into the DUT and boot from it.
76 don't boot from USB.
121 - Plug high-speed high-capacity storage devices in all USB and SD Card
185 - Run the DUT on AC. Plug a power draw USB dongle in each USB port.
[all …]
/external/perfetto/docs/data-sources/
Dbattery-counters.md37 #### Measuring charge while plugged on USB
40 the battery. If the device is plugged to a USB cable, you will likely observe
48 * Using specialized USB hubs that allow to electrically disconnect the USB ports
52 * On rooted phones the power management IC driver allows to disconnect the USB
53 charging while keeping the USB data link active. This feature is
57 Note that in most devices the kernel USB driver holds a wakelock to keep the
58 USB data link active, so the device will never fully suspend even when turning
/external/cpuinfo/test/dmesg/
Dlenovo-a6600-plus.log342 [ 2.926099] (0)[1:init][name:g_android&][g_android][USB]enable_store: device_attr->attr.name: e…
345 [ 2.926187] (0)[60:kworker/0:1][name:g_android&][g_android][USB]enable_store: enable 0->0 case …
347 [ 2.926238] (0)[60:kworker/0:1][name:g_android&][g_android][USB]android_work: is_hwconnected=0
348 [ 2.926258] (0)[60:kworker/0:1][name:g_android&][g_android][USB]android_work: did not send ueve…
349 [ 2.926329] (0)[60:kworker/0:1][name:g_android&][g_android][USB]android_work: sent uevent USB_S…
350 [ 2.926345] (0)[60:kworker/0:1][name:g_android&][g_android][USB]android_work: did not send zero…
351 [ 2.950259] (0)[1:init][name:g_android&][g_android][USB]functions_store
352 [ 2.950289] (0)[1:init][name:g_android&][g_android][USB]functions_store: name = mtp
353 [ 2.950302] (0)[1:init][name:g_android&][g_android][USB]android_enable_function: name = mtp, f-…
354 [ 2.950313] (0)[1:init][name:g_android&][g_android][USB]android_enable_function: name = mtp, f-…
[all …]
/external/autotest/server/site_tests/firmware_RecoveryStress/
Dcontrol.rec_force_mrc10 CRITERIA = "This test will fail if DUT failed to boot into USB OS"
19 - Recovery boot with USB stick using power_state:rec_force_mrc
20 - USB stick is plugged into Servo board, not DUT
Dcontrol.rec10 CRITERIA = "This test will fail if DUT failed to boot into USB OS"
19 - Recovery boot with USB stick using power_state:rec
20 - USB stick is plugged into Servo board, not DUT
/external/autotest/server/site_tests/firmware_ECUsbPorts/
Dcontrol9 PURPOSE = "Servo based EC USB ports test"
10 CRITERIA = "This test will fail if EC USB port control misbehalved."
20 This test check if EC can correctly controls USB port mode.
/external/autotest/server/site_tests/platform_ExternalUSBStress/
Dcontrol9 PURPOSE = "Servo based USB stress test"
10 CRITERIA = "This test will fail if the device fails to detect USB changes."
18 This test uses servo to simulate USB connect/removal,

12345678910>>...15