linux-kernel - Re: [PATCH/RFC] dmaengine: add a slave parameter to __dma_request

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, 3 Apr 2012 22:36:32 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Guennadi Liakhovetski <g.liakhovetski@....de>,
	Vinod Koul <vinod.koul@...el.com>,
	linux-kernel@...r.kernel.org,
	Jassi Brar <jassisinghbrar@...il.com>,
	Magnus Damm <magnus.damm@...il.com>,
	Paul Mundt <lethal@...ux-sh.org>
Subject: Re: [PATCH/RFC] dmaengine: add a slave parameter to __dma_request_channel()

On Fri, Mar 30, 2012 at 12:38 PM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Fri, Mar 30, 2012 at 07:44:09AM +0200, Linus Walleij wrote:
>> However you're right (in some later mail) that we need to distinguish
>> between RX/TX channels at this point, so I can agree we need some
>> additional parameter, but that should be very abstract, not containing
>> any custom stuff or any void * or something like that.
>
> No you don't.  DMA engines can generally deal with transfers operating in
> either direction on a single channel.

You're right, and I came to think of it out of reach from a computer.
The MMC on the RealViews and U300 indeed works like that.
And there has to be one way of doing this instead of hooking it
in at channel selection time, config-time is it.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/