Searched refs:Test (Results 1 – 25 of 161) sorted by relevance
1234567
/Linux-v5.10/Documentation/userspace-api/media/v4l/ |
D | ext-ctrls-image-source.rst | 41 Test pattern red colour component. 44 Test pattern green (next to red) colour component. 47 Test pattern blue colour component. 50 Test pattern green (next to blue) colour component.
|
/Linux-v5.10/drivers/ntb/test/ |
D | Kconfig | 3 tristate "NTB Ping Pong Test Client" 12 tristate "NTB Debugging Tool Test Client" 31 tristate "NTB MSI Test Client"
|
/Linux-v5.10/Documentation/admin-guide/media/ |
D | misc-cardlist.rst | 14 Test drivers 27 vivid Virtual Video Test Driver
|
/Linux-v5.10/tools/testing/selftests/futex/ |
D | README | 1 Futex Test 3 Futex Test is intended to thoroughly test the Linux kernel futex system call 36 Test output shall be easily parsable by both human and machine. Title and 61 o The Futex Test project adheres to the coding standards set forth by Linux
|
/Linux-v5.10/drivers/media/platform/xilinx/ |
D | Kconfig | 23 tristate "Xilinx Video Test Pattern Generator" 27 Driver for the Xilinx Video Test Pattern Generator
|
/Linux-v5.10/tools/testing/selftests/vm/ |
D | charge_reserved_hugetlb.sh | 415 echo Test normal case. 444 echo Test normal case with write. 464 echo Test more than reservation case. 481 echo Test more than cgroup limit case. 497 echo Test normal case, multiple cgroups. 543 echo Test normal case with write, multiple cgroups.
|
/Linux-v5.10/Documentation/dev-tools/kunit/ |
D | style.rst | 4 Test Style and Nomenclature 39 Test subsystems should be named after the code being tested, either after the 40 module (wherever possible), or after the directory or files being tested. Test 82 functionality being tested. Test suites can have shared initialisation and 86 Test suites are named after the subsystem they are part of. If a subsystem 124 Test Cases 155 Test Kconfig Entries 191 Test File and Module Names
|
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/cirrus/ |
D | cs89x0.rst | 46 5.2.1 Diagnostic Self-Test 47 5.2.2 Diagnostic Network Test 384 adapter and its network connection. Use the diagnostics 'Self Test' option to 386 assigned. You can use the diagnostics 'Network Test' to test the ability of the 406 * Select 'Self-Test' to test the adapter's basic functionality. 407 * Select 'Network Test' to test the network connection and cabling. 417 * IO Register Read/Write Test 422 * Shared Memory Test 428 * Interrupt Test 433 * EEPROM Test [all …]
|
/Linux-v5.10/Documentation/ABI/stable/ |
D | sysfs-driver-usb-usbtmc | 9 "Universal Serial Bus Test and Measurement Class Specification 23 "Universal Serial Bus Test and Measurement Class, Subclass
|
/Linux-v5.10/Documentation/litmus-tests/ |
D | README | 16 Test that an atomic RMW followed by a smp_mb__after_atomic() is 21 Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
/Linux-v5.10/drivers/usb/class/ |
D | Kconfig | 42 tristate "USB Test and Measurement Class support" 45 the USB.org specification for USB Test and Measurement devices
|
/Linux-v5.10/drivers/staging/hikey9xx/ |
D | TODO | 4 - Test drivers on Hikey 960;
|
/Linux-v5.10/Documentation/gpu/ |
D | amdgpu.rst | 131 RAS Basic Test 136 RAS Query Test 141 RAS Inject Test 145 RAS Disable Test
|
/Linux-v5.10/Documentation/driver-api/80211/ |
D | cfg80211.rst | 167 Test mode 171 :doc: Test mode
|
/Linux-v5.10/Documentation/dev-tools/kunit/api/ |
D | test.rst | 4 Test API
|
/Linux-v5.10/tools/memory-model/litmus-tests/ |
D | CoWW+poonceonce.litmus | 6 * Test of write-write coherence, that is, whether or not two successive
|
D | CoRR+poonceonce+Once.litmus | 6 * Test of read-read coherence, that is, whether or not two successive
|
D | CoRW+poonceonce+Once.litmus | 6 * Test of read-write coherence, that is, whether or not a read from
|
D | CoWR+poonceonce+Once.litmus | 6 * Test of write-read coherence, that is, whether or not a write to a
|
D | README | 6 Test of read-read coherence, that is, whether or not two 10 Test of read-write coherence, that is, whether or not a read 15 Test of write-read coherence, that is, whether or not a write 20 Test of write-write coherence, that is, whether or not two 24 Test of independent reads from independent writes with smp_mb() 32 Test of independent reads from independent writes with nothing
|
/Linux-v5.10/fs/unicode/ |
D | Kconfig | 12 tristate "Test UTF-8 normalization support"
|
/Linux-v5.10/drivers/pci/endpoint/functions/ |
D | Kconfig | 7 tristate "PCI Endpoint Test driver"
|
/Linux-v5.10/Documentation/litmus-tests/atomic/ |
D | Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 6 * Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
D | Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus | 6 * Test that an atomic RMW followed by a smp_mb__after_atomic() is
|
/Linux-v5.10/drivers/scsi/ufs/ |
D | Kconfig | 65 tristate "DesignWare pci support using a G210 Test Chip" 68 Synopsys Test Chip is a PHY for prototyping purposes. 92 tristate "DesignWare platform support using a G210 Test Chip" 95 Synopsys Test Chip is a PHY for prototyping purposes.
|
1234567