dmatest: restore ability to start test at module load and init
authorDan Williams <dan.j.williams@intel.com>
Thu, 7 Nov 2013 00:30:01 +0000 (16:30 -0800)
committerDan Williams <dan.j.williams@intel.com>
Thu, 14 Nov 2013 19:04:39 +0000 (11:04 -0800)
commita310d037b8d06755c62bb4878c00d19490af5550
tree7546e7c90f51bb2491558ce4772740ad9e903540
parent0adff800662f52d0ffc3e420db231769cb3fff13
dmatest: restore ability to start test at module load and init

1/ move 'run' control to a module parameter so we can do:
   modprobe dmatest run=1.  With this moved the rest of the debugfs
   boilerplate can go.

2/ Fix parameter initialization.  Previously the test was being started
   without taking the parameters into account in the built-in case.

Also killed off the '__' version of some routines.  The new rule is just
hold the lock when calling a *threaded_test() routine.

Acked-by: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Documentation/dmatest.txt
drivers/dma/dmatest.c