From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: The Linux Audio Developers' Mailing List
<linux-audio-dev@music.columbia.edu>,
alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Re: [linux-audio-dev] muse and /dev/rtc
Date: Mon, 22 Nov 2004 19:32:39 -0500 [thread overview]
Message-ID: <1101169959.3689.19.camel@krustophenia.net> (raw)
In-Reply-To: <s5hekilvho7.wl@alsa2.suse.de>
On Mon, 2004-11-22 at 19:54 +0100, Takashi Iwai wrote:
> Yes, I agree that ALSA timer API would be useful for such a case. The
> app can reject to run or do some workaround if the queried timer
> resolution is worse than requirements.
>
> Well, my guess for the next reaction is "the lack of documentation" ;)
I think the only issue is that adding timer support to a driver is not
documented. I did not even know ALSA had a timer API until it was
pointed out to me on the list, as the driver guide was my main
reference. Adding a chapter to the guide would ensure that new drivers
get timer support.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-23 0:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200411202259.57503.lad@koloro.de>
[not found] ` <20041122150120.GB20860@bth05w.ABSp.alcatel.be>
[not found] ` <Pine.LNX.4.58.0411221633160.23424@wotan.suse.de>
[not found] ` <200411221813.23092.rj@spamatica.se>
[not found] ` <20041122175312.GA20957@bth05w.ABSp.alcatel.be>
2004-11-22 18:21 ` [linux-audio-dev] muse and /dev/rtc Lee Revell
2004-11-22 18:54 ` Takashi Iwai
2004-11-23 0:32 ` Lee Revell [this message]
2004-11-23 0:09 ` Fons Adriaensen
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=1101169959.3689.19.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-audio-dev@music.columbia.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox