Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934125AbcCPBe3 (ORCPT ); Tue, 15 Mar 2016 21:34:29 -0400 Received: from mail-vk0-f49.google.com ([209.85.213.49]:34697 "EHLO mail-vk0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933932AbcCPBe1 (ORCPT ); Tue, 15 Mar 2016 21:34:27 -0400 MIME-Version: 1.0 In-Reply-To: <1458062592-27981-6-git-send-email-appanad@xilinx.com> References: <1458062592-27981-1-git-send-email-appanad@xilinx.com> <1458062592-27981-6-git-send-email-appanad@xilinx.com> Date: Tue, 15 Mar 2016 18:34:26 -0700 Message-ID: Subject: Re: [PATCH 5/7] dmaengine: xilinx_vdma: Remove unnecessary axi dma device-tree binding doc From: Moritz Fischer To: Kedareswara rao Appana Cc: Dan Williams , Vinod Koul , Michal Simek , =?UTF-8?Q?S=C3=B6ren_Brinkmann?= , Appana Durga Kedareswara Rao , Laurent Pinchart , Luis de Bethencourt , Anirudha Sarangi , dmaengine@vger.kernel.org, linux-arm-kernel , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2452 Lines: 67 Hi there, On Tue, Mar 15, 2016 at 10:23 AM, Kedareswara rao Appana wrote: > AXI DMA support is added to the existing AXI VDMA driver. > The binding doc for AXI DMA should also be updated in the > VDMA device-tree binding doc. > > Signed-off-by: Kedareswara rao Appana > --- > .../devicetree/bindings/dma/xilinx/xilinx_dma.txt | 65 ---------------------- > 1 file changed, 65 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt > > diff --git a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt b/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt > deleted file mode 100644 > index 2291c40..0000000 > --- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_dma.txt > +++ /dev/null > @@ -1,65 +0,0 @@ > -Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream > -target devices. It can be configured to have one channel or two channels. > -If configured as two channels, one is to transmit to the device and another > -is to receive from the device. > - > -Required properties: > -- compatible: Should be "xlnx,axi-dma-1.00.a" > -- #dma-cells: Should be <1>, see "dmas" property below > -- reg: Should contain DMA registers location and length. > -- dma-channel child node: Should have atleast one channel and can have upto > - two channels per device. This node specifies the properties of each > - DMA channel (see child node properties below). at least vs atleast, up to vs upto. > - > -Optional properties: > -- xlnx,include-sg: Tells whether configured for Scatter-mode in > - the hardware. How about: 'If present, hardware supports scatter-gather mode' > - > -Required child node properties: > -- compatible: It should be either "xlnx,axi-dma-mm2s-channel" or > - "xlnx,axi-dma-s2mm-channel". > -- interrupts: Should contain per channel DMA interrupts. > -- xlnx,datawidth: Should contain the stream data width, take values > - {32,64...1024}. > - > -Option child node properties: > -- xlnx,include-dre: Tells whether hardware is configured for Data > - Realignment Engine. How about: 'If present, hardware supports Data Realignment Engine' > - > -Example: > -++++++++ > - > -axi_dma_0: axidma@40400000 { > - compatible = "xlnx,axi-dma-1.00.a"; > - #dma_cells = <1>; I think you meant #dma-cells = <1>; here. That caught me while testing ;-) Cheers, Moritz