From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 773F2EB64D7 for ; Fri, 30 Jun 2023 16:47:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Ccob9Rg1zMWvhzd0iHEb98ttFYOQ4Rm7klKi5hWrgis=; b=NggJ+tckCpREk4 0dxsAlttJr1zQm/fvIDsAVwqhAoCL/nVC1VPxEQg3efVEiqkcp6gBJ6BwXsm/LO8Cl/BBPDPC9qyX MTYP7IVidEBCbynXoFcm5qM13HmS4M5QkgL2vVietjIBt+HwzypGn3fLe1Os92n5q9dSxH/OndmLE fi4RpEtcXTt3reTAuS4CKFgPfnnCor3IYDOFOSKD7SH82lGhfYl//Mn48EWkJZfEIxFiRuYwIONT0 JvBgsDtwvkKlkc59+bPklWDR7x1GjswEXdc0Szxi+iOtFc/hShGC7j0rl2FdcRYkeiwCx5vJBEMi+ y7g+OGIc9eLCGk8KXizQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qFHH2-0045YJ-0X; Fri, 30 Jun 2023 16:47:08 +0000 Received: from mail-il1-f181.google.com ([209.85.166.181]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1qFHGz-0045X6-1q for linux-arm-kernel@lists.infradead.org; Fri, 30 Jun 2023 16:47:06 +0000 Received: by mail-il1-f181.google.com with SMTP id e9e14a558f8ab-345c487807bso9227315ab.1 for ; Fri, 30 Jun 2023 09:47:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688143623; x=1690735623; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=d6DGhP0NKduRLIremGdPnWFJvBxfZB29kWmtTlgPqSY=; b=B67lighPs9tfRZ5UCr53hH0E4AXTN70VsegGZ3G59JFRki+Wxvnmm7d6teqWrnz8mk rvhh2ImwIKXH4vqRvrfQ6y6M7M2heBpRqBnBuUMH77yGbTFspxTbRhi7sk3DWcEM4hRx AWeIQqj5/awXpX4F9/2cgo6eH2VmrPsFFqwZbR9k9ETHNT0mTVV/V5QdCu4Sdev27wEM l5YxU3Phil1kFf5TyrfvbSPAp4YwIVpV6x8QEkbdn0abuq4+oiL2nggBqFQ1kVzAZHsP 3PYUzZMIel7qdNKrvfaxMwVPY9ewaENPelAJGEvBwKzfTmQtqaAFwJVhJz5strbtu9b0 g0YQ== X-Gm-Message-State: AC+VfDze+wC/CCWv9/jlokdtiCMAftypPfgo0mh+50kHWG49AS15ePA2 weqU/HK4en8t+DuGA009YQ== X-Google-Smtp-Source: ACHHUZ6OwIYPczmqbgzkEpt6HyXVM0dPvYAT8oKibXf2XmJsco67c0AQJfN7FfdjPE7jY6RKcJU0ng== X-Received: by 2002:a5d:9a09:0:b0:77e:249e:d84 with SMTP id s9-20020a5d9a09000000b0077e249e0d84mr3330170iol.5.1688143622820; Fri, 30 Jun 2023 09:47:02 -0700 (PDT) Received: from robh_at_kernel.org ([64.188.179.250]) by smtp.gmail.com with ESMTPSA id el16-20020a0566384d9000b0042aebf02107sm2091962jab.138.2023.06.30.09.47.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 30 Jun 2023 09:47:01 -0700 (PDT) Received: (nullmailer pid 1884430 invoked by uid 1000); Fri, 30 Jun 2023 16:46:59 -0000 Date: Fri, 30 Jun 2023 10:46:59 -0600 From: Rob Herring To: Sarath Babu Naidu Gaddam Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, krzysztof.kozlowski+dt@linaro.org, sbhatta@marvell.com, linux@armlinux.org.uk, michal.simek@amd.com, radhey.shyam.pandey@amd.com, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, anirudha.sarangi@amd.com, harini.katakam@amd.com, git@amd.com Subject: Re: [PATCH net-next V4 1/3] dt-bindings: net: xlnx,axi-ethernet: Introduce DMA support Message-ID: <20230630164659.GA1877117-robh@kernel.org> References: <20230630053844.1366171-1-sarath.babu.naidu.gaddam@amd.com> <20230630053844.1366171-2-sarath.babu.naidu.gaddam@amd.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230630053844.1366171-2-sarath.babu.naidu.gaddam@amd.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230630_094705_609775_73EFF95C X-CRM114-Status: GOOD ( 25.78 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Jun 30, 2023 at 11:08:42AM +0530, Sarath Babu Naidu Gaddam wrote: > From: Radhey Shyam Pandey > > The axiethernet will use dmaengine framework to communicate > with dma controller IP instead of built-in dma programming sequence. What's dmaengine framework? This is a binding patch about the h/w. > > To request dma transmit and receive channels the axiethernet uses > generic dmas, dma-names properties. > > Axiethernet may use AXI DMA or MCDMA. DMA has only two channels > where as MCDMA has 16 Tx, 16 Rx channels. To uniquely identify each > channel, we are using 'chan' suffix. Depending on the usecase AXI > ethernet driver can request any combination of multichannel DMA > channels. The DMA provider is outside the scope of the binding. Instead, describe how Axiethernet can use 2 or 32 channels. > > Example: > dma-names = tx_chan0, rx_chan0, tx_chan1, rx_chan1; > > Also to support the backward compatibility, use "dmas" property to > identify as it should use dmaengine framework or legacy > driver(built-in dma programming). > > At this point it is recommended to use dmaengine framework but it's > optional. Once the solution is stable will make dmas as > required properties. > > Signed-off-by: Radhey Shyam Pandey > Signed-off-by: Sarath Babu Naidu Gaddam > > --- > Changes in V4: > 1) Updated commit description about tx/rx channels name. > 2) Removed "dt-bindings" and "dmaengine" strings in subject. > 3) Extended dmas and dma-names to support MCDMA channel names. > 1) Remove "driver" from commit message. > 2) Use pattern/regex for dma-names property. > > Changes in V3: > 1) Reverted reg and interrupts property to support backward compatibility. > 2) Moved dmas and dma-names properties from Required properties. > > Changes in V2: > - None. > --- > .../bindings/net/xlnx,axi-ethernet.yaml | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/xlnx,axi-ethernet.yaml b/Documentation/devicetree/bindings/net/xlnx,axi-ethernet.yaml > index 1d33d80af11c..ea203504b8d4 100644 > --- a/Documentation/devicetree/bindings/net/xlnx,axi-ethernet.yaml > +++ b/Documentation/devicetree/bindings/net/xlnx,axi-ethernet.yaml > @@ -122,6 +122,20 @@ properties: > and "phy-handle" should point to an external PHY if exists. > maxItems: 1 > > + dmas: > + minItems: 2 > + maxItems: 32 > + description: DMA Channel phandle and DMA request line number Drop this description. That's every 'dmas' property. Instead define what each entry is. > + > + dma-names: > + items: > + pattern: "^[tr]x_chan[0-9]|1[0-5]$" I think you need some parentheses. Does a channel 10 or higher name validate? > + description: > + Should be "tx_chan0", "tx_chan1" ... "tx_chan15" for DMA Tx channel > + Should be "rx_chan0", "rx_chan1" ... "rx_chan15" for DMA Rx channel > + minItems: 2 > + maxItems: 32 > + > required: > - compatible > - interrupts > @@ -143,6 +157,8 @@ examples: > clocks = <&axi_clk>, <&axi_clk>, <&pl_enet_ref_clk>, <&mgt_clk>; > phy-mode = "mii"; > reg = <0x40c00000 0x40000>,<0x50c00000 0x40000>; > + dmas = <&xilinx_dma 0>, <&xilinx_dma 1>; > + dma-names = "tx_chan0", "rx_chan0"; > xlnx,rxcsum = <0x2>; > xlnx,rxmem = <0x800>; > xlnx,txcsum = <0x2>; > -- > 2.25.1 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel