1*49cdfc7eSAndroid Build Coastguard WorkerDevice Driver Testcases: 2*49cdfc7eSAndroid Build Coastguard Worker 3*49cdfc7eSAndroid Build Coastguard WorkerThese tests should always be run individually and never concurrently. Since 4*49cdfc7eSAndroid Build Coastguard Workerthese test will manipulate devices and may leave them in an unstable state, 5*49cdfc7eSAndroid Build Coastguard Workerthese tests should not be run when other important system tasks are being 6*49cdfc7eSAndroid Build Coastguard Workerperformed. These tests shouldn't be included in any system wide test scripts 7*49cdfc7eSAndroid Build Coastguard Workeras they may corrupt the test data from those tests. 8*49cdfc7eSAndroid Build Coastguard Worker 9*49cdfc7eSAndroid Build Coastguard WorkerTo build and execute these tests: 10*49cdfc7eSAndroid Build Coastguard Worker 11*49cdfc7eSAndroid Build Coastguard Worker1) change into each of the directories you want to test and run "make". 12*49cdfc7eSAndroid Build Coastguard Worker2) run the command 'insmod' on the .o file in the kernel space directory. 13*49cdfc7eSAndroid Build Coastguard WorkerNote: If the insmod command fails with a QM_MODULE error, the module functions 14*49cdfc7eSAndroid Build Coastguard Worker are outdated and need to be upgraded. 15*49cdfc7eSAndroid Build Coastguard Worker3) Run "lsmod" to make sure the modules is loaded. 16*49cdfc7eSAndroid Build Coastguard Worker4) Change to the user space program directory and run the *.sh file or the 17*49cdfc7eSAndroid Build Coastguard Worker program executable. 18*49cdfc7eSAndroid Build Coastguard Worker5) The results should be output to the display. 19*49cdfc7eSAndroid Build Coastguard Worker6) These tests will complete very quickly, usually in a few seconds so if the 20*49cdfc7eSAndroid Build Coastguard Worker system doesn't return from the test it's probably hung and a re-boot may be 21*49cdfc7eSAndroid Build Coastguard Worker required. 22