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 6C918C77B6F for ; Wed, 12 Apr 2023 17:00:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229564AbjDLRAT (ORCPT ); Wed, 12 Apr 2023 13:00:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36528 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229661AbjDLRAS (ORCPT ); Wed, 12 Apr 2023 13:00:18 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B110493FE; Wed, 12 Apr 2023 09:59:57 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 333526377F; Wed, 12 Apr 2023 16:59:57 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0685AC433EF; Wed, 12 Apr 2023 16:59:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1681318796; bh=waL1SUStoZYoO7jMUcgEhhUZnXTPiR4HX3xLSQqTvB0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nj3lE1TsmBurSn1IxeNk9HCoQTJjmeSjZDCF6F4SDJgsLJvlnv1KsBDkWQg1BXLHL Q9QTZccm4JtJ2NCp3HXrx5sioJxS5DWjrDHgcJkRl1BaNPs+bJhW443y+h+ctKb+Hj Sv70nuch0Wz7Vua1IpkvuZ8kiyC82KD7lHKKjLnJRAdH3tPprlZ0xf/ZE4MKGyJ8hr F/MWJaWrxf50ZiQQ5biQ40MdFfHwRFes+VkqgEp7UWokKzGdpYnTiyd5ncJuXQCs3W e5VTJp6CrYaj5DKyxwPRI1wDQmB7TVN+xWghLePXgeJLtOC7jgiLh5g/J58WH9zfHJ EjLTFj2ZH3sWQ== Date: Wed, 12 Apr 2023 22:29:52 +0530 From: Vinod Koul To: Cai Huoqing Cc: fancer.lancer@gmail.com, 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 v9 0/4] dmaengine: dw-edma: Add support for native HDMA Message-ID: References: <20230324021420.73401-1-cai.huoqing@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230324021420.73401-1-cai.huoqing@linux.dev> Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On 24-03-23, 10:14, 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. It fails to apply, pls rebase and resend -- ~Vinod