linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 5/5] ASoC: pxa: add DT bindings for pxa2xx-pcm
Date: Mon, 12 Aug 2013 11:17:21 +0200	[thread overview]
Message-ID: <5208A821.6060604@gmail.com> (raw)
In-Reply-To: <5208A424.70704@metafoo.de>

On 12.08.2013 11:00, Lars-Peter Clausen wrote:
> On 08/12/2013 10:42 AM, Daniel Mack wrote:
>> The bindings do not carry any resources, as the module only registers
>> the ASoC platform driver.
>>
>> Signed-off-by: Daniel Mack <zonque@gmail.com>
> 
> As this is just a virtual device (and Linux specific) it shouldn't be in the 
> devicetree. Usually when using devicetree you'd register the PCM device from 
> the CPU DAI driver. Take a look at how other platforms (e.g. tegra) do this.

Ok, then please ignore this one for now.


Thanks,
Daniel

      reply	other threads:[~2013-08-12  9:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  8:42 [PATCH 0/5] ASoC: pxa dmaengine preparation patches Daniel Mack
2013-08-12  8:42 ` [PATCH 1/5] ALSA: move dmaengine implementation from ASoC to ALSA core Daniel Mack
2013-08-12  8:55   ` Daniel Mack
2013-08-15 10:18   ` Mark Brown
2013-08-12  8:42 ` [PATCH 2/5] ASoC: pxa: pxa-ssp: add DT bindings Daniel Mack
2013-08-15 10:33   ` Mark Brown
2013-08-15 10:51     ` Daniel Mack
2013-08-15 13:39       ` Mark Brown
2013-08-15 13:43         ` Daniel Mack
2013-08-15 14:01           ` Mark Brown
2013-08-12  8:42 ` [PATCH 3/5] ASoC: pxa: use snd_dmaengine_dai_dma_data Daniel Mack
2013-08-12  8:42 ` [PATCH 4/5] ASoC: pxa: pxa-ssp: set dma filter data from startup hook Daniel Mack
2013-08-12  8:42 ` [PATCH 5/5] ASoC: pxa: add DT bindings for pxa2xx-pcm Daniel Mack
2013-08-12  9:00   ` [alsa-devel] " Lars-Peter Clausen
2013-08-12  9:17     ` Daniel Mack [this message]

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=5208A821.6060604@gmail.com \
    --to=zonque@gmail.com \
    --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).