Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1835341imu; Thu, 24 Jan 2019 02:47:58 -0800 (PST) X-Google-Smtp-Source: ALg8bN7n/EITkBhn8zk6JhbEsIlViPFh3mCqgM6nwPgRsRpoNJ4iL0mym4OnO8IcibLC+Ip5Ldzd X-Received: by 2002:a17:902:584:: with SMTP id f4mr6229005plf.28.1548326878492; Thu, 24 Jan 2019 02:47:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548326878; cv=none; d=google.com; s=arc-20160816; b=0/wZF50J1tWC2g78zbZ/MqlWGJQC7Rt5zx4NaHd6uSz8yfl5ZFEsr9ePx8djgJitJE FZxRFA46OYYgLxY8DKKpCCYWIwwhHgpJ2pZsQp2EGJL6pE5p3UU5QYNVRdvjMvNlQFMh rVsi93gAX7nwEATvMJLsv7lXBSSCkfDgbZoBmzUureFgLZJys692dxc7XCQNvpDZ37C0 7krEgsD1ihLqZg+6gWgd51aqXFFFriyFQvDOHkA119J6yQCeiyhBLDeO5FXHL9MU4LjF rWMooXhgOrWyG+6+1xIvnFYQHrVoyJtaa5mR8fUS59JfMbort/fZxXxwSfJtBNqlkKaA x53Q== 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=H/PzIVWxbT9COmXlr/acx1MX214mXBmFcEcc1gZvun4oUcR704iARU4Cb7trJz7AVY IiFhdF55PV7QXyNB7ETLlzIVOJiZ/jDj9bKlX5HnlPP+bo3NyFWoo/BCKVuidiiVEAm0 V5IotXyw8WW/9rJI9UDgfZcOXQqXhtq6NWar2b8zLxGVcW9H0lJhVEwjzTm0Q5W7cyKL rorQxvYkkcKGgxqqgBDxROEtego2cC3VGnUCdIKPwWAfEo8dMHdAmYMurY7o5wBBmEgs iEgEiaRyhz/S9iazdraSfEBiVlCiAc7e2XG9DyunzVkTNaK6Wlf5FwyyxsfuaZeI86Ku auhw== 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 r137si22377184pgr.395.2019.01.24.02.47.42; Thu, 24 Jan 2019 02:47:58 -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 S1727742AbfAXKp5 (ORCPT + 99 others); Thu, 24 Jan 2019 05:45:57 -0500 Received: from mailgw02.mediatek.com ([210.61.82.184]:46632 "EHLO mailgw02.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1727117AbfAXKpv (ORCPT ); Thu, 24 Jan 2019 05:45:51 -0500 X-UUID: b69120d616d5475093d0207359a38cb2-20190124 X-UUID: b69120d616d5475093d0207359a38cb2-20190124 Received: from mtkcas06.mediatek.inc [(172.21.101.30)] by mailgw02.mediatek.com (envelope-from ) (mhqrelay.mediatek.com ESMTP with TLS) with ESMTP id 1440440165; Thu, 24 Jan 2019 18:45:36 +0800 Received: from mtkcas07.mediatek.inc (172.21.101.84) by mtkmbs01n1.mediatek.inc (172.21.101.68) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 24 Jan 2019 18:45:35 +0800 Received: from mtkswgap22.mediatek.inc (172.21.77.33) by mtkcas07.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Thu, 24 Jan 2019 18:45:35 +0800 From: To: Sean Wang , Vinod Koul , Rob Herring , Matthias Brugger , Dan Williams CC: , , , , , , Shun-Chih Yu Subject: [PATCH 1/2] dt-bindings: dmaengine: Add MediaTek Command-Queue DMA controller bindings Date: Thu, 24 Jan 2019 18:44:39 +0800 Message-ID: <1548326680-16454-2-git-send-email-shun-chih.yu@mediatek.com> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1548326680-16454-1-git-send-email-shun-chih.yu@mediatek.com> References: <1548326680-16454-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