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] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 3 Jul 2015 17:10:46 +0300
From:	Peter Ujfalusi <peter.ujfalusi@...com>
To:	Vinod Koul <vinod.koul@...el.com>
CC:	Tony Lindgren <tony@...mide.com>, <linux-kernel@...r.kernel.org>,
	<dmaengine@...r.kernel.org>, <linux-omap@...r.kernel.org>,
	<misael.lopez@...com>
Subject: Re: [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support for eDMA

On 07/02/2015 06:56 PM, Vinod Koul wrote:
> On Wed, Jul 01, 2015 at 03:41:26PM +0300, Peter Ujfalusi wrote:
>> Hi,
>>
>> On 06/08/2015 04:22 PM, Peter Ujfalusi wrote:
>>> Hi,
>>>
>>> Changes since v01:
>>> - Drop change in compatible for the crossbar driver and do the configuration
>>>   based on the DT structure.
>>>
>>> The ti-dma-crossbar driver in it's current form can work when it is used with
>>> sDMA (omap-dma). On DRA7x class of devices we have both sDMA and eDMA available.
>>> The sDMA driver expects to get the DMA request line with offset 1. The eDMA
>>> stack does not need the offset.
>>> The crosbbar itself is identical for sDMA and eDMA.
>>> At probe time the driver will do a match to figure out which dma engine it is
>>> connected to and based on that information it will configure the offset needed
>>> by the DMA driver.
>>
>> Gentle ping, it has been almost a month ago this series has been sent.
> Sorry I seem to have missed this series. I relooked at this and it looks
> fine. I will apply it once rc1 is out. If it needs rebase please resend

No problem,
the patch still applies cleanly.

Thanks,
Péter
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ