[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200422102904.1448-1-amelie.delaunay@st.com>
Date: Wed, 22 Apr 2020 12:29:02 +0200
From: Amelie Delaunay <amelie.delaunay@...com>
To: Vinod Koul <vkoul@...nel.org>, Rob Herring <robh+dt@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>
CC: <dmaengine@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
Amelie Delaunay <amelie.delaunay@...com>,
Pierre-Yves Mordret <pierre-yves.mordret@...com>
Subject: [PATCH 0/2] STM32 DMA Direct mode
By default, the driver compute if the FIFO must operate in direct mode or with
FIFO threshold. Direct mode is allowed only if computed source burst and
destination burst are disabled. But with memory source or destination, burst
is always > 0.
Direct mode is useful when the peripheral requires an immediate and single
transfer to or from the memory after each DMA request.
This patchset adds a way to force Direct mode through device tree.
Amelie Delaunay (2):
dt-bindings: dma: add direct mode support through device tree in
stm32-dma
dmaengine: stm32-dma: direct mode support through device tree
.../devicetree/bindings/dma/st,stm32-dma.yaml | 5 +++
drivers/dma/stm32-dma.c | 41 ++++++++++++++-----
2 files changed, 36 insertions(+), 10 deletions(-)
--
2.17.1
Powered by blists - more mailing lists