alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Rajashekhara, Sudhakar" <sudhakar.raj@ti.com>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	"davinci-linux-open-source@linux.davincidsp.com"
	<davinci-linux-open-source@linux.davincidsp.com>,
	"alsa-user@lists.sourceforge.net"
	<alsa-user@lists.sourceforge.net>, "Girdwood, Liam" <lrg@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: DT support for Davinci ASoC platform
Date: Thu, 05 Jul 2012 12:58:06 +0200	[thread overview]
Message-ID: <4FF5733E.6000604@gmail.com> (raw)
In-Reply-To: <1BAFE6F6C881BF42822005164F1491C33EA35352@DBDE01.ent.ti.com>

Hi Gururaja,

On 04.07.2012 14:48, Hebbar, Gururaja wrote:
> All,
> 
> Are there any plans or work going on for providing Device Tree Support for Davinci
> ASoC?
> 
> I am planning to add DT support for TI AM335x (McASP) and I don't want to do duplicate
> task.

That's good to know. But isn't there a dependency on the EDMA engine? Is
that part ported yet?


Daniel

  reply	other threads:[~2012-07-05 10:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 12:48 DT support for Davinci ASoC platform Hebbar, Gururaja
2012-07-05 10:58 ` Daniel Mack [this message]
2012-07-05 15:36   ` Arnd Bergmann
2012-07-05 16:05     ` Daniel Mack
     [not found]       ` <4FF5BB34.9070002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-06 13:12         ` [alsa-devel] " Sekhar Nori
2012-07-06 15:01       ` Arnd Bergmann
2012-08-02 20:32   ` Daniel Mack
2012-08-03  9:09     ` [alsa-devel] " Sekhar Nori
2012-08-08 13:36       ` Daniel Mack
2012-08-08 14:48         ` [alsa-devel] " Porter, Matt

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=4FF5733E.6000604@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=gururaja.hebbar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lrg@ti.com \
    --cc=nsekhar@ti.com \
    --cc=sudhakar.raj@ti.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;
as well as URLs for NNTP newsgroup(s).