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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 4 Apr 2017 17:43:18 +0100
From:   Jose Abreu <>
To:     Andy Shevchenko <>,
        Jose Abreu <>,
        Vinod Koul <>
CC:     "" <>,
        "" <>,
Subject: Re: dmaengine: dw-dmac: Custom cyclic API (Why?)

Hi Andy,

On 04-04-2017 17:23, Andy Shevchenko wrote:
> On Mon, 2017-01-02 at 13:56 +0000, Jose Abreu wrote:
>> On 02-01-2017 11:30, Andy Shevchenko wrote:
>>> On Mon, 2017-01-02 at 15:48 +0530, Vinod Koul wrote:
>>>> On Mon, Jan 02, 2017 at 10:38:00AM +0200, Andy Shevchenko wrote:
>>>>> On Fri, 2016-12-30 at 12:05 +0000, Jose Abreu wrote:
>>> Actually we have AVR32 connected to our lab. So, I can test it
>>> there,
>>> but I rather need a patch to use some dummy stub instead of codec
>>> (it
>>> has no codec connected).
>> Thank you all for the info. I don't have the HW ready to test yet
>> (I was collecting some info first), but when I do I can test on
>> my side using Designware I2S and ALSA SoC DMA engine.
> Just TWIMC, AVR32 is going to be removed from kernel.
> It means in particularly I will follow up and remove related bits in
> dw_dmac driver, including custom cyclic API.

Thanks for sharing this! Unfortunately the plans to include a DMA
for I2S audio were postponed so I never got to the point of
implementing/testing it. As I don't see any plans in using this
cyclic DMA for now I guess if I need to use it I will implement
it again using the standard cyclic DMA engine API.

Best regards,
Jose Miguel Abreu

Powered by blists - more mailing lists