From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/3] ASoC: Add signal generator widget type
Date: Thu, 01 Dec 2011 15:55:14 +0000 [thread overview]
Message-ID: <1322754914.4712.5.camel@odin> (raw)
In-Reply-To: <20111201153050.GA28076@sirena.org.uk>
On Thu, 2011-12-01 at 15:30 +0000, Mark Brown wrote:
> On Thu, Dec 01, 2011 at 03:27:00PM +0000, Liam Girdwood wrote:
> > On Wed, 2011-11-30 at 20:57 +0000, Mark Brown wrote:
> > > A signal generator behaves as an input would but is not considered for
> > > any of the special behaviour associated with external input pins. This
> > > is especially useful when automatically working out not connected widgets.
>
> > Would this not be an output type ?
>
> It's a signal source - in terms of the DAPM graph and figuring out a
> route from an input to an output it's an input.
Ah, OK - I'm thinking here of an internal signal generator (i.e. coming
from within platform/codec). e.g. we could add a simple sine wave
generator to OMAP4 ABE for test/debug purposes.
Regards
Liam
next prev parent reply other threads:[~2011-12-01 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 20:57 [PATCH 1/3] ASoC: Add signal generator widget type Mark Brown
2011-11-30 20:57 ` [PATCH 2/3] ASoC: Make WM5100 tone generator widgets signal generators Mark Brown
2011-11-30 20:57 ` [PATCH 3/3] ASoC: Make WM8962 beep a signal generator Mark Brown
2011-12-01 15:27 ` [PATCH 1/3] ASoC: Add signal generator widget type Liam Girdwood
2011-12-01 15:30 ` Mark Brown
2011-12-01 15:55 ` Liam Girdwood [this message]
2011-12-01 15:59 ` Mark Brown
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=1322754914.4712.5.camel@odin \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=patches@opensource.wolfsonmicro.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