[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160615114908.GB31281@localhost.localdomain>
Date: Wed, 15 Jun 2016 13:49:08 +0200
From: Richard Cochran <richardcochran@...il.com>
To: Henrik Austad <henrik@...tad.us>
Cc: linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
alsa-devel@...r.kernel.org, netdev@...r.kernel.org,
henrk@...tad.us, Henrik Austad <haustad@...co.com>,
Mauro Carvalho Chehab <mchehab@....samsung.com>,
Takashi Iwai <tiwai@...e.de>, Mark Brown <broonie@...nel.org>
Subject: Re: [very-RFC 7/8] AVB ALSA - Add ALSA shim for TSN
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
Powered by blists - more mailing lists