Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Miguel Aguilar <miguel.aguilar@ridgerun.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	clark.becker@ridgerun.com, santiago.nunez@ridgerun.com, "Nori,
	Sekhar" <nsekhar@ti.com>,
	diego.dompe@ridgerun.com, alsa-devel@alsa-project.org,
	"Narnakaje, Snehaprabha" <nsnehaprabha@ti.com>,
	todd.fischer@ridgerun.com, lrg@slimlogic.co.uk
Subject: Re: [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM
Date: Wed, 20 Jan 2010 15:01:43 +0000	[thread overview]
Message-ID: <20100120150143.GA29114@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <4B5713F1.1050407@ridgerun.com>

On Wed, Jan 20, 2010 at 08:32:17AM -0600, Miguel Aguilar wrote:

> Ok, machine driver you mean sound/soc/davinci/davinci-evm.c file?

Yes.

> So at the moment I will use ifdef to choose by using the
> configuration menu one codec or the other one at time, as you said
> it should be straightforward to enable the AIC3x and the Voice Codec
> simultaneously.

Sounds like a plan - hopefully even just as part of the generic update
work.

  reply	other threads:[~2010-01-20 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 22:17 [PATCH 2/2] Davinci: DM365: Enable DaVinci Voice Codec support for DM365 EVM miguel.aguilar
2010-01-08 11:31 ` Mark Brown
2010-01-08 17:36   ` Miguel Aguilar
2010-01-08 19:37     ` Mark Brown
2010-01-11 15:11       ` Miguel Aguilar
2010-01-11 15:34         ` Mark Brown
2010-01-11 15:53           ` Miguel Aguilar
2010-01-11 16:21             ` Mark Brown
2010-01-19 20:47               ` Miguel Aguilar
2010-01-19 22:10                 ` Mark Brown
2010-01-20 14:32                   ` Miguel Aguilar
2010-01-20 15:01                     ` Mark Brown [this message]
2010-01-11 16:04 ` Kevin Hilman
2010-01-11 16:08   ` Miguel Aguilar

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=20100120150143.GA29114@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clark.becker@ridgerun.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=diego.dompe@ridgerun.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=miguel.aguilar@ridgerun.com \
    --cc=nsekhar@ti.com \
    --cc=nsnehaprabha@ti.com \
    --cc=santiago.nunez@ridgerun.com \
    --cc=todd.fischer@ridgerun.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