linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/9] ASoC: tegra: move to generic DMA DT binding
Date: Wed, 24 Jul 2013 08:58:27 +0200	[thread overview]
Message-ID: <51EF7B13.4050207@metafoo.de> (raw)
In-Reply-To: <1374639002-16753-8-git-send-email-rizhao@nvidia.com>

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

  reply	other threads:[~2013-07-24  6:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  4:09 [PATCH 0/9] ARM: tegra: move to generic DMA DT binding Richard Zhao
2013-07-24  4:09 ` [PATCH 1/9] ARM: dts: add generic DMA DT binding for tegra apbdma Richard Zhao
2013-07-26 19:21   ` Stephen Warren
2013-07-30  2:54     ` Richard Zhao
2013-07-30 16:49       ` Stephen Warren
2013-08-01  2:49         ` Richard Zhao
2013-07-24  4:09 ` [PATCH 2/9] dma: tegra20-apbdma: move to generic device tree bindings Richard Zhao
2013-07-26 19:27   ` Stephen Warren
2013-07-30  3:06     ` Richard Zhao
2013-07-30 16:44       ` Stephen Warren
2013-07-31  3:52         ` Richard Zhao
2013-07-31 21:33           ` Stephen Warren
2013-07-24  4:09 ` [PATCH 3/9] spi: tegra114: move to generic dma DT binding Richard Zhao
2013-07-26 19:34   ` Stephen Warren
2013-07-30  3:15     ` Richard Zhao
2013-07-30 16:44       ` Stephen Warren
2013-07-24  4:09 ` [PATCH 4/9] spi: tegra20-slink: " Richard Zhao
2013-07-24  4:09 ` [PATCH 5/9] spi: tegra20-sflash: " Richard Zhao
2013-07-26 19:36   ` Stephen Warren
2013-07-30  3:16     ` Richard Zhao
2013-07-24  4:09 ` [PATCH 6/9] serial: tegra: " Richard Zhao
2013-07-26 19:39   ` Stephen Warren
2013-07-26 19:41     ` Stephen Warren
2013-07-30  3:31     ` Richard Zhao
2013-07-30 16:46       ` Stephen Warren
2013-07-31  3:45         ` Richard Zhao
2013-07-31 21:32           ` Stephen Warren
2013-08-01  3:30             ` Richard Zhao
2013-08-01  3:45               ` Stephen Warren
2013-07-24  4:10 ` [PATCH 7/9] ASoC: tegra: move to generic DMA " Richard Zhao
2013-07-24  6:58   ` Lars-Peter Clausen [this message]
2013-07-26 19:58   ` Stephen Warren
2013-07-30 10:12     ` Richard Zhao
2013-07-30 16:54       ` Stephen Warren
2013-07-24  4:10 ` [PATCH 8/9] ARM: dts: tegra: remove legacy nvidia, dma-request-selector properties Richard Zhao
2013-07-26 19:59   ` Stephen Warren
2013-07-30 10:16     ` [PATCH 8/9] ARM: dts: tegra: remove legacy nvidia,dma-request-selector properties Richard Zhao
2013-07-24  4:10 ` [PATCH 9/9] dma: tegra20-apbdma: remove legacy nvidia, dma-request-selector support Richard Zhao
2013-07-26 19:25 ` [PATCH 0/9] ARM: tegra: move to generic DMA DT binding Stephen Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51EF7B13.4050207@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).