• Home
Name Date Size #Lines LOC

..--

acpi/07-Sep-2024-975673

agp/07-Sep-2024-1,7341,044

base/07-Sep-2024-1,454808

block/07-Sep-2024-674429

cpufreq/07-Sep-2024-230127

dev_sim_framework/07-Sep-2024-897384

drm/07-Sep-2024-789485

include/07-Sep-2024-540350

locking/07-Sep-2024-11854

misc_modules/07-Sep-2024-568433

nls/07-Sep-2024-512330

pci/07-Sep-2024-1,044624

rcu/07-Sep-2024-10567

rtc/07-Sep-2024-442276

tbio/07-Sep-2024-1,093703

uaccess/07-Sep-2024-327184

usb/07-Sep-2024-1,021608

v4l/07-Sep-2024-91,81886,537

zram/07-Sep-2024-728531

MakefileD07-Sep-2024376 2013

READMED07-Sep-20241 KiB2218

README

1Device Driver Testcases:
2
3These tests should always be run individually and never concurrently.  Since
4these test will manipulate devices and may leave them in an unstable state,
5these tests should not be run when other important system tasks are being
6performed.  These tests shouldn't be included in any system wide test scripts
7as they may corrupt the test data from those tests.
8
9To build and execute these tests:
10
111) change into each of the directories you want to test and run "make".
122) run the command 'insmod' on the .o file in the kernel space directory.
13Note: If the insmod command fails with a QM_MODULE error, the module functions
14      are outdated and need to be upgraded.
153) Run "lsmod" to make sure the modules is loaded.
164) Change to the user space program directory and run the *.sh file or the
17   program executable.
185) The results should be output to the display.
196) These tests will complete very quickly, usually in a few seconds so if the
20   system doesn't return from the test it's probably hung and a re-boot may be
21   required.
22