All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jonathan Woithe <jwoithe@just42.net>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, clemens@ladisch.de,
	ffado-devel@lists.sf.net,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality
Date: Wed, 14 Oct 2015 00:20:51 +0200	[thread overview]
Message-ID: <20151014002051.4fa8b0fa@kant> (raw)
In-Reply-To: <20151013100228.GA16452@marvin.atrad.com.au>

On Oct 13 Jonathan Woithe wrote:
> for cases like MOTU, where mixer control setting updates
> are pushed to the computer by the device in response to front panel actions,
> there will be a need for userspace to somehow tap into this flow.  Userspace
> could not gain access to the iso stream because the kernel will have control
> over that.  Or can userspace tap into iso streams that have been initiated
> by the kernel (that is surprising to me if it's true).

Indeed we do not have support for multiple local listeners on the same
stream.  (firewire-core supports multiple listeners for FCP reception, but
this is a simpler case in several respects.)

I guess getting MOTU status out to userspace could work by having the
audio driver extract the data from the stream and push it as a new type of
event of the <sound/firewire.h> API through the ALSA hwdep interface.

(Apologies for going somewhat offtopic.)
-- 
Stefan Richter
-=====-===== =-=- -==-=
http://arcgraph.de/sr/

  reply	other threads:[~2015-10-13 22:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 10:10 [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 1/5] ALSA: firewire-tascam: add support for incoming MIDI messages by asynchronous transaction Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 2/5] ALSA: firewire-tascam: add support for outgoing " Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 3/5] ALSA: firewire-tascam: add support for MIDI functionality Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 4/5] ALSA: firewire-tascam: Turn on/off FireWire LED Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 5/5] ALSA: firewire-tascam: change device probing processing Takashi Sakamoto
2015-10-12 12:42   ` Stefan Richter
2015-10-13 14:12     ` Takashi Sakamoto
2015-10-12 12:21 ` [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality Takashi Iwai
2015-10-12 12:48 ` Stefan Richter
2015-10-12 22:20   ` Jonathan Woithe
2015-10-13  9:36     ` Takashi Sakamoto
2015-10-13 10:02       ` Jonathan Woithe
2015-10-13 22:20         ` Stefan Richter [this message]
2015-10-19 14:21         ` Takashi Sakamoto
2015-10-19 23:45           ` Jonathan Woithe
2015-10-13 14:15       ` Stefan Richter
2015-10-19 14:13         ` Takashi Sakamoto
2015-10-19 23:36           ` Jonathan Woithe
2015-10-20  0:50             ` Takashi Sakamoto
2015-10-20  2:09               ` Takashi Sakamoto
2015-10-20  2:57                 ` Jonathan Woithe
2015-10-20  2:52               ` Jonathan Woithe
2015-10-20  7:39               ` Stefan Richter
2015-10-26 15:18                 ` Takashi Sakamoto
2015-10-27  1:38                   ` Stefan Richter

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=20151014002051.4fa8b0fa@kant \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=ffado-devel@lists.sf.net \
    --cc=jwoithe@just42.net \
    --cc=o-takashi@sakamocchi.jp \
    --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.