From: Robert Baldyga <r.baldyga@samsung.com>
To: Vinod Koul <vinod.koul@intel.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: Wed, 10 Dec 2014 12:01:53 +0100 [thread overview]
Message-ID: <54882821.2010106@samsung.com> (raw)
In-Reply-To: <20141209091609.GB16827@intel.com>
Hi,
On 12/09/2014 10:16 AM, Vinod Koul wrote:
> 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
>
I have found bug in my patches in series v2. There was double
pm_runtime_put() call. I have fixed it in v3, which is already sent to list.
Thanks,
Robert Baldyga
prev parent reply other threads:[~2014-12-10 11:01 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 ` [PATCH v2 0/2] dma: pl330: improve status checking Vinod Koul
2014-12-10 11:01 ` Robert Baldyga [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=54882821.2010106@samsung.com \
--to=r.baldyga@samsung.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=vinod.koul@intel.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