From: Vinod Koul <vkoul@kernel.org>
To: Federico Vaga <federico.vaga@cern.ch>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: DMA Engine Documentation: TX Descriptor and Submission
Date: Fri, 1 Feb 2019 09:47:50 +0530 [thread overview]
Message-ID: <20190201041750.GM4635@vkoul-mobl> (raw)
In-Reply-To: <1655406.8MLMLfCWyH@pcbe13614>
On 28-01-19, 09:47, Federico Vaga wrote:
> Hi,
>
> I have a new question concerning documentation.
>
> https://www.kernel.org/doc/html/latest/driver-api/dmaengine/client.html
>
> >From this document it is not really clear, at least to me, if clients can
> consider valid the `struct dma_async_tx_descriptor` after submission to the
> DMA engine.
Nope they can't and should not touch the descriptor after submission.
The client get cookie and that is supposed to be used
>
> Clients get a TX descriptor from a DMA engine using things like
> `dmaengine_prep_*`. These calls - may - allocate new descriptors and return
> them to the caller; this may include other structures which are not visible to
> clients. So, if my understanding is correct, this means that it's the DMA
> engine that, on TX completion, releases any TX descriptor allocated by
> `dmaengine_prep_*`. This implies that the pointer that the client is using
> must be considered invalid right after `dmaengine_submit()`.
> If what I understood by reading the documentation and the code is correct,
> then I think that this should be mentioned in the Documentation.
> If I'm wrong, please tell me where :)
And what exactly are you trying to do here..?
--
~Vinod
next prev parent reply other threads:[~2019-02-01 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:47 DMA Engine Documentation: TX Descriptor and Submission Federico Vaga
2019-02-01 4:17 ` Vinod Koul [this message]
2019-02-01 9:59 ` Federico Vaga
2019-02-02 9:35 ` Vinod Koul
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=20190201041750.GM4635@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=federico.vaga@cern.ch \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).