Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2509093rwd; Fri, 19 May 2023 06:44:57 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7oCcXGtX0cv5D3WjlnD3lM74st4OrWlwPIS0Tj+8BOuDB4Qo0lnBAqY+s9MpTrs14K7ewE X-Received: by 2002:a17:902:d501:b0:1ae:2e0d:b38c with SMTP id b1-20020a170902d50100b001ae2e0db38cmr3317232plg.12.1684503897465; Fri, 19 May 2023 06:44:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684503897; cv=none; d=google.com; s=arc-20160816; b=Qs6Ib1Y5xuHkwbNzjRq/t7CP9i6lAZjIYTiKLMoaI+yh4FJHwrwCz66VxGRWszuQMx 1nVhm4Oil2ZhSLVt778FZnqMai9NWMmie/IF3ozeyKqCBEAMxmCVatyyZJPT7ghty0Vy 0Yfj9CA++YfL1i0whhxMD4PD0A/RM/fLMqeK8/ucBuJ7XdGvRL3V+pd4Jnnvh2spnx/u wBl6BujOkqRB0+e+cxYJQRw87LYyeeDXsOwEdM+fRxEP/WD3qJmdZPQQB3VEyCX9YmU0 1H7ERStbvZ5EZSdAVxRDnh5pUmNHVI34spPnW7mVGBj6sN9XEP85IyFsA65u6FjjkNQd wRGQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:dkim-signature:date; bh=RXWuk6ghIzOyzAA9yZbbCypRzSnh7XOuXuFVDgXLo2Y=; b=DFoy4C3xgk0ek4MxXJ97kKNzbQX9xP17FBNHDtFWHv838JDK9aXCBfKsB7IUnxx9K+ 6fxXU/5RWyhXIA5xO40fb9/RuB/ShOoxErXjGyh9/x/fzxM3DfChCONlG3cmEdU5LcuD fXFfcRVwusjSpdrfM3RdX6oOczauEbA6uaggtQW3bEjwQWPPJ2w+n73xN88/9ZEbfH9m 0VgIsuUYiVgSvioz6khP2kkfK4QPlN0+wd796kRtdQ+eZhxftU9bYdymIL7XuVkZbaA/ 9HYau7YZErQFaAvZMJcVteyHPU3Kakok/QsoIvPoudzq+FI48yG/Pq3QGEDTMOGCfBgA ndpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=spAu7Wm5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b5-20020a170902e94500b001ae515f032esi3314142pll.481.2023.05.19.06.44.42; Fri, 19 May 2023 06:44:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b=spAu7Wm5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231883AbjESNj2 (ORCPT + 99 others); Fri, 19 May 2023 09:39:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55230 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230394AbjESNjX (ORCPT ); Fri, 19 May 2023 09:39:23 -0400 Received: from out-40.mta1.migadu.com (out-40.mta1.migadu.com [IPv6:2001:41d0:203:375::28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DED3712C for ; Fri, 19 May 2023 06:39:15 -0700 (PDT) Date: Fri, 19 May 2023 21:39:08 +0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1684503553; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=RXWuk6ghIzOyzAA9yZbbCypRzSnh7XOuXuFVDgXLo2Y=; b=spAu7Wm5CNQBvp/g3euBkKQ6z3M/HwWqBZ25mZueQ58hLPiLjZz/cgK0UJGMmGvccgTcrx BsrK0dq8ynNE6BAtuyZwlBCH36/C2j5SSBN0l1c+wBtrrjMS+mIMlyTEJA2ey4BDXBGAjs i6FCTcVDHciL+ocz/+qweE01z4jW2hQ= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Cai Huoqing To: Vinod Koul Cc: Serge Semin , Gustavo Pimentel , Jingoo Han , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , Bjorn Helgaas , linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH v10 0/4] dmaengine: dw-edma: Add support for native HDMA Message-ID: References: <20230517030115.21093-1-cai.huoqing@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Migadu-Flow: FLOW_OUT X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19 5月 23 16:57:06, Vinod Koul wrote: > On 17-05-23, 11:01, Cai Huoqing wrote: > > Add support for HDMA NATIVE, as long the IP design has set > > the compatible register map parameter-HDMA_NATIVE, > > which allows compatibility for native HDMA register configuration. > > > > The HDMA Hyper-DMA IP is an enhancement of the eDMA embedded-DMA IP. > > And the native HDMA registers are different from eDMA, > > so this patch add support for HDMA NATIVE mode. > > > > HDMA write and read channels operate independently to maximize > > the performance of the HDMA read and write data transfer over > > the link When you configure the HDMA with multiple read channels, > > then it uses a round robin (RR) arbitration scheme to select > > the next read channel to be serviced.The same applies when > > youhave multiple write channels. > > > > The native HDMA driver also supports a maximum of 16 independent > > channels (8 write + 8 read), which can run simultaneously. > > Both SAR (Source Address Register) and DAR (Destination Address Register) > > are aligned to byte. > > > > Cai Huoqing (1): > > dmaengine: dw-edma: Add support for native HDMA > > > > Cai huoqing (3): > > dmaengine: dw-edma: Rename dw_edma_core_ops structure to > > dw_edma_plat_ops > > dmaengine: dw-edma: Create a new dw_edma_core_ops structure to > > abstract controller operation > > dmaengine: dw-edma: Add HDMA DebugFS support > > You should have a single name for all these patches :-( Hi Vinod, Thanks for your reply. Do you mean patch[0/4] and patch[3/4] shouldn't have the same name? Thanks, Cai- > > > > > Tested-by: Serge Semin > > > > v9->v10: > > 1.Update commit log. > > 2.rebase for dma-next > > > > v9 link: > > https://lore.kernel.org/lkml/20230413033156.93751-1-cai.huoqing@linux.dev/ > > > > drivers/dma/dw-edma/Makefile | 8 +- > > drivers/dma/dw-edma/dw-edma-core.c | 86 ++---- > > drivers/dma/dw-edma/dw-edma-core.h | 58 ++++ > > drivers/dma/dw-edma/dw-edma-pcie.c | 4 +- > > drivers/dma/dw-edma/dw-edma-v0-core.c | 85 +++++- > > drivers/dma/dw-edma/dw-edma-v0-core.h | 14 +- > > drivers/dma/dw-edma/dw-hdma-v0-core.c | 296 +++++++++++++++++++ > > drivers/dma/dw-edma/dw-hdma-v0-core.h | 17 ++ > > drivers/dma/dw-edma/dw-hdma-v0-debugfs.c | 170 +++++++++++ > > drivers/dma/dw-edma/dw-hdma-v0-debugfs.h | 22 ++ > > drivers/dma/dw-edma/dw-hdma-v0-regs.h | 129 ++++++++ > > drivers/pci/controller/dwc/pcie-designware.c | 2 +- > > include/linux/dma/edma.h | 7 +- > > 13 files changed, 807 insertions(+), 91 deletions(-) > > create mode 100644 drivers/dma/dw-edma/dw-hdma-v0-core.c > > create mode 100644 drivers/dma/dw-edma/dw-hdma-v0-core.h > > create mode 100644 drivers/dma/dw-edma/dw-hdma-v0-debugfs.c > > create mode 100644 drivers/dma/dw-edma/dw-hdma-v0-debugfs.h > > create mode 100644 drivers/dma/dw-edma/dw-hdma-v0-regs.h > > > > -- > > 2.34.1 > > -- > ~Vinod