From: Vinod Koul <vinod.koul@intel.com>
To: Robert Baldyga <r.baldyga@samsung.com>
Cc: dan.j.williams@intel.com, lars@metafoo.de,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
m.szyprowski@samsung.com, l.czerwinski@samsung.com,
kyungmin.park@samsung.com, k.kozlowski@samsung.com,
padma.kvr@gmail.com
Subject: Re: [PATCH v2 0/2] dma: pl330: improve status checking
Date: Tue, 9 Dec 2014 14:46:09 +0530 [thread overview]
Message-ID: <20141209091609.GB16827@intel.com> (raw)
In-Reply-To: <1417767955-5480-1-git-send-email-r.baldyga@samsung.com>
On Fri, Dec 05, 2014 at 09:25:53AM +0100, Robert Baldyga wrote:
> Hi,
>
> This series allows to check DMA transfer residue (number of bytes left
> to send/receive) by modifying pl330_tx_status() function, when struct
> dma_tx_state is filled with needed data. It also introduces DMA_PAUSE
> feature, which allows to halt DMA transfer before termination and read
> residue without risk of data loss.
>
> This features are needed for proper implementation of DMA transfers,
> particulary for serial drivers when transfer sizes are unknown and
> requests on DMA channels are terminated before transfer completion
> very ofter (it's becouse we terminate then in timeout interrupt to
> avoid latency which is usually undesirable).
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2014-12-09 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 8:25 [PATCH v2 0/2] dma: pl330: improve status checking Robert Baldyga
2014-12-05 8:25 ` [PATCH v2 1/2] dma: pl330: improve pl330_tx_status() function Robert Baldyga
2014-12-05 8:25 ` [PATCH v2 2/2] dma: pl330: add DMA_PAUSE feature Robert Baldyga
2014-12-09 9:16 ` Vinod Koul [this message]
2014-12-10 11:01 ` [PATCH v2 0/2] dma: pl330: improve status checking Robert Baldyga
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=20141209091609.GB16827@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=l.czerwinski@samsung.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=padma.kvr@gmail.com \
--cc=r.baldyga@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.