linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 2/2] dmaengine: dmatest: add support for memset test
Date: Tue, 18 Jul 2017 21:56:03 +0530	[thread overview]
Message-ID: <20170718162602.GW3053@localhost> (raw)
In-Reply-To: <1498789858-18583-2-git-send-email-okaya@codeaurora.org>

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

  reply	other threads:[~2017-07-18 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  2:30 [PATCH V3 1/2] dmaengine: qcom_hidma: introduce memset support Sinan Kaya
2017-06-30  2:30 ` [PATCH V3 2/2] dmaengine: dmatest: add support for memset test Sinan Kaya
2017-07-18 16:26   ` Vinod Koul [this message]
2017-07-18 16:19 ` [PATCH V3 1/2] dmaengine: qcom_hidma: introduce memset support Vinod Koul
2017-07-18 16:26   ` Sinan Kaya
2017-07-18 16:47     ` Vinod Koul
2017-07-19  4:03       ` Vinod Koul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170718162602.GW3053@localhost \
    --to=vinod.koul@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).