linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA: get data count of descriptor in dmaengine
Date: Fri, 7 Sep 2012 11:35:47 +0100	[thread overview]
Message-ID: <20120907103547.GD13739@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <E8F7C03B253D5640818937FAAE6B175C39CD07A7@penmbx02>

On Fri, Sep 07, 2012 at 09:59:17AM +0000, Song, Elen wrote:
> Hi All:
> 
> 	When I am developing using dma for uart receive, I found a problem.
> 	I use a cyclic dma transfer and set descriptor transfer size to lk, 
> 	only receive 1k bytes(descriptor transfer done) that will call an interrupt.
> 
> 	If I receive 1 byte, there will happened nothing except my peripherals have timeout function. 
> 	Fortunately, I got timeout function in uart peripheral, in timeout handler, I can receive data from uart.
> 	But I do not know how many data I have receive, so there should be a count register in dma.
> 
> 	I found the count register but I do not found correlative api in dmaengine, I think we should add one.
> 	Even during a single or multi buffer transfer, knowing how many data has been transfer in current descriptor is necessary.
> 	Through that, we will not lose a data.
> 
> 	So there should be an api to get current descriptor receive data count.
> 	Or we could get current descriptor status , the status with count value?
> 
> 	I submit an patch to retrieve descriptor data transfer size.
> 	We use this to get data count .
> 	We use Atmel dma, but it could be a common demand.

See dmaengine_tx_status() - the residue is returned in struct dma_tx_state.
See the PL011 UART driver to see how this is used with a timeout interrupt.

  reply	other threads:[~2012-09-07 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  9:59 DMA: get data count of descriptor in dmaengine Song, Elen
2012-09-07 10:35 ` Russell King - ARM Linux [this message]
2012-09-10  3:26   ` Song, Elen

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=20120907103547.GD13739@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).