From: Frank Li <Frank.li@nxp.com>
To: wangxiaolei <xiaolei.wang@windriver.com>
Cc: vkoul@kernel.org, imx@lists.linux.dev, dmaengine@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: dmaengine: fsl-edma: dmatest timeout
Date: Tue, 28 Nov 2023 16:57:55 -0500 [thread overview]
Message-ID: <ZWZiY4Cy/GP8L+Px@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <ZWYJgc/S8xMofmWw@lizhi-Precision-Tower-5810>
On Tue, Nov 28, 2023 at 10:38:41AM -0500, Frank Li wrote:
> On Tue, Nov 28, 2023 at 12:43:59PM +0800, wangxiaolei wrote:
> > Hi
> >
> > When I executed the following command to do dmatest on the imx8qm platform,
> >
> > I found that the timeout occurred on the current mainline kernel:
> >
> >
> > modprobe dmatest run=1 iterations=42
> >
>
> dmatest use mem to mem transfer. It seldom used at actual system. Let me
> check it.
>
> Frank
>
> >
> > I found that the completion interrupt was not received in
> > fsl_edma3_tx_handler().
I test at imx93, it works. I supposed it is the same as 8qm.
echo dma0chan0 > /sys/module/dmatest/parameters/channel
echo 2000 > /sys/module/dmatest/parameters/timeout
echo 1 > /sys/module/dmatest/parameters/iterations
echo 1 > /sys/module/dmatest/parameters/run
I add debug message:
[ 154.090765] fsl_edma_tx_chan_handler
[ 154.094711] fsl_edma_prep_memcpy 8d842340 8d839280 7104
[ 154.100063] fsl_edma_tx_chan_handler
[ 154.103949] fsl_edma_prep_memcpy 8d8419c0 8d838580 4288
[ 154.109265] fsl_edma_tx_chan_handler
[ 154.113235] fsl_edma_prep_memcpy 8d840ec0 8d838340 6016
[ 154.118573] fsl_edma_tx_chan_handler
[ 154.122508] fsl_edma_prep_memcpy 8d841c00 8d83a8c0 1920
[ 154.127791] fsl_edma_tx_chan_handler
[ 154.131738] fsl_edma_prep_memcpy 8d840040 8d838200 14784
[ 154.137272] fsl_edma_tx_chan_handler
[ 154.141171] fsl_edma_prep_memcpy 8d840280 8d838080 15616
[ 154.146716] fsl_edma_tx_chan_handler
[ 154.150598] fsl_edma_prep_memcpy 8d840e00 8d838f40 4928
[ 154.155915] fsl_edma_tx_chan_handler
[ 154.159858] fsl_edma_prep_memcpy 8d8419c0 8d838040 7424
[ 154.165203] fsl_edma_tx_chan_handler
[ 154.169140] fsl_edma_prep_memcpy 8d841700 8d839380 2560
Frank
> >
> > I didn't find any special configuration from the manual. Can anyone give
> > some suggestions?
> >
> >
> > thanks
> >
> > xiaolei
> >
next prev parent reply other threads:[~2023-11-28 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 4:43 dmaengine: fsl-edma: dmatest timeout wangxiaolei
2023-11-28 15:38 ` Frank Li
2023-11-28 21:57 ` Frank Li [this message]
2023-11-29 3:10 ` wangxiaolei
2023-11-29 15:31 ` Frank Li
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=ZWZiY4Cy/GP8L+Px@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=xiaolei.wang@windriver.com \
/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