Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jarkko Nikula <jarkko.nikula@bitmer.com>
Subject: Re: [PATCH v2 0/4] ASoC: Regression fix for OMAP in DT boot (3.11)
Date: Thu, 11 Jul 2013 16:23:24 +0200	[thread overview]
Message-ID: <51DEBFDC.4000607@ti.com> (raw)
In-Reply-To: <51DEBAE2.6060709@metafoo.de>

On 07/11/2013 04:02 PM, Lars-Peter Clausen wrote:
> Looks good, all 4 patches:
> Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>

Thanks

> But I'm wondering who do you register the PCM device in the DT case? Do you
> have a separate DT node for the PCM device?

It is a platform_device right now registered in arch/arm/mach-omap2/devices.c
We do not have and I don't plan to have DT node for it. The device for the PCM
is registered if soc audio is selected for OMAP.

-- 
Péter

  reply	other threads:[~2013-07-11 14:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 12:35 [PATCH v2 0/4] ASoC: Regression fix for OMAP in DT boot (3.11) Peter Ujfalusi
2013-07-11 12:35 ` [PATCH v2 1/4] ASoC: omap-pcm: Request the DMA channel differently when DT is involved Peter Ujfalusi
2013-07-11 16:38   ` Mark Brown
2013-07-11 12:35 ` [PATCH v2 2/4] ASoC: omap-mcpdm: Do not use platform_get_resource_byname() for DMA Peter Ujfalusi
2013-07-11 12:35 ` [PATCH v2 3/4] ASoC: omap-dmic: " Peter Ujfalusi
2013-07-11 12:35 ` [PATCH v2 4/4] ASoC: omap-mcbsp: Use different method for DMA request when booted with DT Peter Ujfalusi
2013-07-11 14:02 ` [PATCH v2 0/4] ASoC: Regression fix for OMAP in DT boot (3.11) Lars-Peter Clausen
2013-07-11 14:23   ` Peter Ujfalusi [this message]
2013-07-11 16:36     ` Mark Brown

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=51DEBFDC.4000607@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@bitmer.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    /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