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]

Message-ID: <1332227493.12110.21.camel@vkoul-udesk3>
Date:	Tue, 20 Mar 2012 12:41:33 +0530
From:	Vinod Koul <vinod.koul@...ux.intel.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	Russell King - ARM Linux <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	'Jassi Brar' <jassisinghbrar@...il.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	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 Mon, 2012-03-19 at 17:32 +0100, Guennadi Liakhovetski wrote:
> Sure. In the datasheet we have: to configure a channel for client 1 write 
> value X to register A and value Y to register B. That's it. One of them is 
> really just a magic slave ID. Another one has several fields with values 
> like bus width and transfer size. They could be passed "properly," but 
> since those fields also vary between DMAC versions, it is easier to just 
> fix the whole register value per client and pass it from the platform 
> data. In any case, at least the slave ID is really just a constant, that 
> cannot be calculated and has to be passed from platform data.
I think I like the idea of having the these slave IDs coming from
platform map. That way drivers can be agnostic...

-- 
~Vinod

--
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/