linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: elen.song@atmel.com (corp\elen.song)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] DMA: AT91: Fix get residue function in at_hdmac.c
Date: Wed, 13 Mar 2013 12:00:13 +0800	[thread overview]
Message-ID: <513FF9CD.2010809@atmel.com> (raw)
In-Reply-To: <1354871458-13930-1-git-send-email-elen.song@atmel.com>

On 12/7/2012 5:10 PM, Elen Song wrote:
> The residue actually means the bytes remain in transfer identified by current cookie.
> The get residue api did not return the correct values in at_hdmac.c.
> This patch serial focus on fix the issue.
>
> This patch serials is based on DMA: AT91: Get residual bytes in dma buffer v2.
> It is split into 3 aimed patch, the first one is to get transmit buswidth,
> the second one is to get resiude in cookie, it use the buswidth to get residual bytes,
> the third part is to handle the status that there are still some bytes remain in dma fifo.
>
> Compare to v2, this patch serials improve:
> 1) consider buswidth to get correct residue.
> 2) handle dma fifo empty status.
>
>
> Elen Song (3):
>    DMA: AT91: Add value about transmit buswidth
>    DMA: AT91: Get residual bytes in dma buffer
>    DMA: AT91: Check fifo empty
>
>   drivers/dma/at_hdmac.c      |  151 ++++++++++++++++++++++++++++++++++++++-----
>   drivers/dma/at_hdmac_regs.h |    5 ++
>   2 files changed, 139 insertions(+), 17 deletions(-)
>
Hi All:

Any new comments about this patch serial?
I verified this patch serial, it can smooth apply on 3.9-rc2 and the 
function is all right.

Best regards
Elen Song

      reply	other threads:[~2013-03-13  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  9:10 [PATCH 0/3] DMA: AT91: Fix get residue function in at_hdmac.c Elen Song
2013-03-13  4:00 ` corpelen.song [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=513FF9CD.2010809@atmel.com \
    --to=elen.song@atmel.com \
    --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).