From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jarkko.nikula@nokia.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [asoc-dev][RFC/PATCH 0/2] Generic DAPM register modifier widget
Date: Wed, 25 Jun 2008 16:40:33 +0100 [thread overview]
Message-ID: <1214408433.3877.103.camel@localhost.localdomain> (raw)
In-Reply-To: <20080625151555.81154289.jarkko.nikula@nokia.com>
On Wed, 2008-06-25 at 15:15 +0300, Jarkko Nikula wrote:
> On Wed, 25 Jun 2008 13:01:20 +0100
> "ext Liam Girdwood" <lg@opensource.wolfsonmicro.com> wrote:
>
> > > So I came with this idea of generic register modifiers widget and
> > > event handler for it.
> > >
> >
> > Any chance you could also add a little text to
> > Docs/sound/alsa/soc/dapm.txt for this.
> >
> Documentation? That's difficult and actually forgot it completely :-)
>
> But is it documented already? "There are convience macros defined in
> soc-dapm.h that can be used to quickly build a list of widgets of the
> codecs and machines DAPM widgets."
>
Sorry, just to clarify, I was meaning 1 line in section 2 of dapm.txt
(the widget type table). Just a little description next to the others.
Thanks
Liam
next prev parent reply other threads:[~2008-06-25 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 11:42 [asoc-dev][RFC/PATCH 0/2] Generic DAPM register modifier widget Jarkko Nikula
2008-06-25 11:42 ` [asoc-dev][RFC/PATCH 1/2] ASoC: Add support for generic " Jarkko Nikula
2008-06-25 11:59 ` Liam Girdwood
2008-06-25 11:42 ` [asoc-dev][RFC/PATCH 2/2] ASoC: TLV320AIC3X: Use register modifier widget for mic bias Jarkko Nikula
2008-06-25 12:00 ` Liam Girdwood
2008-06-25 12:01 ` [asoc-dev][RFC/PATCH 0/2] Generic DAPM register modifier widget Liam Girdwood
2008-06-25 12:15 ` Jarkko Nikula
2008-06-25 15:40 ` Liam Girdwood [this message]
2008-06-26 10:11 ` Jarkko Nikula
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=1214408433.3877.103.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jarkko.nikula@nokia.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 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.