From: "naveen krishna ch" <naveenkrishna.ch@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, Steve Sakoman <steve@sakoman.com>
Subject: Re: twl4030 asoc kcontrols and widgets
Date: Thu, 20 Nov 2008 19:47:34 +0530 [thread overview]
Message-ID: <ef0d8a250811200617s49f2abao5676e085a2b71d17@mail.gmail.com> (raw)
In-Reply-To: <200811201602.44035.peter.ujfalusi@nokia.com>
On Thu, Nov 20, 2008 at 7:32 PM, Peter Ujfalusi <peter.ujfalusi@nokia.com>wrote:
> Hello,
>
> I have been also working on the twl4030 codec driver for some time now.
> Altrough my patchset is not yet ready, but I'd like to be heard early
> enough:
> 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:
> For all outputs (HSOL/R, PreDriveL/R, HFL/R IHFL/R, EAR) one can select
> from where the audio is routed.
> For example:
> PreDriveL can output audio from Voice, DACL1, DACL2, DACR2
> PreDriveR can output audio from Voice, DACR1, DACR2, DACL2
> HSOL can output audio from Voice, DACL1, DACL2
> HSOR can output audio from Voice, DACR1, DACR2
> and the list goes on...
> 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.
>
> CCing: Steve Sakoman who actually wrote the driver - could cc Mark Brown
> as well, but it seams that he is reading alsa-devel quite frequently ;)
>
> What do you think?
Great job.
In my case being a custom board the other paths (DACL1 and Voice) and Pre
car kit are not configured.
Routing that way would get full CODEC into use and using DAPM events then
would really give their best.
>
> --
> Péter
>
> On Thursday 20 November 2008 11:38:33 ext naveen krishna ch wrote:
> > Hi Alsa devel,
> >
> > I have been working on TWL4030 codec driver for ALSA SOC.
> > I have taken sound/soc/codec/twl4030.c as reference from main line
> >
> > This Patch adds some kcontrols, widgets and interconnection map for some
> of
> > the TWL4030 ASOC codec
> > I was building it for a custom board as it was for OVERO
> >
> >
> > Suggestions on the DAPM part of the driver would be helpful
> >
> > Thanks in advance.
> >
> > The patch is as follows.
> > I need suggestions on the DAPM part of the driver.
> >
> > Thanks and Regards,
> >
> > (: Naveen Krishna Ch :)
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
>
--
Thanks,
keep smiling...
keep winning...
(: Naveen Krishna Ch :)
prev parent reply other threads:[~2008-11-20 14:17 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
2008-11-21 9:49 ` Peter Ujfalusi
2008-11-21 15:49 ` Mark Brown
2008-11-20 14:17 ` naveen krishna ch [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=ef0d8a250811200617s49f2abao5676e085a2b71d17@mail.gmail.com \
--to=naveenkrishna.ch@gmail.com \
--cc=alsa-devel@alsa-project.org \
--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