* [PATCH 1/1] dmaengine: fsl-edma: fix edma4 channel enable failure on second attempt
@ 2023-08-23 18:26 Frank Li
2023-09-28 12:08 ` Vinod Koul
0 siblings, 1 reply; 2+ messages in thread
From: Frank Li @ 2023-08-23 18:26 UTC (permalink / raw)
To: vkoul
Cc: devicetree, dmaengine, frank.li, imx, joy.zou,
krzysztof.kozlowski+dt, linux-kernel, peng.fan, robh+dt,
shenwei.wang
When attempting to start DMA for the second time using
fsl_edma3_enable_request(), channel never start.
CHn_MUX must have a unique value when selecting a peripheral slot in the
channel mux configuration. The only value that may overlap is source 0.
If there is an attempt to write a mux configuration value that is already
consumed by another channel, a mux configuration of 0 (SRC = 0) will be
written.
Check CHn_MUX before writing in fsl_edma3_enable_request().
Fixes: 72f5801a4e2b ("dmaengine: fsl-edma: integrate v3 support")
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
drivers/dma/fsl-edma-common.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/fsl-edma-common.c b/drivers/dma/fsl-edma-common.c
index a0f5741abcc4..edb92fa93315 100644
--- a/drivers/dma/fsl-edma-common.c
+++ b/drivers/dma/fsl-edma-common.c
@@ -92,8 +92,14 @@ static void fsl_edma3_enable_request(struct fsl_edma_chan *fsl_chan)
edma_writel_chreg(fsl_chan, val, ch_sbr);
- if (flags & FSL_EDMA_DRV_HAS_CHMUX)
- edma_writel_chreg(fsl_chan, fsl_chan->srcid, ch_mux);
+ if (flags & FSL_EDMA_DRV_HAS_CHMUX) {
+ /*
+ * ch_mux: With the exception of 0, attempts to write a value
+ * already in use will be forced to 0.
+ */
+ if (!edma_readl_chreg(fsl_chan, ch_mux))
+ edma_writel_chreg(fsl_chan, fsl_chan->srcid, ch_mux);
+ }
val = edma_readl_chreg(fsl_chan, ch_csr);
val |= EDMA_V3_CH_CSR_ERQ;
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/1] dmaengine: fsl-edma: fix edma4 channel enable failure on second attempt
2023-08-23 18:26 [PATCH 1/1] dmaengine: fsl-edma: fix edma4 channel enable failure on second attempt Frank Li
@ 2023-09-28 12:08 ` Vinod Koul
0 siblings, 0 replies; 2+ messages in thread
From: Vinod Koul @ 2023-09-28 12:08 UTC (permalink / raw)
To: Frank Li
Cc: devicetree, dmaengine, frank.li, imx, joy.zou,
krzysztof.kozlowski+dt, linux-kernel, peng.fan, robh+dt,
shenwei.wang
On Wed, 23 Aug 2023 14:26:35 -0400, Frank Li wrote:
> When attempting to start DMA for the second time using
> fsl_edma3_enable_request(), channel never start.
>
> CHn_MUX must have a unique value when selecting a peripheral slot in the
> channel mux configuration. The only value that may overlap is source 0.
> If there is an attempt to write a mux configuration value that is already
> consumed by another channel, a mux configuration of 0 (SRC = 0) will be
> written.
>
> [...]
Applied, thanks!
[1/1] dmaengine: fsl-edma: fix edma4 channel enable failure on second attempt
commit: 3f4b82167a3b1f4ddb33d890f758a042ef4ceef1
Best regards,
--
~Vinod
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-09-28 12:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-23 18:26 [PATCH 1/1] dmaengine: fsl-edma: fix edma4 channel enable failure on second attempt Frank Li
2023-09-28 12:08 ` Vinod Koul
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).