From: Richard Cochran <richardcochran@gmail.com>
To: Henrik Austad <henrik@austad.us>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
alsa-devel@vger.kernel.org, netdev@vger.kernel.org,
henrk@austad.us, Henrik Austad <haustad@cisco.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>
Subject: Re: [very-RFC 7/8] AVB ALSA - Add ALSA shim for TSN
Date: Wed, 15 Jun 2016 13:49:08 +0200 [thread overview]
Message-ID: <20160615114908.GB31281@localhost.localdomain> (raw)
In-Reply-To: <1465686096-22156-8-git-send-email-henrik@austad.us>
Now that I understand better...
On Sun, Jun 12, 2016 at 01:01:35AM +0200, Henrik Austad wrote:
> Userspace is supposed to reserve bandwidth, find StreamID etc.
>
> To use as a Talker:
>
> mkdir /config/tsn/test/eth0/talker
> cd /config/tsn/test/eth0/talker
> echo 65535 > buffer_size
> echo 08:00:27:08:9f:c3 > remote_mac
> echo 42 > stream_id
> echo alsa > enabled
This is exactly why configfs is the wrong interface. If you implement
the AVB device in alsa-lib user space, then you can handle the
reservations, configuration, UDP sockets, etc, in a way transparent to
the aplay program.
Heck, if done properly, your layer could discover the AVB nodes in the
network and present each one as a separate device...
Thanks,
Richard
next prev parent reply other threads:[~2016-06-15 11:49 UTC|newest]
Thread overview: 55+ 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 [this message]
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
2016-06-23 10:38 ` Henrik Austad
2016-06-23 13:28 ` Richard Cochran
2016-06-15 3:27 ` Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2016-06-11 22:22 Henrik Austad
2016-06-11 22:22 ` [very-RFC 7/8] AVB ALSA - Add ALSA shim for TSN Henrik Austad
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=20160615114908.GB31281@localhost.localdomain \
--to=richardcochran@gmail.com \
--cc=alsa-devel@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=haustad@cisco.com \
--cc=henrik@austad.us \
--cc=henrk@austad.us \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=netdev@vger.kernel.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 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).