From: Amelie Delaunay <amelie.delaunay@foss.st.com>
To: Vinod Koul <vkoul@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <dmaengine@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@foss.st.com>
Subject: [PATCH 0/4] STM32 DMA pause/resume support
Date: Thu, 5 May 2022 12:26:32 +0200 [thread overview]
Message-ID: <20220505102636.35506-1-amelie.delaunay@foss.st.com> (raw)
This patchset introduces pause/resume support in stm32-dma driver.
[1/4], [2/4] and [3/4] ease the introduction of device_pause/device_resume
ops management in [4/4].
Amelie Delaunay (4):
dmaengine: stm32-dma: introduce stm32_dma_sg_inc to manage
chan->next_sg
dmaengine: stm32-dma: pass DMA_SxSCR value to
stm32_dma_handle_chan_done()
dmaengine: stm32-dma: rename pm ops before dma pause/resume
introduction
dmaengine: stm32-dma: add device_pause/device_resume support
drivers/dma/stm32-dma.c | 311 ++++++++++++++++++++++++++++++++++------
1 file changed, 268 insertions(+), 43 deletions(-)
--
2.25.1
next reply other threads:[~2022-05-05 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:26 Amelie Delaunay [this message]
2022-05-05 10:26 ` [PATCH 1/4] dmaengine: stm32-dma: introduce stm32_dma_sg_inc to manage chan->next_sg Amelie Delaunay
2022-05-05 10:26 ` [PATCH 2/4] dmaengine: stm32-dma: pass DMA_SxSCR value to stm32_dma_handle_chan_done() Amelie Delaunay
2022-05-05 10:26 ` [PATCH 3/4] dmaengine: stm32-dma: rename pm ops before dma pause/resume introduction Amelie Delaunay
2022-05-05 11:16 ` [PATCH 0/4] STM32 DMA pause/resume support Amelie Delaunay
2022-05-05 11:14 Amelie Delaunay
2022-05-05 11:16 ` Amelie Delaunay
2022-05-05 11:56 Amelie Delaunay
2022-05-19 17:49 ` 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=20220505102636.35506-1-amelie.delaunay@foss.st.com \
--to=amelie.delaunay@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--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=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).