From: Clemens Ladisch <clemens@ladisch.de>
To: "torsten.schenk" <torsten.schenk@zoho.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Card driver: device or resource busy
Date: Mon, 17 Jan 2011 08:46:20 +0100 [thread overview]
Message-ID: <4D33F3CC.1070202@ladisch.de> (raw)
In-Reply-To: <12d8ae03d3b.-1810748071142587921.-87582792196928800@zoho.com>
torsten.schenk wrote:
> I figured out that the difference between my driver and existing ones
> is, that my driver only allows one client and others multiple.
Very few devices can mix streams in hardware.
To get software mixing, you have to add the dmix plugin to the default
device for your card; see alsa-lib/src/conf/cards/.
> Another point (perhaps not unrelated to this) is, that I get a bug
> (see below) that seems to tell me, that prepare cannot schedule.
ALSA doesn't prevent the prepare callback from scheduling, but I'd guess
that your code disables interrupts somewhere.
Regards,
Clemens
prev parent reply other threads:[~2011-01-17 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 18:11 Card driver: device or resource busy torsten.schenk
2011-01-16 1:13 ` Raymond Yau
2011-01-17 7:46 ` Clemens Ladisch [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=4D33F3CC.1070202@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=torsten.schenk@zoho.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).