Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1675286imu; Wed, 23 Jan 2019 23:16:27 -0800 (PST) X-Google-Smtp-Source: ALg8bN6yz8rlY6MwdFObyexFrfoasQFh6esWN//AdoB3TL+NUONRjniz6+w06AE88LxCB77BYjcE X-Received: by 2002:a63:ff62:: with SMTP id s34mr4948494pgk.325.1548314187902; Wed, 23 Jan 2019 23:16:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548314187; cv=none; d=google.com; s=arc-20160816; b=AIOGn9U/GqHOXdbneB60d68XpyjNrX2WGqb64uHqs47WefenOe/b8DmYcFLgA/WqT2 na7cp15A9G26N6FGNtKAAl83o/1gTiTKmeE96HxqrPhHZTUhfsIeYid5vdvgWzIwmLui UAS8wC5iaJ9wZcaZhdGg/nyYfHtdnZfyZSN0DUqJjB4oZ6c4hup50ZYw2Q8RqWluPq4o sot/I9Ox4QF2zf59hUU5+/Z0psXp9H4fFfWZ1vmpE2nxB8Xi+a+PIs6ACG6IKjblwaQb 42VqzRFBEwwFM6Lbbp0i6vofpv3Evqp78+cCMzOH/40lRd0Ffu+Y+f8Kpd7fb1q/3eBH 9vlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=5mtI3BGzt0jKo5pggMWGlazsF1LJQes6dAXectadhm0=; b=TBhcvNUwmtEpvpKYANjFeHLmbbr65c/vQzKWoKa1za7qsxVO/8kS6oruAJBQQkub2W TPYuLLUMw8ode27eiRHv9lpRzSaqgpGWBruraxrjU2sGrI0QjLFIhlq2TjkZ6/N2XqkT cqRCPZzf9Bzip/hS6KNvOEIAvFFfJ4o6jnQ62ebNuU1YhCPHmVu2/t2O42e61+UhGSPi xfDqpdwa458nlxIl/WGaB4Kjw1VEpi0xEVF+04MOsVakI2AKNakajhFpwr1zFHXtXmMw 9eG9HgKQwh/E4OYQ+Y9di8xlc29vALCo05GHI/mr3bKHhiADNilrWCjUVp5vpbGyWDpN MG7g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 3si21799879plx.33.2019.01.23.23.16.12; Wed, 23 Jan 2019 23:16:27 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726308AbfAXHPF (ORCPT + 99 others); Thu, 24 Jan 2019 02:15:05 -0500 Received: from mailgw01.mediatek.com ([210.61.82.183]:52719 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1725287AbfAXHPF (ORCPT ); Thu, 24 Jan 2019 02:15:05 -0500 X-UUID: 4bcfcf511c2d435e9a04a0aad1b42e6c-20190124 X-UUID: 4bcfcf511c2d435e9a04a0aad1b42e6c-20190124 Received: from mtkcas08.mediatek.inc [(172.21.101.126)] by mailgw01.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1512581152; Thu, 24 Jan 2019 15:14:57 +0800 Received: from MTKCAS06.mediatek.inc (172.21.101.30) by mtkmbs01n1.mediatek.inc (172.21.101.68) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 24 Jan 2019 15:14:56 +0800 Received: from mtkswgap22.mediatek.inc (172.21.77.33) by MTKCAS06.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Thu, 24 Jan 2019 15:14:56 +0800 From: To: Sean Wang , Vinod Koul , Rob Herring , Matthias Brugger , Dan Williams CC: , , , , , , Shun-Chih Yu Subject: [PATCH v5 1/2] dt-bindings: dmaengine: Add MediaTek Command-Queue DMA controller bindings Date: Thu, 24 Jan 2019 15:14:19 +0800 Message-ID: <1548314060-4833-2-git-send-email-shun-chih.yu@mediatek.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1548314060-4833-1-git-send-email-shun-chih.yu@mediatek.com> References: <1548314060-4833-1-git-send-email-shun-chih.yu@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Shun-Chih Yu Document the devicetree bindings for MediaTek Command-Queue DMA controller which could be found on MT6765 SoC or other similar Mediatek SoCs. Signed-off-by: Shun-Chih Yu Reviewed-by: Rob Herring --- .../devicetree/bindings/dma/mtk-cqdma.txt | 31 ++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 Documentation/devicetree/bindings/dma/mtk-cqdma.txt diff --git a/Documentation/devicetree/bindings/dma/mtk-cqdma.txt b/Documentation/devicetree/bindings/dma/mtk-cqdma.txt new file mode 100644 index 0000000..fb12927 --- /dev/null +++ b/Documentation/devicetree/bindings/dma/mtk-cqdma.txt @@ -0,0 +1,31 @@ +MediaTek Command-Queue DMA Controller +================================== + +Required properties: + +- compatible: Must be "mediatek,mt6765-cqdma" for MT6765. +- reg: Should contain the base address and length for each channel. +- interrupts: Should contain references to the interrupts for each channel. +- clocks: Should be the clock specifiers corresponding to the entry in + clock-names property. +- clock-names: Should contain "cqdma" entries. +- dma-channels: The number of DMA channels supported by the controller. +- dma-requests: The number of DMA request supported by the controller. +- #dma-cells: The length of the DMA specifier, must be <1>. This one cell + in dmas property of a client device represents the channel + number. +Example: + + cqdma: dma-controller@10212000 { + compatible = "mediatek,mt6765-cqdma"; + reg = <0 0x10212000 0 0x1000>; + interrupts = , + ; + clocks = <&infracfg CLK_IFR_CQ_DMA>; + clock-names = "cqdma"; + dma-channels = <2>; + dma-requests = <32>; + #dma-cells = <1>; + }; + +DMA clients must use the format described in dma/dma.txt file. -- 1.7.9.5