From: Hans-Christian Egtvedt <hcegtvedt@atmel.no>
To: alsa-devel@alsa-project.org
Subject: Is the mixer interface in the kernel protect against concurrent access?
Date: Mon, 17 Dec 2007 15:13:37 +0100 [thread overview]
Message-ID: <1197900817.1365.38.camel@localhost.localdomain> (raw)
Hi,
I am solving a locking bug in the at73c213 SPI sound driver, and
wondered if the mixer API is protected against concurrent access in
ALSA? Or should I implement a mutex to protect my hardware against
concurrent access?
--
Mvh
Hans-Christian Egtvedt
next reply other threads:[~2007-12-17 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 14:13 Hans-Christian Egtvedt [this message]
2007-12-17 15:43 ` Is the mixer interface in the kernel protect against concurrent access? Jaroslav Kysela
2007-12-17 16:07 ` Hans-Christian Egtvedt
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=1197900817.1365.38.camel@localhost.localdomain \
--to=hcegtvedt@atmel.no \
--cc=alsa-devel@alsa-project.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