All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dylan Reid <dgreid@chromium.org>, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ALSA: hda/ca0132 - Update latency based on DSP state.
Date: Fri, 05 Apr 2013 11:28:58 -0500	[thread overview]
Message-ID: <515EFBCA.9060101@linux.intel.com> (raw)
In-Reply-To: <s5h4nfl2ea5.wl%tiwai@suse.de>


> I thought that the timestamp and the runtime delay are basically
> independent parameters.  Why must the former be disabled?

In HDA you have DPIB and LPIB. The position in the buffer is reported by 
DPIB and the # of samples rendered is reported by LPIB. The delay is the 
difference between the two when you use the LPIB_DELAY implementation. 
As a result, when you look-up the timestamps and query the delay, what 
you get is the current time as seen by the HDA interface. If you 
increment the runtime delay to add the codec delay, then you must also 
increment by the same amount in azx_get_wallclock_tstamp(). Just 
updating the runtime delay is not enough.
One problem I also have with this approach is that the delay may be 
different if you have multiple streams processed with different 
algorithms, and that isn't exposed here.
-Pierre

  reply	other threads:[~2013-04-05 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 20:55 [PATCH v2] ALSA: hda/ca0132 - Update latency based on DSP state Dylan Reid
2013-04-05  5:40 ` Takashi Iwai
2013-04-05 15:01   ` Pierre-Louis Bossart
2013-04-05 15:22     ` Takashi Iwai
2013-04-05 16:28       ` Pierre-Louis Bossart [this message]
2013-04-05 17:01         ` Dylan Reid
2013-04-05 17:20           ` Pierre-Louis Bossart
2013-04-05 18:13             ` Dylan Reid
2013-04-05 21:24               ` Pierre-Louis Bossart
2013-04-05 21:44                 ` Dylan Reid

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=515EFBCA.9060101@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=dgreid@chromium.org \
    --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 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.