From: "Steve Sakoman" <sakoman@gmail.com>
To: Mark Brown <broonie@sirena.org.uk>
Cc: ext naveen krishna ch <naveenkrishna.ch@gmail.com>,
alsa-devel@alsa-project.org,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
Steve Sakoman <steve@sakoman.com>
Subject: Re: twl4030 asoc kcontrols and widgets
Date: Thu, 20 Nov 2008 07:39:14 -0800 [thread overview]
Message-ID: <5e088bd90811200739x537252efx94e3fbe4e2303180@mail.gmail.com> (raw)
In-Reply-To: <20081120141401.GG4539@sirena.org.uk>
On Thu, Nov 20, 2008 at 6:14 AM, Mark Brown <broonie@sirena.org.uk> wrote:
> On Thu, Nov 20, 2008 at 04:02:43PM +0200, Peter Ujfalusi wrote:
>
>> My plan is to add _all_ (ok, almost all) the features we can get with
>> TWLx030...
>> So instead of having 'only' one possible route from DACl2/DACR2, I have
>> implemented in a reverse order:
>
> ...
>
>> With this mode one can enable whatever combination of routing he/she
>> needs from TWL.
>
>> Since these channels are really 'independent' inside of TWL, making the
>> routing/mixing flexible (you might say extremely flexible) could make
>> sense.
>
> This is good - an ASoC codec driver should expose as much functionality
> of the codec as possible and let user space configure it at runtime.
> See for example the WM8900 or WM8990 drivers for examples of codecs with
> fairly complex audio routing.
Agreed! This is a really good thing to do.
Had I not been under a lot of time pressure when doing the original
version of the driver I would have taken this approach myself.
I'm glad to see that you are tackling this. Peter, you should post
your patches for comment. Might help speed things along if we get
more folks looking and contributing.
Steve
next prev parent reply other threads:[~2008-11-20 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 9:38 twl4030 asoc kcontrols and widgets naveen krishna ch
2008-11-20 10:52 ` Mark Brown
2008-11-20 14:02 ` Peter Ujfalusi
2008-11-20 14:14 ` Mark Brown
2008-11-20 15:39 ` Steve Sakoman [this message]
2008-11-21 9:49 ` Peter Ujfalusi
2008-11-21 15:49 ` Mark Brown
2008-11-20 14:17 ` naveen krishna ch
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=5e088bd90811200739x537252efx94e3fbe4e2303180@mail.gmail.com \
--to=sakoman@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=naveenkrishna.ch@gmail.com \
--cc=peter.ujfalusi@nokia.com \
--cc=steve@sakoman.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