From: Tanu Kaskinen <tanuk@iki.fi>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Arun Raghavan <arun.raghavan@collabora.co.uk>,
jankovac503@gmail.com, Liam Girdwood <lrg@ti.com>,
alsa-devel@alsa-project.org,
pulseaudio-discuss@lists.freedesktop.org
Subject: Re: [pulseaudio-discuss] Using UCM with PulseAudio
Date: Fri, 15 Jun 2012 20:38:08 +0300 [thread overview]
Message-ID: <1339781888.3007.153.camel@laptop> (raw)
In-Reply-To: <20120615173441.GN4482@opensource.wolfsonmicro.com>
On Fri, 2012-06-15 at 18:34 +0100, Mark Brown wrote:
> On Fri, Jun 15, 2012 at 06:28:51PM +0100, Liam Girdwood wrote:
> > On Fri, 2012-06-15 at 15:11 +0300, Tanu Kaskinen wrote:
>
> > > This sort of hardware causes trouble for the planned routing system, at
> > > least as I have envisioned it to behave. My vision has been that the
> > > routing logic in pulseaudio would enable and disable ports based on the
> > > streams that exist and their properties. In the OMAP4 case, there aren't
> > > any streams created when a cellular call starts, and therefore the
> > > routing logic doesn't know that it should do something.
>
> > This is quite common in the smartphone voice call use case. A lot of
>
> It's more than common, I'm only aware of one phone design which does
> route the audio via the CPU on call (the N900). Anything that can't
> cope with bypassed on call audio is going to struggle.
N9 also routes the audio via the CPU. Now you know two phone designs :)
--
Tanu
next prev parent reply other threads:[~2012-06-15 17:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 2:53 Using UCM with PulseAudio Arun Raghavan
2012-06-15 12:11 ` [pulseaudio-discuss] " Tanu Kaskinen
2012-06-15 17:28 ` Liam Girdwood
2012-06-15 17:34 ` Mark Brown
2012-06-15 17:38 ` Tanu Kaskinen [this message]
2012-07-23 3:38 ` Arun Raghavan
2012-07-23 6:33 ` Tanu Kaskinen
2012-07-23 10:06 ` Mark Brown
2012-07-23 7:57 ` Mark Brown
2012-06-15 12:28 ` Mark Brown
2012-06-15 17:08 ` Liam Girdwood
2012-06-20 12:30 ` Arun Raghavan
2012-06-21 2:50 ` Gabriel M. Beddingfield
2012-06-25 1:25 ` Arun Raghavan
2012-06-21 8:30 ` [alsa-devel] " Feng Wei
2012-06-25 1:31 ` Arun Raghavan
2012-06-25 16:28 ` Arun Raghavan
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=1339781888.3007.153.camel@laptop \
--to=tanuk@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=arun.raghavan@collabora.co.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jankovac503@gmail.com \
--cc=lrg@ti.com \
--cc=pulseaudio-discuss@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.