From: Takashi Iwai <tiwai@suse.de>
To: Alan Young <Alan.Young@IEE.org>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] pcm_dshare: Do not discard slave reported delay in status result.
Date: Thu, 17 Nov 2016 16:20:23 +0100 [thread overview]
Message-ID: <s5hzikyuo94.wl-tiwai@suse.de> (raw)
In-Reply-To: <f4a6b593-eef2-55c0-6b98-caa3251bfdb0@IEE.org>
On Thu, 17 Nov 2016 16:18:53 +0100,
Alan Young wrote:
>
> On 17/11/16 15:12, Takashi Iwai wrote:
> > On Thu, 17 Nov 2016 15:35:55 +0100,
> > Alan Young wrote:
> >> snd_pcm_dshare_status() gets the underlying status from the slave PCM.
> >> This may contain a delay value that includes elements such as codec and
> >> other transfer delays. Use this as the base for the returned delay
> >> value, adjusted for any frames buffered locally (within the dshare
> >> plugin).
> >>
> >> Note: snd_pcm_dshare_delay() is not updated.
> >>
> >> Signed-off-by: Alan Young <consult.awy@gmail.com>
> > Unfortunately, your MUA seems malforming the texts and does
> > line-break and replacing the tabs, so the patch is broken.
> > Please either fix your MUA setup or use an attachment as a fallback.
> Let's try an attachment.
OK, applied now.
thanks,
Takashi
prev parent reply other threads:[~2016-11-17 15:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 14:30 Accurate delay reporting from dshare Alan Young
2016-10-27 10:52 ` Takashi Iwai
2016-11-02 14:17 ` Alan Young
2016-11-02 17:34 ` Alan Young
2016-11-17 8:20 ` [PATCH] pcm_dshare: Do not discard slave reported delay in status result Alan Young
2016-11-17 10:31 ` Takashi Iwai
2016-11-17 14:18 ` Alan Young
2016-11-17 14:21 ` Takashi Iwai
2016-11-17 14:35 ` Alan Young
2016-11-17 15:12 ` Takashi Iwai
2016-11-17 15:18 ` Alan Young
2016-11-17 15:20 ` Takashi Iwai [this message]
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=s5hzikyuo94.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Alan.Young@IEE.org \
--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 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.