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: synchronized block of register writes
Date: Thu, 7 Apr 2011 07:48:53 +0900 [thread overview]
Message-ID: <20110406224851.GB5297@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <B2150E1E4418E1438554A300EA5040E40DAC77494E@ITSVLEX06.it.maxim-ic.internal>
On Wed, Apr 06, 2011 at 03:28:10PM -0700, Peter Hsiang wrote:
> Hi Mark and Everyone,
Fix your mailer to word wrap at 80 columns, I've reflowed your text.
> 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?
The framework should be taking care of locking for you in most
situations. If you implement custom controls you will want to take the
CODEC mutex while applying changes from them (most of the existing
drivers are lax about this) and similarly for IRQs.
next prev parent reply other threads:[~2011-04-06 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 22:28 synchronized block of register writes Peter Hsiang
2011-04-06 22:48 ` Mark Brown [this message]
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=20110406224851.GB5297@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 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.