From: Francesco Dolcini <francesco@dolcini.it>
To: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dmaengine: ti: k3-udma: Avoid false error msg on chan teardown
Date: Mon, 7 Aug 2023 17:40:13 +0200 [thread overview]
Message-ID: <ZNEQXVYDstabJCVc@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20220215044112.161634-1-vigneshr@ti.com>
Hello Vignesh,
reviving this old email, since it seems that it raised a valid issue
that is still not resolved.
On Tue, Feb 15, 2022 at 10:11:12AM +0530, Vignesh Raghavendra wrote:
> In cyclic mode, there is no additional descriptor pushed to collect
> outstanding data on channel teardown. Therefore no need to wait for this
> descriptor to come back.
>
> Without this terminating aplay cmd outputs false error msg like:
> [ 116.402800] ti-bcdma 485c0100.dma-controller: chan1 teardown timeout!
I am experiencing a similar issue on Toradex Verdin AM62:
```
kern :warn : [ 40.196661] ti-udma 485c0100.dma-controller: chan2 teardown timeout!
kern :warn : [ 41.077013] kauditd_printk_skb: 14 callbacks suppressed
kern :warn : [ 46.404672] ti-udma 485c0100.dma-controller: chan2 teardown timeout!
kern :warn : [ 50.852643] ti-udma 485c0100.dma-controller: chan1 teardown timeout!
kern :warn : [ 56.932709] ti-udma 485c0100.dma-controller: chan1 teardown timeout!
kern :warn : [ 64.516797] ti-udma 485c0100.dma-controller: chan1 teardown timeout!
kern :warn : [ 70.404724] ti-udma 485c0100.dma-controller: chan1 teardown timeout!
kern :warn : [ 71.588933] ti-udma 485c0100.dma-controller: chan2 teardown timeout!
kern :warn : [ 75.908818] ti-udma 485c0100.dma-controller: chan1 teardown timeout!
kern :warn : [ 77.064761] ti-udma 485c0100.dma-controller: chan2 teardown timeout!
```
I would say just the same, since this happens everytime aplay terminates.
Any idea to progress on this?
Francesco
prev parent reply other threads:[~2023-08-07 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 4:41 [PATCH] dmaengine: ti: k3-udma: Avoid false error msg on chan teardown Vignesh Raghavendra
2022-02-20 20:12 ` Péter Ujfalusi
2022-02-28 9:22 ` Vignesh Raghavendra
2022-02-28 11:18 ` Vignesh Raghavendra
2022-03-01 19:31 ` Péter Ujfalusi
2023-08-07 15:40 ` Francesco Dolcini [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=ZNEQXVYDstabJCVc@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vigneshr@ti.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