All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Mike Brady <mikebrady@eircom.net>
Cc: eric@anholt.net, stefan.wahren@i2se.com,
	gregkh@linuxfoundation.org, f.fainelli@gmail.com, tiwai@suse.de,
	nishka.dasgupta_ug18@ashoka.edu.in, julia.lawall@lip6.fr,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: bcm2835-audio: interpolate audio delay
Date: Thu, 18 Oct 2018 21:48:36 +0200	[thread overview]
Message-ID: <22867d63-12f1-31f7-acb6-ce9a58fcbe71@gmail.com> (raw)
In-Reply-To: <20181018105715.GA6660@ubuntu>

Hello Mike,

On 10/18/18 12:57, Mike Brady wrote:
> +	ktime_t now = ktime_get();
> +
> +	/* Give userspace better delay reporting by interpolating between GPU
> +	 * notifications, assuming audio speed is close enough to the clock
> +	 * used for ktime
> +	 */
> +
> +	if ((ktime_to_ns(alsa_stream->interpolate_start)) &&
> +	    (ktime_compare(alsa_stream->interpolate_start, now) < 0)) {
> +		u64 interval =
> +			(ktime_to_ns(ktime_sub(now,
> +				alsa_stream->interpolate_start)));
> +		u64 frames_output_in_interval =
> +			div_u64((interval * runtime->rate), 1000000000);
> +		snd_pcm_sframes_t frames_output_in_interval_sized =
> +			-frames_output_in_interval;
> +		runtime->delay = frames_output_in_interval_sized;
> +	}

This doesn't look like a good solution for me. More like a workaround. What is
the root cause of the delay?

Best Regards,
Kirill

WARNING: multiple messages have this Message-ID (diff)
From: k.marinushkin@gmail.com (Kirill Marinushkin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] staging: bcm2835-audio: interpolate audio delay
Date: Thu, 18 Oct 2018 21:48:36 +0200	[thread overview]
Message-ID: <22867d63-12f1-31f7-acb6-ce9a58fcbe71@gmail.com> (raw)
In-Reply-To: <20181018105715.GA6660@ubuntu>

Hello Mike,

On 10/18/18 12:57, Mike Brady wrote:
> +	ktime_t now = ktime_get();
> +
> +	/* Give userspace better delay reporting by interpolating between GPU
> +	 * notifications, assuming audio speed is close enough to the clock
> +	 * used for ktime
> +	 */
> +
> +	if ((ktime_to_ns(alsa_stream->interpolate_start)) &&
> +	    (ktime_compare(alsa_stream->interpolate_start, now) < 0)) {
> +		u64 interval =
> +			(ktime_to_ns(ktime_sub(now,
> +				alsa_stream->interpolate_start)));
> +		u64 frames_output_in_interval =
> +			div_u64((interval * runtime->rate), 1000000000);
> +		snd_pcm_sframes_t frames_output_in_interval_sized =
> +			-frames_output_in_interval;
> +		runtime->delay = frames_output_in_interval_sized;
> +	}

This doesn't look like a good solution for me. More like a workaround. What is
the root cause of the delay?

Best Regards,
Kirill

  parent reply	other threads:[~2018-10-18 19:47 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 10:57 [PATCH] staging: bcm2835-audio: interpolate audio delay Mike Brady
2018-10-18 10:57 ` Mike Brady
2018-10-18 11:02 ` Takashi Iwai
2018-10-18 11:02   ` Takashi Iwai
2018-10-18 19:48 ` Kirill Marinushkin [this message]
2018-10-18 19:48   ` Kirill Marinushkin
2018-10-22 19:08   ` Mike Brady
2018-10-22 19:08     ` Mike Brady
2018-10-22 19:17 ` [PATCH v2] " Mike Brady
2018-10-22 19:17   ` Mike Brady
2018-10-22 19:17   ` Mike Brady
2018-10-22 22:25   ` Kirill Marinushkin
2018-10-22 22:25     ` Kirill Marinushkin
2018-10-24  8:20     ` [alsa-devel] " Mike Brady
2018-10-24  8:20       ` Mike Brady
2018-10-24  8:20       ` Mike Brady
2018-10-24 18:06       ` [alsa-devel] " Kirill Marinushkin
2018-10-24 18:06         ` Kirill Marinushkin
2018-10-24 19:54         ` Mike Brady
2018-10-24 19:54           ` Mike Brady
2018-10-24 19:54           ` Mike Brady
2018-10-24 22:02           ` [alsa-devel] " Kirill Marinushkin
2018-10-24 22:02             ` Kirill Marinushkin
2018-10-25  7:37             ` Takashi Iwai
2018-10-25  7:37               ` Takashi Iwai
2018-10-25  7:37               ` Takashi Iwai
2018-10-25 17:20               ` [alsa-devel] " Kirill Marinushkin
2018-10-25 17:20                 ` Kirill Marinushkin
2018-10-28 14:24                 ` Mike Brady
2018-10-28 14:24                   ` Mike Brady
2018-10-28 14:24                   ` Mike Brady
2018-10-28 14:26               ` [alsa-devel] " Mike Brady
2018-10-28 14:26                 ` Mike Brady
2018-10-28 14:26                 ` Mike Brady
2018-11-05 15:57                 ` [alsa-devel] " Mike Brady
2018-11-05 15:57                   ` Mike Brady
2018-11-05 15:57                   ` Mike Brady
2018-11-05 16:11                   ` [alsa-devel] " Takashi Iwai
2018-11-05 16:11                     ` Takashi Iwai
2018-11-06 21:05                     ` Mike Brady
2018-11-06 21:05                       ` Mike Brady
2018-11-06 21:31                       ` Takashi Iwai
2018-11-06 21:31                         ` Takashi Iwai
2018-11-11 18:08                         ` Mike Brady
2018-11-11 18:21                           ` [PATCH v2] ARM: " Mike Brady
2018-11-11 18:08                           ` [alsa-devel] [PATCH v2] " Mike Brady
2018-11-11 20:18                           ` [PATCH v2] ARM: " Stefan Wahren
2018-11-11 20:18                             ` Stefan Wahren
2018-11-11 20:18                             ` Stefan Wahren
2018-11-13 16:50                           ` Takashi Iwai
2018-11-13 16:50                             ` Takashi Iwai
2019-01-01 10:02                             ` Mike Brady
2019-01-01 10:02                               ` Mike Brady
2019-01-01 10:02                               ` Mike Brady

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=22867d63-12f1-31f7-acb6-ce9a58fcbe71@gmail.com \
    --to=k.marinushkin@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mikebrady@eircom.net \
    --cc=nishka.dasgupta_ug18@ashoka.edu.in \
    --cc=stefan.wahren@i2se.com \
    --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.