All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: Manuel Jander <manuel.jander@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/2] RFC: support for audio wall clock
Date: Fri, 20 Jul 2012 14:57:38 -0500	[thread overview]
Message-ID: <5009B832.5060802@linux.intel.com> (raw)
In-Reply-To: <CAN8cciZR73c74p6yTDn7qu4CKJUC_o7d4mwQthFmAtC9j3SzVw@mail.gmail.com>

On 6/29/2012 8:03 PM, Raymond Yau wrote:
> Do suspsend/resume affect the usage of the wall clock ? Those au88x0 
> also have a 32 bit register which return the ticks from a 12.288 Mz 
> oscillator (i.e. 256 x 48000Hz) , this register wrap around in around 
> 349.5 seconds Can this clock be used to determine the drift too ? 

In theory any clock can be used, as long as it's synchronous with the 
bitclock used in the serial stream. I am planning to use our 19.2 MHz 
clock on non HDAudio platforms, a 12.288 would work at well. The cycle 
count will be translated to ns, the initial clock base has a marginal 
impact on the result.
I haven't validated anything related to suspend/resume. It should work 
if the trigger is invoked on resume where the audio wallclock is 
reinitialized with the system time
-Pierre

  reply	other threads:[~2012-07-20 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 21:12 [PATCH 0/2] RFC: support for audio wall clock Pierre-Louis Bossart
2012-06-28 21:12 ` [PATCH 1/2] ALSA: core: add hooks for audio timestamps read from WALLCLOCK Pierre-Louis Bossart
2012-06-28 21:12 ` [PATCH 2/2] ALSA: hda: support for wallclock timestamps Pierre-Louis Bossart
2012-06-30  1:03 ` [PATCH 0/2] RFC: support for audio wall clock Raymond Yau
2012-07-20 19:57   ` Pierre-Louis Bossart [this message]
2012-07-18 17:10 ` Takashi Iwai
2012-07-20 19:47   ` Pierre-Louis Bossart
2012-07-21  6:20     ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2012-06-13 20:26 Pierre-Louis Bossart

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=5009B832.5060802@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=manuel.jander@gmail.com \
    --cc=superquad.vortex2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.