linux-kernel - Re: [PATCH] dmaengine: omap-dma: Fix the port

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]

Message-ID: <20170110053845.GX3573@localhost>
Date:   Tue, 10 Jan 2017 11:08:45 +0530
From:   Vinod Koul <vinod.koul@...el.com>
To:     Peter Ujfalusi <peter.ujfalusi@...com>
Cc:     dan.j.williams@...el.com, tony@...mide.com, linux@...linux.org.uk,
        dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, arnd@...db.de
Subject: Re: [PATCH] dmaengine: omap-dma: Fix the port_window support

On Mon, Jan 09, 2017 at 04:50:52PM +0200, Peter Ujfalusi wrote:
> We do not yet have users of port_window. The following errors were found
> when converting the tusb6010_omap.c musb driver:
> 
> - The peripheral side must have SRC_/DST_PACKED disabled
> - when configuring the burst for the peripheral side the memory side
>   configuration were overwritten: d->csdp = ... -> d->csdp |= ...
> - The EI and FI were configured for the wrong sides of the transfers.
> 
> With these changes and the converted tus6010_omap.c I was able to verify
> that things are working as they expected to work.

Applied now to fixes

-- 
~Vinod