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
| ||
|
Date: Sun, 14 May 2017 18:40:08 +0530 From: Vinod Koul <vinod.koul@...el.com> To: Peter Ujfalusi <peter.ujfalusi@...com> Cc: b-liu@...com, tony@...mide.com, gregkh@...uxfoundation.org, linux-usb@...r.kernel.org, linux-omap@...r.kernel.org, balbi@...nel.org, linux-kernel@...r.kernel.org, Russell King <linux@...linux.org.uk>, dmaengine@...r.kernel.org, dan.j.williams@...el.com Subject: Re: [PATCH v3 1/9] dmaengine: omap-dma: port_window support correction for both direction On Fri, May 12, 2017 at 04:57:44PM +0300, Peter Ujfalusi wrote: > When the port_window support was verified it was done on setup where only > the MEM_TO_DEV direction was enabled. This got un-noticed and thus only > this direction worked. > > Now that I have managed to get a setup to verify both direction it turned > out that the setup was incorrect: > omap_desc members are settings for the slave port while the omap_sg members > apply to the memory side of the sDMA setup. Acked-by: Vinod Koul <vinod.koul@...el.com> -- ~Vinod
Powered by blists - more mailing lists