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