linux-kernel - Re: [PATCH 7/9] ASoC: tegra: move to generic DMA DT binding

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: <51EF7B13.4050207@metafoo.de>
Date:	Wed, 24 Jul 2013 08:58:27 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Richard Zhao <rizhao@...dia.com>
CC:	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org,
	linux-serial@...r.kernel.org, alsa-devel@...a-project.org,
	grant.likely@...aro.org, rob.herring@...xeda.com, rob@...dley.net,
	swarren@...dotorg.org, vinod.koul@...el.com, djbw@...com,
	broonie@...nel.org, gregkh@...uxfoundation.org,
	lgirdwood@...il.com, linuxzsc@...il.com, ldewangan@...dia.com,
	dev@...xeye.de
Subject: Re: [PATCH 7/9] ASoC: tegra: move to generic DMA DT binding

On 07/24/2013 06:10 AM, Richard Zhao wrote:
> - add tegra_dma_filter_data to specify dma info
>    DMA DT binding needs the device that raise dma request and dma name
>    to request a dma channel. tegra30_i2s is a special case. It should be ahub
>    device and it also has dma name that cannot handled by ASoC dmaengine code.
>    So we pass the info using filter data in snd_dmaengine_dai_dma_data.

How about extending the generic dmaengine PCM driver so that it is possible to 
specify the the DMA channel names? I think that will make the code a bit 
simpler and also allow you to remove tegra_pcm.c completely eventually.

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