On Thu, Jun 29, 2017 at 10:30:58PM -0400, Sinan Kaya wrote: > Introducing memset test into dmatest. This change allows us to test > memset capable HW using the dmatest test procedure. The new dmatest > value for memset is 2 and it is not the default value. > > Memset support patch shares the same code path as the other dmatest > code to reuse as much as we can. > > The first value inside the source buffer is used as a pattern > to fill in the destination buffer space. > > Prior to running the test, source/destination buffers are initialized > in the current code. > > "The remaining bits are the inverse of a counter which increments by > one for each byte address." > > Memset test will fill in the upper bits of pattern with the inverse of > fixed counter value 1 as opposed to an incrementing value in a loop. > > An example run is as follows: > > echo dma0chan0 > /sys/module/dmatest/parameters/channel > echo 2 > /sys/module/dmatest/parameters/dmatest > echo 2000 > /sys/module/dmatest/parameters/timeout > echo 10 > /sys/module/dmatest/parameters/iterations > echo 1 > /sys/module/dmatest/parameters/run Applied, thanks -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
