From: Frank.Li@oss.nxp.com
To: Shengjiu Wang <shengjiu.wang@gmail.com>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Nicolin Chen <nicoleotsuka@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org (open list:FREESCALE SOC SOUND
DRIVERS),
linuxppc-dev@lists.ozlabs.org (open list:FREESCALE SOC SOUND
DRIVERS), linux-kernel@vger.kernel.org (open list)
Cc: imx@lists.linux.dev, vkoul@kernel.org, Frank Li <Frank.Li@nxp.com>
Subject: [PATCH 1/1] ASoC: fsl_asrc_m2m: use dma_chan directly for dma_async_issue_pending()
Date: Mon, 2 Nov 2026 14:52:27 -0500 [thread overview]
Message-ID: <20261102195228.4084438-1-Frank.Li@oss.nxp.com> (raw)
From: Frank Li <Frank.Li@nxp.com>
Use pair->dma_chan[] directly instead of pair->desc[]->chan when calling
dma_async_issue_pending(), which is more straightforward and avoids
dereferencing the descriptor to get the channel.
Prepare to make struct dma_async_tx_descriptor private.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
sound/soc/fsl/fsl_asrc_m2m.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/fsl/fsl_asrc_m2m.c b/sound/soc/fsl/fsl_asrc_m2m.c
index c6970a7e88f3f..796a78124765f 100644
--- a/sound/soc/fsl/fsl_asrc_m2m.c
+++ b/sound/soc/fsl/fsl_asrc_m2m.c
@@ -257,12 +257,12 @@ static int asrc_m2m_device_run(struct fsl_asrc_pair *pair, struct snd_compr_task
/* Submit DMA request */
dmaengine_submit(pair->desc[IN]);
- dma_async_issue_pending(pair->desc[IN]->chan);
+ dma_async_issue_pending(pair->dma_chan[IN]);
if (out_dma_len > 0) {
if (asrc->start_before_dma && asrc->m2m_output_ready)
asrc->m2m_output_ready(pair);
dmaengine_submit(pair->desc[OUT]);
- dma_async_issue_pending(pair->desc[OUT]->chan);
+ dma_async_issue_pending(pair->dma_chan[OUT]);
}
if (!asrc->start_before_dma)
--
2.43.0
reply other threads:[~2026-11-02 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261102195228.4084438-1-Frank.Li@oss.nxp.com \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=Xiubo.Lee@gmail.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@gmail.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®