From: Amelie Delaunay <amelie.delaunay@st.com>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Cc: <dmaengine@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Amelie Delaunay <amelie.delaunay@st.com>,
Pierre-Yves Mordret <pierre-yves.mordret@st.com>
Subject: [PATCH 0/2] STM32 DMA Direct mode
Date: Wed, 22 Apr 2020 12:29:02 +0200 [thread overview]
Message-ID: <20200422102904.1448-1-amelie.delaunay@st.com> (raw)
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
next reply other threads:[~2020-04-22 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 10:29 Amelie Delaunay [this message]
2020-04-22 10:29 ` [PATCH 1/2] dt-bindings: dma: add direct mode support through device tree in stm32-dma Amelie Delaunay
2020-04-22 10:29 ` [PATCH 2/2] dmaengine: stm32-dma: direct mode support through device tree Amelie Delaunay
2020-04-27 16:10 ` [PATCH 0/2] STM32 DMA Direct mode Vinod Koul
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=20200422102904.1448-1-amelie.delaunay@st.com \
--to=amelie.delaunay@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=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@st.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).