From patchwork Mon Feb 24 11:09:31 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Popov X-Patchwork-Id: 3708641 X-Patchwork-Delegate: vinod.koul@intel.com Return-Path: X-Original-To: patchwork-dmaengine@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 2D7DDBF13A for ; Mon, 24 Feb 2014 11:09:56 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 42CB620149 for ; Mon, 24 Feb 2014 11:09:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 5C9D02013A for ; Mon, 24 Feb 2014 11:09:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752274AbaBXLJy (ORCPT ); Mon, 24 Feb 2014 06:09:54 -0500 Received: from mail-la0-f44.google.com ([209.85.215.44]:49714 "EHLO mail-la0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751830AbaBXLJw (ORCPT ); Mon, 24 Feb 2014 06:09:52 -0500 Received: by mail-la0-f44.google.com with SMTP id hr13so2500068lab.17 for ; Mon, 24 Feb 2014 03:09:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=556HNEivxILe266Sq3FF/ytukskcAXcjieYRjNTbuuI=; b=0ywcJbftl52PHk7ps9ae4w11vqGTOyDUjqp2V+rgjywy1bymJfsvryW2YzS3iHxury tGWV8HWX83jttG6gSJcug+f9V/i8CwSfSfrtouXCf56S6f8I9kUIdhhzh3i6DByDtSXm bKEruuH5btGfHMBxg7ci7kzMI5TN1UzOuZs5QyezIBgz6/q6sdHkVbz2tGf4f0cW0UG5 6/J3okSL8LfBEf+P4Yy2DDyV+GQrW/JsXTyyU3Dmssgp9Kz/m4ETS4VnqgNXGk4V+CS/ fAJU0CKyFahQgTSPzJyrGN4oyy9rSWJKKazPczJMolY/QOEmFAD951S9uGZgJLXcU2sp F9iA== X-Received: by 10.112.170.234 with SMTP id ap10mr11118693lbc.23.1393240191220; Mon, 24 Feb 2014 03:09:51 -0800 (PST) Received: from a13xCCC.localdomain (mail.tecon.ru. [89.175.104.62]) by mx.google.com with ESMTPSA id gb8sm18245648lbc.13.2014.02.24.03.09.48 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 24 Feb 2014 03:09:50 -0800 (PST) From: Alexander Popov To: Gerhard Sittig , Dan Williams , Vinod Koul , Lars-Peter Clausen , Arnd Bergmann , Anatolij Gustschin , Alexander Popov , linuxppc-dev@lists.ozlabs.org, dmaengine@vger.kernel.org Cc: devicetree@vger.kernel.org Subject: [PATCH RFC v8 4/5] dma: mpc512x: add device tree binding document Date: Mon, 24 Feb 2014 15:09:31 +0400 Message-Id: <1393240172-18769-5-git-send-email-a13xp0p0v88@gmail.com> X-Mailer: git-send-email 1.7.11.3 In-Reply-To: <1393240172-18769-1-git-send-email-a13xp0p0v88@gmail.com> References: <1393240172-18769-1-git-send-email-a13xp0p0v88@gmail.com> Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org X-Spam-Status: No, score=-6.8 required=5.0 tests=BAYES_00, DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED, FREEMAIL_FROM, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, T_DKIM_INVALID, UNPARSEABLE_RELAY autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP From: Gerhard Sittig introduce a device tree binding document for the MPC512x DMA controller Signed-off-by: Gerhard Sittig [ a13xp0p0v88@gmail.com: turn this into a separate patch ] --- .../devicetree/bindings/dma/mpc512x-dma.txt | 55 ++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 Documentation/devicetree/bindings/dma/mpc512x-dma.txt diff --git a/Documentation/devicetree/bindings/dma/mpc512x-dma.txt b/Documentation/devicetree/bindings/dma/mpc512x-dma.txt new file mode 100644 index 0000000..a4867d5 --- /dev/null +++ b/Documentation/devicetree/bindings/dma/mpc512x-dma.txt @@ -0,0 +1,55 @@ +* Freescale MPC512x DMA Controller + +The DMA controller in the Freescale MPC512x SoC can move blocks of +memory contents between memory and peripherals or memory to memory. + +Refer to the "Generic DMA Controller and DMA request bindings" description +in the dma.txt file for a more detailled discussion of the binding. The +MPC512x DMA engine binding follows the common scheme, but doesn't provide +support for the optional channels and requests counters (those values are +derived from the detected hardware features) and has a fixed client +specifier length of 1 integer cell (the value is the DMA channel, since +the DMA controller uses a fixed assignment of request lines per channel). + + +DMA controller node properties: + +Required properties: +- compatible: should be "fsl,mpc5121-dma" +- reg: address and size of the DMA controller's register set +- interrupts: interrupt spec for the DMA controller + +Optional properties: +- #dma-cells: must be <1>, describes the number of integer cells + needed to specify the 'dmas' property in client nodes, + strongly recommended since common client helper code + uses this property + +Example: + + dma0: dma@14000 { + compatible = "fsl,mpc5121-dma"; + reg = <0x14000 0x1800>; + interrupts = <65 0x8>; + #dma-cells = <1>; + }; + + +Client node properties: + +Required properties: +- dmas: list of DMA specifiers, consisting each of a handle + for the DMA controller and integer cells to specify + the channel used within the DMA controller +- dma-names: list of identifier strings for the DMA specifiers, + client device driver code uses these strings to + have DMA channels looked up at the controller + +Example: + + sdhc@1500 { + compatible = "fsl,mpc5121-sdhc"; + /* ... */ + dmas = <&dma0 30>; + dma-names = "rx-tx"; + };