Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp1600624imj; Thu, 14 Feb 2019 09:00:19 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia8AYqNt/M9ltHNl6HWs2uypCQIWq3MGiHfygecyPCiul056AsbJqqm0LjbpWqQ2ZEECrbQ X-Received: by 2002:a65:5bcc:: with SMTP id o12mr4599500pgr.304.1550163619856; Thu, 14 Feb 2019 09:00:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550163619; cv=none; d=google.com; s=arc-20160816; b=WRc+XBVVjf4Gw2Z+g6byaCUQJM0XqsJlfdpgbD06kgogJbMcekWsFYITg9nfWtJfgZ TB6KOyI1vJLOvFnkwrpzCpFnUK17n0dsOhJt3aBKLZvfJrnBDsDgz0QJPb2F8QfnKlkD sAbHo+MbFU6/yZcUgFEDPTeLwDrvjG0hqBAc37UOdPuoQ0s++1PpX3AefHn4hfWirYM3 yXiCM5wlq8KxmlpRgRfwJnge2alzrte7nVMzVm9NxpxEy3MqHNQEjr0NKD83cR6a3NJn hJhKBgP28jv42CIQx0Gq+YwKL9yW3UeztcqQxb6BhDGaVjCrKlqhVP/DGqd08gq/yUax /vSw== 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=iKjhWdzb1/WUAwIkB0okUpiVgrbSVkP7MX5+kKV2D9o=; b=SraRiMR74Zl4ZR2jSNg/wVpFIFu4ljD6koK4/fk70iTdNAmAFtOOXA4hbOSOYJcj50 iT0cTNs2uXirFGjiQjp+87fSXTg0rrWayRAcBKxZi4wguL/RhfvDJOVFaNymZ28xrJ/W aHOzoO+X03DBGlYeIKjyg6X6W+F37d8FCa+QT0HzcEZLZL8sHFbTW0Rdk4WI8lfxHUZj iVfszCjDQ6kBIEMvsQD+9UgJ0MBT11M/BpTcWDXf63xOHj2ywde7JZS0RGceh7dwfYvl Zh/sfzenUqblcjoXsHucCIjQxqptMZ/DVe68BxQEtQZXDEaUyDpCgPAsCrhNUUatEgZk Hl7Q== 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 v2si3021160pfv.210.2019.02.14.09.00.03; Thu, 14 Feb 2019 09:00:19 -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 S2437311AbfBNHly (ORCPT + 99 others); Thu, 14 Feb 2019 02:41:54 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:31886 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S2437301AbfBNHlx (ORCPT ); Thu, 14 Feb 2019 02:41:53 -0500 X-UUID: bcc70f86294b45a5b705f2b57d9cbe16-20190214 X-UUID: bcc70f86294b45a5b705f2b57d9cbe16-20190214 Received: from mtkexhb01.mediatek.inc [(172.21.101.102)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1621777597; Thu, 14 Feb 2019 15:41:47 +0800 Received: from MTKCAS06.mediatek.inc (172.21.101.30) by mtkmbs02n1.mediatek.inc (172.21.101.77) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 14 Feb 2019 15:41:45 +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, 14 Feb 2019 15:41:45 +0800 From: To: Sean Wang , Vinod Koul , Rob Herring , Matthias Brugger , Dan Williams CC: , , , , , , Shun-Chih Yu Subject: [PATCH 1/1] dt-bindings: dmaengine: Add MediaTek Command-Queue DMA controller bindings Date: Thu, 14 Feb 2019 15:40:58 +0800 Message-ID: <1550130058-16566-2-git-send-email-shun-chih.yu@mediatek.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1550130058-16566-1-git-send-email-shun-chih.yu@mediatek.com> References: <1550130058-16566-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. Change-Id: I9736c8cac9be160358feeab935fabaffc5730519 Signed-off-by: Shun-Chih Yu --- .../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