alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Babu, Ramesh" <ramesh.babu@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: ASoC: Configuring codec PCM port question
Date: Fri, 28 Jan 2011 13:19:02 +0000	[thread overview]
Message-ID: <20110128131902.GE10350@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <12D0C12AF19E15409D57F22566E88EF50937515E81@bgsmsx501.gar.corp.intel.com>

On Fri, Jan 28, 2011 at 06:30:59PM +0530, Babu, Ramesh wrote:

> I am thinking of following two options to configure PCM1 port:

> 1. AlSA Mixer control:  Create mixer control and provide options like VOICE_HS,
> 	VOICE_IHF, VOICE_EP and VOICE_DISABLE. Application will use one of the option to
> 	Configure the PCM1 port.

> 2. IOCTL : Application invokes IOCTL in hardware specific driver code and then it enables
> 	PCM1 port (cross-path DAPM ?) 

> Which is the best way to implement it?
> Are there any other existing way to implement it?

The current mainline solution to this is to do something like the
OpenMoko GTA02 or Samsung Aquilla and Goni do and represent the modem as
a dummy CPU DAI then use application code like this:

  http://opensource.wolfsonmicro.com/~gg/bluetooth-pcm/bluetooth_pcm.c

to start the audio - ie, run through everything except DMA.

There's some updates that I'd expect to see soon which will allow the
configuration for the hw_params() for the link to be baked into the
machine driver (I'll be doing that in the next couple of weeks) and
which will allow DAPM to propagate power over links between CODECs (Liam
has some work for that in his git, though he's still working on tidying
it up for mainline) which should make life much easier but it may be
easier for you to submit something now and then update later as the
support for this scenario improves.

      reply	other threads:[~2011-01-28 13:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 13:00 ASoC: Configuring codec PCM port question Babu, Ramesh
2011-01-28 13:19 ` Mark Brown [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=20110128131902.GE10350@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=ramesh.babu@intel.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).