From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: alsa-devel@alsa-project.org, netdev@vger.kernel.org,
Henrik Austad <henrik@austad.us>,
linux-kernel@vger.kernel.org,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Arnd Bergmann <arnd@linaro.org>,
linux-media@vger.kernel.org
Subject: Re: [alsa-devel] [very-RFC 0/8] TSN driver for the kernel
Date: Wed, 22 Jun 2016 05:36:42 -0700 [thread overview]
Message-ID: <04675515-ff64-0acc-f0f0-7714e20c1485@linux.intel.com> (raw)
In-Reply-To: <20160621194001.GB2489@netboy>
On 6/21/16 12:40 PM, Richard Cochran wrote:
> On Tue, Jun 21, 2016 at 10:45:18AM -0700, Pierre-Louis Bossart wrote:
>> You can experiment with the 'dma' and 'link' timestamps today on any
>> HDaudio-based device. Like I said the synchronized part has not been
>> upstreamed yet (delays + dependency on ART-to-TSC conversions that made it
>> in the kernel recently)
>
> Can you point me to any open source apps using the dma/link
> timestamps?
Those timestamps are only used in custom applications at the moment, not
'mainstream' open source.
It takes time for new kernel capabilities to trickle into userspace,
applications usually align on the lowest hardware common denominator. In
addition, most applications don't access the kernel directly but go
through an audio server or HAL which needs to be updated as well so it's
a two-level dependency. These timestamps can be directly mappped to the
Android AudioTrack.getTimeStamp API though.
next prev parent reply other threads:[~2016-06-22 12:37 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 23:01 [very-RFC 0/8] TSN driver for the kernel Henrik Austad
2016-06-11 23:01 ` [very-RFC 1/8] TSN: add documentation Henrik Austad
2016-06-11 23:01 ` [very-RFC 2/8] TSN: Add the standard formerly known as AVB to the kernel Henrik Austad
2016-06-11 23:01 ` [very-RFC 3/8] Adding TSN-driver to Intel I210 controller Henrik Austad
2016-06-11 23:01 ` [very-RFC 4/8] Add TSN header for the driver Henrik Austad
2016-06-11 23:01 ` [very-RFC 5/8] Add TSN machinery to drive the traffic from a shim over the network Henrik Austad
2016-06-11 23:01 ` [very-RFC 6/8] Add TSN event-tracing Henrik Austad
2016-06-12 16:58 ` Steven Rostedt
2016-06-12 21:25 ` Henrik Austad
2016-06-13 2:22 ` Steven Rostedt
2016-06-13 7:20 ` Henrik Austad
2016-06-11 23:01 ` [very-RFC 7/8] AVB ALSA - Add ALSA shim for TSN Henrik Austad
2016-06-15 11:49 ` Richard Cochran
2016-06-15 12:13 ` Henrik Austad
2016-06-15 12:43 ` Richard Cochran
2016-06-11 23:01 ` [very-RFC 8/8] MAINTAINERS: add TSN/AVB-entries Henrik Austad
2016-06-13 11:47 ` [very-RFC 0/8] TSN driver for the kernel Richard Cochran
2016-06-13 13:00 ` Henrik Austad
2016-06-13 19:32 ` Richard Cochran
2016-06-14 9:30 ` Henrik Austad
2016-06-14 18:26 ` Richard Cochran
2016-06-14 20:38 ` Henrik Austad
2016-06-15 7:04 ` Richard Cochran
2016-06-15 7:50 ` Henrik Austad
2016-06-15 11:41 ` Richard Cochran
2016-06-15 7:11 ` Richard Cochran
2016-06-13 19:37 ` Richard Cochran
2016-06-13 13:12 ` Arnd Bergmann
2016-06-13 15:56 ` John Fastabend
2016-06-14 8:35 ` Henrik Austad
2016-06-13 19:51 ` Richard Cochran
2016-06-14 11:18 ` One Thousand Gnomes
2016-06-14 17:04 ` Richard Cochran
2016-06-15 3:15 ` Takashi Sakamoto
2016-06-15 8:06 ` Richard Cochran
2016-06-18 5:22 ` Takashi Sakamoto
2016-06-18 22:45 ` Henrik Austad
2016-06-19 9:46 ` Richard Cochran
2016-06-20 8:05 ` Henrik Austad
2016-06-20 11:08 ` [alsa-devel] " Pierre-Louis Bossart
2016-06-20 11:49 ` Henrik Austad
2016-06-20 12:18 ` Richard Cochran
2016-06-20 12:31 ` Richard Cochran
2016-06-20 15:21 ` Richard Cochran
2016-06-21 5:54 ` Takashi Iwai
2016-06-21 6:38 ` Richard Cochran
2016-06-21 6:45 ` Takashi Iwai
2016-06-21 17:18 ` Pierre-Louis Bossart
2016-06-21 17:45 ` Pierre-Louis Bossart
2016-06-21 19:40 ` Richard Cochran
2016-06-22 12:36 ` Pierre-Louis Bossart [this message]
2016-06-23 10:38 ` Henrik Austad
2016-06-23 13:28 ` Richard Cochran
2016-06-15 3:27 ` Takashi Sakamoto
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=04675515-ff64-0acc-f0f0-7714e20c1485@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@linaro.org \
--cc=henrik@austad.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=richardcochran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).