public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: pandith.n@intel.com
Cc: Eugeniy.Paltsev@synopsys.com, dmaengine@vger.kernel.org,
	lakshmi.bai.raja.subramanian@intel.com, kris.pan@intel.com,
	mallikarjunappa.sangannavar@intel.com,
	Srikanth.Thokala@intel.com
Subject: Re: [PATCH V5 0/3] dmaengine: dw-axi-dmac: support parallel memory <--> peripheral transfers
Date: Mon, 2 Aug 2021 12:20:02 +0530	[thread overview]
Message-ID: <YQeVmuuLBznc9sBv@matsya> (raw)
In-Reply-To: <20210802055454.15192-1-pandith.n@intel.com>

On 02-08-21, 11:24, pandith.n@intel.com wrote:
> From: Pandith N <pandith.n@intel.com>
> 
> Added support for multiple DMA_MEM_TO_DEV, DMA_DEV_TO_MEM transfers in
> parallel. Peripherals can use DMA for both transmit and receive
> operations in parallel.
> 
> To setup DMA handshaking, the peripheral source number to be programmed
> in respective channel select slot of AXIDMA_CTRL_DMA_HS_SEL. No need to
> check for free slot in dw_axi_dma_set_hw_channel().
> 
> The channel slot used in AXIDMA_CTRL_DMA_HS_SEL needs to be set in
> src_per/dst_per of CHx_CFG register
> 
> Burst length, DMA HW capability set in dt-binding is now used in driver.

Applied, thanks

-- 
~Vinod

      parent reply	other threads:[~2021-08-02  6:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  5:54 [PATCH V5 0/3] dmaengine: dw-axi-dmac: support parallel memory <--> peripheral transfers pandith.n
2021-08-02  5:54 ` [PATCH V5 1/3] dmaengine: dw-axi-dmac: Remove free slot check algorithm in dw_axi_dma_set_hw_channel pandith.n
2021-08-02  5:54 ` [PATCH V5 2/3] dmaengine: dw-axi-dmac: support parallel memory <--> peripheral transfers pandith.n
2021-08-02  5:54 ` [PATCH V5 3/3] dmaengine: dw-axi-dmac: Burst length settings pandith.n
2021-08-02  6:50 ` Vinod Koul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YQeVmuuLBznc9sBv@matsya \
    --to=vkoul@kernel.org \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Srikanth.Thokala@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=kris.pan@intel.com \
    --cc=lakshmi.bai.raja.subramanian@intel.com \
    --cc=mallikarjunappa.sangannavar@intel.com \
    --cc=pandith.n@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox