linux-kernel - Re: [PATCH] dmaengine: rcar-dmac: use DMATCRB when xxx_TO

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:   Tue, 17 Oct 2017 00:18:49 +0000
From:   Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:     Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
Cc:     Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Dan Williams <dan.j.williams@...el.com>,
        Vinod Koul <vinod.koul@...el.com>,
        Niklas Söderlund 
        <niklas.soderlund+renesas@...natech.se>, dmaengine@...r.kernel.org,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Hiroyuki Yokoyama <hiroyuki.yokoyama.vx@...esas.com>
Subject: Re: [PATCH] dmaengine: rcar-dmac: use DMATCRB when xxx_TO_MEM direction


Hi

> Thank you for your explanation.
> My 1st patch focused to "transfer completed" count (= TCRB) for all case.
> In any case, "completed" information should be used.
> But in MEM_TO_DEV case, I thought if is OK if data was read from MEM
> (= the data will be send to DEV automatically, I didn't care about interruption)
> But yes, your opinion is correct I think.
> 
> I think MEM_TO_MEM should use TCRB.
> I think logic is same as your MEM_TO_DEV explanation ?
> 
> Anyway, in all case I can use TCRB in v3 patch,
> and it needs abouve explanation. 

If so, I think v1 is enough... ?
"transfer completed count is important for all case" is no doubt... ?

Best regards
---
Kuninori Morimoto