From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Hsiang <Peter.Hsiang@maxim-ic.com>
Cc: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: Dynamic control commands that match the downloadable DSP firmware
Date: Thu, 7 Apr 2011 08:18:57 +0900 [thread overview]
Message-ID: <20110406231855.GD5297@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B2150E1E4418E1438554A300EA5040E40DAC774969@ITSVLEX06.it.maxim-ic.internal>
On Wed, Apr 06, 2011 at 03:51:49PM -0700, Peter Hsiang wrote:
> Hi Mark and Everyone,
As previously mentioned fix your mail client to word wrap within
paragraphs. Not doing this makes your mails very hard to read and reply
to. I've reflowed your text.
> Rather than hard coding the control commands in the driver directly,
> wouldn't it be cool if, in addition to the firmware being loaded from
> file, the control commands information can be loaded from file as
> well. Then the driver would dynamically create and install the
> control commands the same way we already do for the EQ.
Yes, this is one of the topics that's on the agenda for the ASoC
conference next month. There's some tricks here as for many DSPs there
are sequencing requirements for updating the controls, especially things
like coefficient banks, or constraints on which firmware features can be
active simultaneously both of which make a purely data driven approach
more complex than it could be.
With more complex systems it's not just controls but also DAPM that can
need updating, and of course we also need to manage changing firmwares
at runtime and convincing firmware vendors to supply data that ALSA can
comprehend.
prev parent reply other threads:[~2011-04-06 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:51 Dynamic control commands that match the downloadable DSP firmware Peter Hsiang
2011-04-06 23:18 ` Mark Brown [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=20110406231855.GD5297@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Peter.Hsiang@maxim-ic.com \
--cc=alsa-devel@alsa-project.org \
--cc=dp@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=lrg@slimlogic.co.uk \
--cc=tiwai@suse.de \
/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