From: Vinod Koul <vkoul@kernel.org>
To: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
M'boumba Cedric Madianga <cedric.madianga@gmail.com>,
Pierre-Yves MORDRET <pierre-yves.mordret@st.com>,
Amelie Delaunay <amelie.delaunay@foss.st.com>
Cc: Alain Volmat <alain.volmat@foss.st.com>,
stable@vger.kernel.org, dmaengine@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: stm32-mdma: correct desc prep when channel running
Date: Mon, 16 Oct 2023 16:43:05 +0530 [thread overview]
Message-ID: <169745478541.211836.5231413059323245231.b4-ty@kernel.org> (raw)
In-Reply-To: <20231009082450.452877-1-amelie.delaunay@foss.st.com>
On Mon, 09 Oct 2023 10:24:50 +0200, Amelie Delaunay wrote:
> In case of the prep descriptor while the channel is already running, the
> CCR register value stored into the channel could already have its EN bit
> set. This would lead to a bad transfer since, at start transfer time,
> enabling the channel while other registers aren't yet properly set.
> To avoid this, ensure to mask the CCR_EN bit when storing the ccr value
> into the mdma channel structure.
>
> [...]
Applied, thanks!
[1/1] dmaengine: stm32-mdma: correct desc prep when channel running
commit: 03f25d53b145bc2f7ccc82fc04e4482ed734f524
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-10-16 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 8:24 Amelie Delaunay
2023-10-09 9:02 ` Alain Volmat
2023-10-16 11:11 ` Vinod Koul
2023-10-16 11:13 ` 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=169745478541.211836.5231413059323245231.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=cedric.madianga@gmail.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=pierre-yves.mordret@st.com \
--cc=stable@vger.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
all inboxes | Powered by JetHome®