linux-kernel - Re: [PATCH V2] spi: tegra: add spi driver for SLINK controller

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: <20121030151451.GT4511@opensource.wolfsonmicro.com>
Date:	Tue, 30 Oct 2012 15:14:51 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	Stephen Warren <swarren@...dotorg.org>,
	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"spi-devel-general@...ts.sourceforge.net" 
	<spi-devel-general@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V2] spi: tegra: add spi driver for SLINK controller

On Tue, Oct 30, 2012 at 11:13:34AM +0530, Laxman Dewangan wrote:
> On Tuesday 30 October 2012 12:44 AM, Stephen Warren wrote:

> >I think it depends on DMAENGINE, not the specific driver now, doesn't it?

> Taking example from the mfd, we depends on particular driver, not
> from the core driver.
> I like to have this depends on Tegra20_apb_dma.

The reason MFDs do this is that the function drivers usually directly
reference the core driver in some way, for example by relying on data
structures it sets up.  With DMA that should all be hidden behind the
dmaengine API.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)