devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Yves MORDRET <pierre-yves.mordret@st.com>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>,
	devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/7] Add-DMA-MDMA-chaining-support
Date: Fri, 28 Sep 2018 16:30:51 +0200	[thread overview]
Message-ID: <6bc2e022-1a36-f36c-b23b-e2ba7b16f2fc@st.com> (raw)
In-Reply-To: <1538123794-17085-1-git-send-email-pierre-yves.mordret@st.com>

Hello all,

I've submitted a V3 following a KBuild warning.
You can thus drop this V2.

Thanks and sorry for the spamming.

Have a nice weekend.
Regards

On 09/28/2018 10:36 AM, Pierre-Yves MORDRET wrote:
> This serie adds support for M2M transfer triggered by STM32 DMA in order to
> transfer data from/to SRAM to/from DDR.
> 
> Normally, this mode should not be needed as transferring data from/to DDR
> is supported by the STM32 DMA.
> However, the STM32 DMA don't have the ability to generate burst transfer
> on the DDR as it only embeds only a 4-word FIFO although the minimal burst
> length on the DDR is 8 words.
> Due to this constraint, the STM32 DMA transfers data from/to DDR in a
> single way and could lead to pollute the DDR.
> To avoid this, we have to use SRAM for all transfers where STM32 DMA is
> involved.
> 
> An Hw design has been specially put in place to allow this chaining where DMA
> interrupt is connected on GIC and MDMA request line as well. This grants the
> possibility to trigger an MDMA transfer from the completion of DMA.
> At the same time MDMA has the ability to acknowlege DMA. The aim is to have an
> self refreching mechanism to transfer from/to device to/from DDR with minimal
> sw support.
> For instance the DMA is set in cyclic double buffering to feed SRAM and MDMA
> transfer to DDR thanks to LLI.
> 
> M'boumba Cedric Madianga (7):
>   dt-bindings: stm32-dma: Add DMA/MDMA chaining support bindings
>   dt-bindings: stm32-dmamux: Add one cell to support DMA/MDMA chain
>   dt-bindings: stm32-mdma: Add DMA/MDMA chaining support bindings
>   dmaengine: stm32-dma: Add DMA/MDMA chaining support
>   dmaengine: stm32-mdma: Add DMA/MDMA chaining support
>   dmaengine: stm32-dma: enable descriptor_reuse
>   dmaengine: stm32-mdma: enable descriptor_reuse
> 
>  .../devicetree/bindings/dma/stm32-dma.txt          |  27 +-
>  .../devicetree/bindings/dma/stm32-dmamux.txt       |   6 +-
>  .../devicetree/bindings/dma/stm32-mdma.txt         |  12 +-
>  drivers/dma/stm32-dma.c                            | 903 ++++++++++++++++++---
>  drivers/dma/stm32-mdma.c                           | 133 ++-
>  5 files changed, 949 insertions(+), 132 deletions(-)
> 

      parent reply	other threads:[~2018-09-28 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28  8:36 [PATCH v2 0/7] Add-DMA-MDMA-chaining-support Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 1/7] dt-bindings: stm32-dma: Add DMA/MDMA chaining support bindings Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 2/7] dt-bindings: stm32-dmamux: Add one cell to support DMA/MDMA chain Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 3/7] dt-bindings: stm32-mdma: Add DMA/MDMA chaining support bindings Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 4/7] dmaengine: stm32-dma: Add DMA/MDMA chaining support Pierre-Yves MORDRET
2018-09-28 12:36   ` kbuild test robot
2018-09-28  8:36 ` [PATCH v2 5/7] dmaengine: stm32-mdma: " Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 6/7] dmaengine: stm32-dma: enable descriptor_reuse Pierre-Yves MORDRET
2018-09-28  8:36 ` [PATCH v2 7/7] dmaengine: stm32-mdma: " Pierre-Yves MORDRET
2018-09-28 14:30 ` Pierre Yves MORDRET [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=6bc2e022-1a36-f36c-b23b-e2ba7b16f2fc@st.com \
    --to=pierre-yves.mordret@st.com \
    --cc=alexandre.torgue@st.com \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).