From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Subject: Re: HDA driver without interrupt
Date: Wed, 02 May 2012 14:28:15 -0500 [thread overview]
Message-ID: <4FA18ACF.7020106@linux.intel.com> (raw)
In-Reply-To: <4FA12E91.8050804@gmail.com>
On 5/2/2012 7:54 AM, liufc wrote:
> Hi guys,I'm trying to implement an alsa driver based on the Intel HDA
> driver.However due to some hardware defects,I'm not able to use
> interrupt.So I wonder whether there is a way to do the job without the
> help of interrupt.Can anyone give me a suggestion?
What interrupt are you talking about? ALSA has the ability to discard
periodic interrupts but the user-space code needs to explicitly request
this mode (eg PulseAudio/AudioHAL). Regular/legacy apps do need an
interrupt coming from the hardware.
-Pierre
next prev parent reply other threads:[~2012-05-02 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 12:54 HDA driver without interrupt liufc
2012-05-02 19:28 ` Pierre-Louis Bossart [this message]
2012-05-03 6:13 ` Clemens Ladisch
[not found] ` <CAOAAS1z7iA2excEt9cE45CBmQs=XUkigW6+A94zyp2BuRLBBcA@mail.gmail.com>
2012-05-03 8:37 ` Clemens Ladisch
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=4FA18ACF.7020106@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).