| 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
| ||
|
Message-ID: <4FF1D083.7060207@wwwdotorg.org> Date: Mon, 02 Jul 2012 10:46:59 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Laxman Dewangan <ldewangan@...dia.com>, broonie@...nsource.wolfsonmicro.com CC: tiwai@...e.de, perex@...ex.cz, swarren@...dia.com, lrg@...com, alsa-devel@...a-project.org, linux-kernel@...r.kernel.org, linux-tegra@...r.kernel.org Subject: Re: [PATCH] ASoC: tegra: use dmaengine based dma driver On 06/29/2012 05:34 AM, Laxman Dewangan wrote: > Use the dmaengine based Tegra APB DMA driver for > data transfer between SPI fifo and memory in > place of legacy Tegra APB DMA. > > Because generic soc-dmaengine-pcm uses the DMAs API > based on dmaengine, using the exported APIs provided > by this generic driver. > > The new driver is selected if legacy driver is not > selected and new dma driver is enabled through config > file. > > Signed-off-by: Laxman Dewangan <ldewangan@...dia.com> Acked-by: Stephen Warren <swarren@...dotorg.org> Tested-by: Stephen Warren <swarren@...dotorg.org> (Tested on Cardhu/Tegra30. It fails on Whistler/Tegra20, but I assume that's due to a bug in the dmaengine driver not this patch. There won't be a regression when applying this patch since we haven't switched to dmaengine as the default yet). -- 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/
Powered by blists - more mailing lists