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:   Mon, 12 Sep 2016 11:38:21 +0200
From:   Sylwester Nawrocki <s.nawrocki@...sung.com>
To:     Sam Van Den Berge <sam.van.den.berge@...enet.be>
Cc:     Krzysztof Kozlowski <krzk@...nel.org>,
        Arnd Bergmann <arnd@...db.de>,
        Krzysztof Kozlowski <k.kozlowski@...sung.com>,
        Olof Johansson <olof@...om.net>,
        Kevin Hilman <khilman@...nel.org>, arm@...nel.org,
        Kukjin Kim <kgene@...nel.org>,
        linux-arm-kernel@...ts.infradead.org,
        linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Subject: Re: [GIT PULL 1/4] ARM: exynos: SoC/Mach for v4.9

On 09/08/2016 09:24 PM, Sam Van Den Berge wrote:
> Thanks for the suggestion and apologies for the late response. Last couple of 
> days I've been figuring out what this would involve and I decided that I want
> to give this a try. I found this patch series [1] that I'll use as an example.
> If I understand it correctly, I'll need to create a dma_slave_map and
> pass that via the platform data into the s3c24xx-dma driver. There I'll
> need to fill in the filter_map of the dma slave device. Right?

Yes, AFAIU that's what needs to be done.  Subsequently, related DMA
clients could be updated to not use dma_request_slave_channel_compat().

-- 
Thanks,
Sylwester

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ