linux-kernel - Re: [PATCH v2 0/2] dma: pl330: improve status checking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 10 Dec 2014 12:01:53 +0100
From:	Robert Baldyga <r.baldyga@...sung.com>
To:	Vinod Koul <vinod.koul@...el.com>
Cc:	dan.j.williams@...el.com, lars@...afoo.de,
	dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
	m.szyprowski@...sung.com, l.czerwinski@...sung.com,
	kyungmin.park@...sung.com, k.kozlowski@...sung.com,
	padma.kvr@...il.com
Subject: Re: [PATCH v2 0/2] dma: pl330: improve status checking

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/