From: Peter Hsiang <Peter.Hsiang@maxim-ic.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Dimitris Papastamos <dp@opensour>
Subject: synchronized block of register writes
Date: Wed, 6 Apr 2011 15:28:10 -0700 [thread overview]
Message-ID: <B2150E1E4418E1438554A300EA5040E40DAC77494E@ITSVLEX06.it.maxim-ic.internal> (raw)
Hi Mark and Everyone,
When a codec driver control handling function needs to write a group of registers without any other register of the same codec being written to in parallel by ALSA, what is the best way to do this under the snd-soc codec driver architecture? In the current architecture, does the driver's control handling function execute serially with other ALSA automated activities?
For example, the codec has filter coefficient data registers in a secondary registers "segment" i.e. a portion of the register map is banked, and the secondary bank is purely for coefficients and they do not require caching. The coefficient registers share the same register numbers as those in the normal primary segment. To write the coefficients, one would first write to a register bit to select the desired segment, and then switch back when done. This means when writing the coefficients, I use the un-cached write.
Thanks in advance for your sound advice.
Peter
next reply other threads:[~2011-04-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:28 Peter Hsiang [this message]
2011-04-06 22:48 ` synchronized block of register writes Mark Brown
2011-04-07 0:01 ` Peter Hsiang
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=B2150E1E4418E1438554A300EA5040E40DAC77494E@ITSVLEX06.it.maxim-ic.internal \
--to=peter.hsiang@maxim-ic.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dp@opensour \
--cc=lrg@slimlogic.co.uk \
--cc=perex@perex.cz \
--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 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.