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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9DD11C41513 for ; Tue, 8 Aug 2023 22:54:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229437AbjHHWxa (ORCPT ); Tue, 8 Aug 2023 18:53:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35820 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229499AbjHHWxS (ORCPT ); Tue, 8 Aug 2023 18:53:18 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89102173F; Tue, 8 Aug 2023 15:53:17 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 1B78562DFC; Tue, 8 Aug 2023 22:53:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E512EC433C8; Tue, 8 Aug 2023 22:53:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1691535196; bh=1gOeRTsFXmQto/w6QtWmIOTr5WO2jJS/Rnlqgow9WNM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=EePUFjZuFqQjcPPRVFStz5aFRARMwCXyHEG10Ao6tbEk8Osw71qQU0NQfUbArfVP3 6IK9UJeh2+tABdWa78TfEvVCvlK6W6m9qeRD1gMemE09avgyhT43sZuI+gOCOQ9UMu XI90EDt5z6Rp4k+bzHbBDkYCkSYo1Q5t7ImxIKGDZlmwXZLvKVVylwthx9fQeotQkI TGi2CRyqeVxv00rM0wsvfSVbj71ZSi9JItImRYDwCLzopF2Ubg05WjRoIoULx9nkit m80u6o2+CBGZolkKLkb+f+4Rd9jL+uOIWmkvkzWehbWZ2c/+YF6LpqWeHpn0JmnXy0 IUyCibHwArkpw== Date: Tue, 8 Aug 2023 15:53:15 -0700 From: Jakub Kicinski To: Cc: Radhey Shyam Pandey , , , , , , , , , , , , , , Subject: Re: [PATCH net-next v5 00/10] net: axienet: Introduce dmaengine Message-ID: <20230808155315.2e68b95c@kernel.org> In-Reply-To: <1691387509-2113129-1-git-send-email-radhey.shyam.pandey@amd.com> References: <1691387509-2113129-1-git-send-email-radhey.shyam.pandey@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Mon, 7 Aug 2023 11:21:39 +0530 Radhey Shyam Pandey wrote: > The axiethernet driver can use the dmaengine framework to communicate > with the xilinx DMAengine driver(AXIDMA, MCDMA). The inspiration behind > this dmaengine adoption is to reuse the in-kernel xilinx dma engine > driver[1] and remove redundant dma programming sequence[2] from the > ethernet driver. This simplifies the ethernet driver and also makes > it generic to be hooked to any complaint dma IP i.e AXIDMA, MCDMA > without any modification. > > The dmaengine framework was extended for metadata API support during > the axidma RFC[3] discussion. However, it still needs further > enhancements to make it well suited for ethernet usecases. > > Comments, suggestions, thoughts to implement remaining functional > features are very welcome! Vinod, any preference on how this gets merged? Since we're already at -rc5 if the dmaengine parts look good to you taking those in for 6.6 and delaying the networking bits until 6.7 could be on the table? Possibly?