Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
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
In-Reply-To: <20231009082450.452877-1-amelie.delaunay@foss.st.com>
References: <20231009082450.452877-1-amelie.delaunay@foss.st.com>
Subject: Re: [PATCH] dmaengine: stm32-mdma: correct desc prep when channel
 running
Message-Id: <169745478541.211836.5231413059323245231.b4-ty@kernel.org>
Date:   Mon, 16 Oct 2023 16:43:05 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


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