From: Vinod Koul <vkoul@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@gmail.com>,
Jai Luthra <jai.luthra@linux.dev>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Devarsh Thakkar <devarsht@ti.com>,
Rishikesh Donadkar <r-donadkar@ti.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: ti: k3-udma: Set EOP for all TRs in cyclic BCDMA transfer
Date: Tue, 15 Oct 2024 00:02:31 +0530 [thread overview]
Message-ID: <172893075181.75950.15122834753763958777.b4-ty@kernel.org> (raw)
In-Reply-To: <20240930-z_cnt-v2-1-9d38aba149a2@linux.dev>
On Mon, 30 Sep 2024 13:02:54 -0400, Jai Luthra wrote:
> When receiving data in cyclic mode from PDMA peripherals, where reload
> count is set to infinite, any TR in the set can potentially be the last
> one of the overall transfer. In such cases, the EOP flag needs to be set
> in each TR and PDMA's Static TR "Z" parameter should be set, matching
> the size of the TR.
>
> This is required for the teardown to function properly and cleanup the
> internal state memory. This only affects platforms using BCDMA and not
> those using UDMA-P, which could set EOP flag in the teardown TR
> automatically.
>
> [...]
Applied, thanks!
[1/1] dmaengine: ti: k3-udma: Set EOP for all TRs in cyclic BCDMA transfer
commit: d35f40642904b017d1301340734b91aef69d1c0c
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-10-14 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 17:02 [PATCH v2] dmaengine: ti: k3-udma: Set EOP for all TRs in cyclic BCDMA transfer Jai Luthra
2024-10-06 17:50 ` Péter Ujfalusi
2024-10-14 18:32 ` Vinod Koul [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=172893075181.75950.15122834753763958777.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=devarsht@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=jai.luthra@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=r-donadkar@ti.com \
--cc=vigneshr@ti.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