Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: damien@zamaudio.com, robin@gareus.org, clemens@ladisch.de,
	alsa-devel@alsa-project.org, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/6 v3] ALSA: firewire-digi00x: support MIDI functionality
Date: Sun, 11 Oct 2015 18:27:44 +0200	[thread overview]
Message-ID: <s5hsi5hid4v.wl-tiwai@suse.de> (raw)
In-Reply-To: <1444534219-31718-1-git-send-email-o-takashi@sakamocchi.jp>

On Sun, 11 Oct 2015 05:30:13 +0200,
Takashi Sakamoto wrote:
> 
> Hi,
> 
> This commit updates my former post (patch 13, 15, 16):
> 
> [alsa-devel] [PATCH 00/25 v2] ALSA: support AMDTP variants
> http://mailman.alsa-project.org/pipermail/alsa-devel/2015-August/096739.html
> 
> Digi 00x driver may be newly available in Linux 4.4. This patchset adds
> ALSA MIDI ports to support physical MIDI ports and physical controls. I
> tested physical MIDI ports, while never tested physical controls because
> I'm not an owner of 'console' models.
> 
> The functionality for physical controls is written according to my
> assumption. When I investigated Digi 002 rack, Windows driver registers
> a certain address to the device, and adds virtual MIDI ports to the
> system. These ports are named as 'control'. When MIDI application sends
> MIDI messages to the port, asynchronous transactions start on IEEE 1394
> bus. On the other hand, I have no way to confirm asynchronous transaction
> in opposite direction because the rack model doesn't have the
> functionality. In this time, I apply the same format of outgoing
> asynchronous transaction to incoming asynchronous transaction.
> 
> Takashi Sakamoto (6):
>   firewire-digi00x: use in-kernel representation for the type of 8 bits
>   firewire-digi00x: handle MIDI messages in isochronous packets
>   firewire-digi00x: add support for MIDI ports corresponding to
>     isochronous packet streaming
>   firewire-digi00x: add support of asynchronous transaction for incoming
>     MIDI messages from physical controls
>   firewire-digi00x: add support of asynchronous transaction for outgoing
>     MIDI messages to physical controls
>   firewire-digi00x: add support for MIDI ports for physical controls

Thanks, applied all six patches now.


Takashi

> 
>  sound/firewire/digi00x/Makefile              |   2 +-
>  sound/firewire/digi00x/amdtp-dot.c           | 150 +++++++++++++++++++++----
>  sound/firewire/digi00x/digi00x-midi.c        | 160 +++++++++++++++++++++++++++
>  sound/firewire/digi00x/digi00x-stream.c      |   6 +-
>  sound/firewire/digi00x/digi00x-transaction.c |  70 ++++++++++--
>  sound/firewire/digi00x/digi00x.c             |   4 +
>  sound/firewire/digi00x/digi00x.h             |  15 ++-
>  7 files changed, 376 insertions(+), 31 deletions(-)
>  create mode 100644 sound/firewire/digi00x/digi00x-midi.c
> 
> -- 
> 2.1.4
> 

  parent reply	other threads:[~2015-10-11 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-11  3:30 [PATCH 0/6 v3] ALSA: firewire-digi00x: support MIDI functionality Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 1/6] firewire-digi00x: use in-kernel representation for the type of 8 bits Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 2/6] firewire-digi00x: handle MIDI messages in isochronous packets Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 3/6] firewire-digi00x: add support for MIDI ports corresponding to isochronous packet streaming Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 4/6] firewire-digi00x: add support of asynchronous transaction for incoming MIDI messages from physical controls Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 5/6] firewire-digi00x: add support of asynchronous transaction for outgoing MIDI messages to " Takashi Sakamoto
2015-10-11  3:30 ` [PATCH 6/6] firewire-digi00x: add support for MIDI ports for " Takashi Sakamoto
2015-10-11 16:27 ` Takashi Iwai [this message]
2015-10-11 23:26   ` [PATCH 0/6 v3] ALSA: firewire-digi00x: support MIDI functionality 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=s5hsi5hid4v.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=damien@zamaudio.com \
    --cc=ffado-devel@lists.sf.net \
    --cc=o-takashi@sakamocchi.jp \
    --cc=robin@gareus.org \
    /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