From patchwork Thu Mar 20 14:47:57 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alexander Popov X-Patchwork-Id: 3866491 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 4E245BF540 for ; Thu, 20 Mar 2014 14:48:34 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 6E8ED20237 for ; Thu, 20 Mar 2014 14:48:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 873F920240 for ; Thu, 20 Mar 2014 14:48:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933973AbaCTOs3 (ORCPT ); Thu, 20 Mar 2014 10:48:29 -0400 Received: from mail-la0-f50.google.com ([209.85.215.50]:38320 "EHLO mail-la0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965116AbaCTOsY (ORCPT ); Thu, 20 Mar 2014 10:48:24 -0400 Received: by mail-la0-f50.google.com with SMTP id y1so676002lam.23 for ; Thu, 20 Mar 2014 07:48:22 -0700 (PDT) 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=RheIwPZUB5fUrgapCw8f9A6rPANoK0SISpcXrc73XKFzJbAkTO3ZtxrpcWdjfNWY91 TjFxSbKsCJRKznBfroXFtzhTGZoOm7+uSLqDdUu4ShtLLJoBRqF9FnMG3SKjw/AcHeaI 8fg6NUBZiTjY0Ms48KsdTqJHJz5f+q3vSmfrW9LaN/9ni640quVx4ezvEiR/eKTabIYp iXngGsGJKrQ1WsrzLiCxKJLhlF1qcoPdhZxLDfUtD1/wnvTkef119FwnDvTtSntLmaU+ HWYrP6tCoGL38aXXypV3eAl60aoPcl9N/d+YtNUOXOm4M81qnHDNjGHF/JdmFZEM/9h9 bISw== X-Received: by 10.152.225.70 with SMTP id ri6mr30334287lac.26.1395326902788; Thu, 20 Mar 2014 07:48:22 -0700 (PDT) Received: from a13xCCC.localdomain (mail.tecon.ru. [89.175.104.62]) by mx.google.com with ESMTPSA id qa7sm1398967lbb.6.2014.03.20.07.48.20 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 20 Mar 2014 07:48:21 -0700 (PDT) From: Alexander Popov To: Gerhard Sittig , Dan Williams , Vinod Koul , Lars-Peter Clausen , Arnd Bergmann , Anatolij Gustschin , Andy Shevchenko , Alexander Popov , linuxppc-dev@lists.ozlabs.org, dmaengine@vger.kernel.org Cc: devicetree@vger.kernel.org Subject: [PATCH RFC v10 5/6] dma: mpc512x: add device tree binding document Date: Thu, 20 Mar 2014 18:47:57 +0400 Message-Id: <1395326878-25243-6-git-send-email-a13xp0p0v88@gmail.com> X-Mailer: git-send-email 1.7.11.3 In-Reply-To: <1395326878-25243-1-git-send-email-a13xp0p0v88@gmail.com> References: <1395326878-25243-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, T_DKIM_INVALID, T_RP_MATCHES_RCVD, 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"; + };