From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
lgirdwood@gmail.com
Subject: Re: [RFC PATCH] ASoC: wm_adsp: Change ADSPs to be mixer widgets rather the PGAs
Date: Wed, 18 Dec 2013 13:14:36 +0000 [thread overview]
Message-ID: <20131218131436.GE11138@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20131218112739.GH28455@sirena.org.uk>
On Wed, Dec 18, 2013 at 11:27:39AM +0000, Mark Brown wrote:
> On Wed, Dec 18, 2013 at 10:53:44AM +0000, Charles Keepax wrote:
>
> > Was also considering if it would be worth adding an
> > additional snd_soc_dapm_dsp id? That could sit between
> > mixers and pgas, but I can't really see any obvious issue
> > with treating the DSP as a mixer and it is a much simpler
> > change. Although I am open to writing the other change if it
> > is preferred?
>
> One of the issues here was trying to ensure that the DSP started up with
> its inputs stable so noise from them starting didn't propagage into the
> algorithm and confuse it. The expecation with putting it as a PGA was
> that it would start with the outputs mute and do a digital unmute to
> bring them up. Since everything is digital this should all be more
> robust than it would be for analogue.
Muting the output is a little tricky though as a graph walk will
be required to determine which output was connected, unless you
have any handy ideas I have not spotted? I will start having a
look to see what could be done on the muting front.
Thanks,
Charles
next prev parent reply other threads:[~2013-12-18 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 10:53 [RFC PATCH] ASoC: wm_adsp: Change ADSPs to be mixer widgets rather the PGAs Charles Keepax
2013-12-18 11:27 ` Mark Brown
2013-12-18 13:14 ` Charles Keepax [this message]
2013-12-18 13:23 ` Mark Brown
2013-12-18 14:14 ` Charles Keepax
2013-12-18 16:19 ` Mark Brown
2013-12-18 17:05 ` Charles Keepax
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=20131218131436.GE11138@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.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 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.