From: Vinod Koul <vkoul@kernel.org>
To: Vaishnav Achath <vaishnav.a@ti.com>
Cc: dmaengine@vger.kernel.org, kishon@ti.com,
linux-kernel@vger.kernel.org, peter.ujfalusi@gmail.com,
vigneshr@ti.com
Subject: Re: [PATCH v2] dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not requested
Date: Thu, 29 Sep 2022 22:35:36 +0530 [thread overview]
Message-ID: <YzXQYE/N3S+TijFI@matsya> (raw)
In-Reply-To: <20220914110049.5842-1-vaishnav.a@ti.com>
On 14-09-22, 16:30, Vaishnav Achath wrote:
> If the DMA consumer driver does not expect the callback for TX done, then
> we need not perform the channel RT byte counter calculations and estimate
> the completion but return complete on first attempt itself.This assumes
> that the consumer who did not request DMA_PREP_INTERRUPT has its own
> mechanism for understanding TX completion, example: MCSPI EOW interrupt
> can be used as TX completion signal for a SPI transaction.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-09-29 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 11:00 [PATCH v2] dmaengine: ti: k3-udma: Respond TX done if DMA_PREP_INTERRUPT is not requested Vaishnav Achath
2022-09-29 17:05 ` 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=YzXQYE/N3S+TijFI@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vaishnav.a@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