From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lg@opensource.wolfsonmicro.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 3/3] asoc tlv320aic3x: add more routing controls
Date: Fri, 25 Apr 2008 11:57:57 +0100 [thread overview]
Message-ID: <20080425105757.GC22926@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1209119680.3286.167.camel@localhost.localdomain>
On Fri, Apr 25, 2008 at 11:34:40AM +0100, Liam Girdwood wrote:
> The main problem I think we have on phones is that the audio routing is
> incredibly complex compared to a PC. i.e. a lot of mixers/controls have
> to be changed when we have a use case change.
It's also proved a substantial win for users to be able to use
interactive applications like alsamixer to set up the audio paths that
they need for their system rather than having to write kernel code -
it's much less of a learning curve for people for whom audio is just one
part of the system they're trying to put together.
I guess the other thing with the sort of systems that use ASoC is that
it's generally only developers who ever see the actual ALSA API in the
sort of systems that use ASoC. Unlike desktop systems end users will
typically see a device or application specific user interface of some
kind that shows them only a very small subset of the available controls.
next prev parent reply other threads:[~2008-04-25 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 9:18 [PATCH 3/3] asoc tlv320aic3x: add more routing controls Daniel Mack
2008-04-25 9:22 ` Takashi Iwai
2008-04-25 9:30 ` Daniel Mack
2008-04-25 9:42 ` Takashi Iwai
2008-04-25 10:34 ` Liam Girdwood
2008-04-25 10:36 ` Liam Girdwood
2008-04-25 10:57 ` Mark Brown [this message]
2008-04-25 13:10 ` Takashi Iwai
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=20080425105757.GC22926@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lg@opensource.wolfsonmicro.com \
--cc=tiwai@suse.de \
/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.