From patchwork Wed Oct 25 06:32:55 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Vinod Koul X-Patchwork-Id: 10025935 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 4A17960381 for ; Wed, 25 Oct 2017 06:28:45 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 3B6BA28AED for ; Wed, 25 Oct 2017 06:28:45 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 3039628AEF; Wed, 25 Oct 2017 06:28:45 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=2.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id B84B428AED for ; Wed, 25 Oct 2017 06:28:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932152AbdJYG2o (ORCPT ); Wed, 25 Oct 2017 02:28:44 -0400 Received: from mga03.intel.com ([134.134.136.65]:21796 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751421AbdJYG2n (ORCPT ); Wed, 25 Oct 2017 02:28:43 -0400 Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2017 23:28:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,430,1503385200"; d="scan'208";a="1029076090" Received: from vkoul-udesk7.iind.intel.com ([10.223.84.143]) by orsmga003.jf.intel.com with ESMTP; 24 Oct 2017 23:28:41 -0700 From: Vinod Koul To: dmaengine@vger.kernel.org Cc: linux-doc@vger.kernel.org, Jonathan Corbet , Vinod Koul Subject: [PATCH 4/5] dmaengine: doc: ReSTize dmatest doc Date: Wed, 25 Oct 2017 12:02:55 +0530 Message-Id: <1508913176-812-5-git-send-email-vinod.koul@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1508913176-812-1-git-send-email-vinod.koul@intel.com> References: <1508913176-812-1-git-send-email-vinod.koul@intel.com> Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP This converts dmatest file with some format changes for RST style Signed-off-by: Vinod Koul --- .../dmaengine/{dmatest.txt => dmatest.rst} | 58 ++++++++++++++++++---- Documentation/dmaengine/index.rst | 10 ++++ 2 files changed, 57 insertions(+), 11 deletions(-) rename Documentation/dmaengine/{dmatest.txt => dmatest.rst} (80%) diff --git a/Documentation/dmaengine/dmatest.txt b/Documentation/dmaengine/dmatest.rst similarity index 80% rename from Documentation/dmaengine/dmatest.txt rename to Documentation/dmaengine/dmatest.rst index fb683c72dea8..923b343ef1c1 100644 --- a/Documentation/dmaengine/dmatest.txt +++ b/Documentation/dmaengine/dmatest.rst @@ -1,11 +1,12 @@ - DMA Test Guide - ============== +DMA Test Guide +============== - Andy Shevchenko +Andy Shevchenko This small document introduces how to test DMA drivers using dmatest module. - Part 1 - How to build the test module +Part 1 - How to build the test module +------------------------------------- The menuconfig contains an option that could be found by following path: Device Drivers -> DMA Engine support -> DMA Test client @@ -13,12 +14,19 @@ The menuconfig contains an option that could be found by following path: In the configuration file the option called CONFIG_DMATEST. The dmatest could be built as module or inside kernel. Let's consider those cases. - Part 2 - When dmatest is built as a module... +Part 2 - When dmatest is built as a module +------------------------------------------ Example of usage: - % modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run=1 + +:: + + % modprobe dmatest channel=dma0chan0 timeout=2000 iterations=1 run=1 ...or: + +:: + % modprobe dmatest % echo dma0chan0 > /sys/module/dmatest/parameters/channel % echo 2000 > /sys/module/dmatest/parameters/timeout @@ -27,10 +35,15 @@ Example of usage: ...or on the kernel command line: +:: + dmatest.channel=dma0chan0 dmatest.timeout=2000 dmatest.iterations=1 dmatest.run=1 -Hint: available channel list could be extracted by running the following -command: +..hint:: available channel list could be extracted by running the following + command: + +:: + % ls -1 /sys/class/dma/ Once started a message like "dmatest: Started 1 threads using dma0chan0" is @@ -40,6 +53,9 @@ stops. Note that running a new test will not stop any in progress test. The following command returns the state of the test. + +:: + % cat /sys/module/dmatest/parameters/run To wait for test completion userpace can poll 'run' until it is false, or use @@ -51,14 +67,22 @@ to complete before exiting. Note that if 'iterations' is set to 'infinite' then waiting is disabled. Example: + +:: + % modprobe dmatest run=1 iterations=42 wait=1 % modprobe -r dmatest + ...or: + +:: + % modprobe dmatest run=1 iterations=42 % cat /sys/module/dmatest/parameters/wait % modprobe -r dmatest - Part 3 - When built-in in the kernel... +Part 3 - When built-in in the kernel +------------------------------------ The module parameters that is supplied to the kernel command line will be used for the first performed test. After user gets a control, the test could be @@ -67,15 +91,24 @@ section "Part 2 - When dmatest is built as a module..." In both cases the module parameters are used as the actual values for the test case. You always could check them at run-time by running + +:: + % grep -H . /sys/module/dmatest/parameters/* - Part 4 - Gathering the test results +Part 4 - Gathering the test results +----------------------------------- Test results are printed to the kernel log buffer with the format: -"dmatest: result : : '' with src_off= dst_off= len= ()" +:: + + "dmatest: result : : '' with src_off= dst_off= len= ()" Example of output: + +:: + % dmesg | tail -n 1 dmatest: result dma0chan0-copy0: #1: No errors with src_off=0x7bf dst_off=0x8ad len=0x3fea (0) @@ -85,6 +118,9 @@ or status. A test thread also emits a summary line at completion listing the number of tests executed, number that failed, and a result code. Example: + +:: + % dmesg | tail -n 1 dmatest: dma0chan0-copy0: summary 1 test, 0 failures 1000 iops 100000 KB/s (0) diff --git a/Documentation/dmaengine/index.rst b/Documentation/dmaengine/index.rst index ffc2b797938c..fae852922a49 100644 --- a/Documentation/dmaengine/index.rst +++ b/Documentation/dmaengine/index.rst @@ -27,6 +27,16 @@ API of the DMAEngine. This is applicable only for slave DMA usage only. client +DMA Test documentation +---------------------- + +This book introduces how to test DMA drivers using dmatest module. + +.. toctree:: + :maxdepth: 1 + + dmatest + .. only:: subproject Indices