Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2482931imj; Mon, 18 Feb 2019 06:48:21 -0800 (PST) X-Google-Smtp-Source: AHgI3IapiO4dKh/NmBOVlphZzw8A8MFyT4xcH1yQSyo6fJkchpFqEy4/c0Hea2pvuWmus5RAMOB3 X-Received: by 2002:a63:2705:: with SMTP id n5mr19552566pgn.429.1550501301388; Mon, 18 Feb 2019 06:48:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550501301; cv=none; d=google.com; s=arc-20160816; b=LP+vEUHolH28drdxQGjgmBVH8g/5jha4xT+S7hhJBPx6ywCShwb3eQ+dSfFIwE6T9u Bd9q2mFJpIu7Icxmvqo2u76UCqW2b1eTwVDWf4XEmSXjaYshjLHXm50assQFwXaPwXHs M8q2nNqAvCt6kyBNB08U99RWC7D3rsz/UIpjGSEBD6LnQBKk3U40K6bOXk5A6w8sfVui G7VRaEzb60Moy7xfPDCKlSba1iPtxj7ECrgh49Ox3M3AS3atAZfI45kW1QlQ/toIhEc+ lH3A/p8MiRXBDzfqgQsVO3PsQMXDMfpuTDBY9ODZ0Ngnzvozf4TevPZKqY1xKyKjTtXu IGVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Mi5KJ4XJl6hs8QPqo8n1vqN9I3V/5JezP3CF56Gj/Fk=; b=aeeyCoHUtwhzrB/b26rbAvRxSPAIAVnqKSAYErS+gpahH929WQJFqNzqaWaJrr79qL KlZ33QwuZ4qHJ0RUw57LhTVQnxXARkr/3f+1z6A072uMQS+42FdFKH/2Okr+Njir4qY3 kSda4ouB7rjVIYFemBqb7tq8XqBE2fMKZOor32FHqZCSJODzHFCq12l8vUtRpLS+DM9i dspHyPRcr+VnNOao9ZDEmTBFyHlE2T+0MQHY/sxu0o2NpHkQOtA5JlwkL0nzcY4EeyMa F8ZYAV8Y8MV3ALmsG488KNptlbzKOdjBoRN6q3gog0dqa4GoF8xiAr3rwKx563CEiG9u uhvA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si8885886pgc.558.2019.02.18.06.48.05; Mon, 18 Feb 2019 06:48:21 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390350AbfBROrX (ORCPT + 99 others); Mon, 18 Feb 2019 09:47:23 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:41314 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731777AbfBROrW (ORCPT ); Mon, 18 Feb 2019 09:47:22 -0500 Received: by mail-ot1-f66.google.com with SMTP id t7so12242203otk.8; Mon, 18 Feb 2019 06:47:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Mi5KJ4XJl6hs8QPqo8n1vqN9I3V/5JezP3CF56Gj/Fk=; b=MU2RUFdcIg2y30HD0LAVYT2UgDipY7UaaIdU6/ByoVFaV1+qZKN2Yu1DAeWr3n8UpT 1JHt9sOD6+7VGk6ifGuXtf3WO8zhUGGXyGJ6bGfD1SUmwbxWVCj7D/RXqkt0bRXz9K3i SrnNC+QCN3Ga80KaUPdAcc8gw70JJm/utYEnVxUvQxyhJoXT4Q6WrbOlYk9AofiYuqD5 Et/X5wjmBEwB0qreupJsbcC2TxQOxLUAdvNGjJ71vaZYF/HIhTCmQpeavya3vpwytCet RPhlxG1TUJ2aDJYWA3I8p98c65NZ4nrBDvYwmj9mKrVAeUNdobbvSiOGvvcXP+2Mf6Ng MdkQ== X-Gm-Message-State: AHQUAuazEy6hVWHyr49qAMx217zluBndpeyfMcDNuaKIv3QgMOlYKNaU zghpYr8jK2T+uzHEycjrzpZsxSA= X-Received: by 2002:a9d:7417:: with SMTP id n23mr13908923otk.63.1550501241034; Mon, 18 Feb 2019 06:47:21 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id 88sm2285575otx.57.2019.02.18.06.47.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 18 Feb 2019 06:47:20 -0800 (PST) Date: Mon, 18 Feb 2019 08:47:19 -0600 From: Rob Herring To: shun-chih.yu@mediatek.com Cc: Sean Wang , Vinod Koul , Matthias Brugger , Dan Williams , dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, srv_wsdupstream@mediatek.com Subject: Re: [PATCH 1/1] dt-bindings: dmaengine: Add MediaTek Command-Queue DMA controller bindings Message-ID: <20190218144719.GA28079@bogus> References: <1550130058-16566-1-git-send-email-shun-chih.yu@mediatek.com> <1550130058-16566-2-git-send-email-shun-chih.yu@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1550130058-16566-2-git-send-email-shun-chih.yu@mediatek.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 14, 2019 at 03:40:58PM +0800, shun-chih.yu@mediatek.com wrote: > 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 Drop this. > 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. What's the range of valid values? > +- dma-requests: The number of DMA request supported by the controller. What's the range of valid values? > +- #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>; Should be 2 entries here since there are 2 channels? Or the description above is wrong. > + 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 >