From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ASoC: dapm: Add new widget type for constructing DAPM graphs on DSPs.
Date: Wed, 14 Jun 2017 12:28:55 +0100 [thread overview]
Message-ID: <1497439735.30929.330.camel@loki> (raw)
In-Reply-To: <20170609175333.6ift3olr3thobopr@sirena.org.uk>
On Fri, 2017-06-09 at 18:53 +0100, Mark Brown wrote:
> On Fri, Jun 09, 2017 at 04:23:49PM +0100, Liam Girdwood wrote:
>
> > Changes v1.
> > o Added some documentation.
> > o Split codec widget into encoder and decoder to avoid confusion with HW
> > CODECS.
>
> Please put the inter-version changelogs after the --- so they get
> filtered out when applied.
>
> > +Pipeline
> > + Collection of widgets within a DSP, can represent a sequence of DSP
> > + widgets and their collective configuration.
> > +Effect
> > + Widget that performs an audio processing effect.
>
> I'm still a bit unclear about how a pipeline and effect are different
> from an ASoC point of view - it matters on the DSP but from the kernel's
> point of view a pipeline just an effect that happens to have a more
> complicated implementation on the DSP?
Sorry for the delay.
Yes, that's true, some of the objects will most likely be treated the
same by the kernel core but for the DSP and driver they will different.
i.e. they create different objects with different topology private data
(using the widget ID to differentiate).
Liam
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2017-06-14 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:23 [PATCH v2] ASoC: dapm: Add new widget type for constructing DAPM graphs on DSPs Liam Girdwood
2017-06-09 17:53 ` Mark Brown
2017-06-14 11:28 ` Liam Girdwood [this message]
2017-06-15 10:01 ` Mark Brown
2017-06-15 10:56 ` Liam Girdwood
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=1497439735.30929.330.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).