The first approach to get dmatest module more flexible and easier to play with. The amount of patches could be reduced, but I would like to get a comments first on smaller pieces. The entire series creates dmatest.txt file in the Documentation folder. Similar description is scattered through the commit messages.
Module was tested on Intel Medfield and Lynxpoint systems with dw_dmac DMA controller embedded. Andy Shevchenko (10): dmatest: cancel thread immediately when asked for dmatest: allocate memory for pq_coefs from heap dmatest: create dmatest_info to keep test parameters dmatest: move dmatest_channels and nr_channels to dmatest_info dmatest: split test parameters to separate structure dmatest: run test via debugfs dmatest: return actual state in 'run' file dmatest: define MAX_ERROR_COUNT constant dmatest: gather test results in the linked list dmatest: append verify result to results Documentation/dmatest.txt | 81 +++++ drivers/dma/dmatest.c | 887 +++++++++++++++++++++++++++++++++++++++------- 2 files changed, 832 insertions(+), 136 deletions(-) create mode 100644 Documentation/dmatest.txt -- 1.8.2.rc0.22.gb3600c3 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
