Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Jaroslav Kysela <perex@suse.cz>
Subject: Re: RFC: Add support for monotonic clock for 2.6
Date: Wed, 07 Mar 2007 22:33:25 +0000	[thread overview]
Message-ID: <45EF3DB5.3090008@superbug.co.uk> (raw)
In-Reply-To: <s5hirdcbsty.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Tue, 27 Feb 2007 15:52:41 +0100 (CET),
> Jaroslav Kysela wrote:
>> Hi,
>>
>> 	in 2.6 kernels, we can use ktime_get_ts() function to get 
>> monotonic time which can be used for PCM timestamps. I would propose to 
>> reuse the SNDRV_PCM_IOCTL_TSTAMP ioctl to enable using of monotonic clock.
>> The "enable" (int) argument might mean:
>>
>> 0: standard clock - getnstimeofday()
>> 1: standard clock - getnstimeofday() - for "compatibility"
>> 2: monotonic clock - ktime_get_ts()
> 
> Good to add a new feature...  but is there any user of this PCM
> timestamp so far?  I see some good purposes but rarely seen in the
> reality, unfortunately...
> 
> 
> Takashi
> 

There are some good applications for it, but I have not got round to 
writing them yet!

James




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-03-07 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 14:52 RFC: Add support for monotonic clock for 2.6 Jaroslav Kysela
2007-03-07 22:18 ` Takashi Iwai
2007-03-07 22:33   ` James Courtier-Dutton [this message]
2007-03-07 22:48     ` Takashi Iwai
2007-03-07 23:03       ` James Courtier-Dutton
2007-03-08  7:01         ` Jaroslav Kysela
2007-03-08  6:57     ` Jaroslav Kysela

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=45EF3DB5.3090008@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@suse.cz \
    --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