From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: tiwai@suse.de
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: [PATCH 0/3] ALSA: bebob: enable MIDI message transmission for multiple ports
Date: Sun, 21 Mar 2021 12:28:28 +0900 [thread overview]
Message-ID: <20210321032831.340278-1-o-takashi@sakamocchi.jp> (raw)
Hi,
Although below models supported by ALSA bebob driver have multiple MIDI
ports, the driver just adds one pair of MIDI ports for ALSA Rawmidi
interface:
* M-Audio ProjectMix I/O
* ESI Quatafire 610
The cause comes from two bugs:
* The driver registers the number of MIDI conformant data channels into
AM824 data block processing layer, instead of the number of MIDI
ports.
* For Quatafire, the driver counts plugs with MIDI type, however the
number of physical MIDI ports is expressed in the number of channels
on the plugs.
This patchset enables MIDI message transmission for multiple ports.
Takashi Sakamoto (3):
ALSA: bebob: code refactoring for stream format detection
ALSA: bebob: detect the number of available MIDI ports
ALSA: bebob: enable to deliver MIDI messages for multiple ports
sound/firewire/bebob/bebob.h | 2 +
sound/firewire/bebob/bebob_command.c | 36 ++++++
sound/firewire/bebob/bebob_stream.c | 163 ++++++++++++++-------------
3 files changed, 120 insertions(+), 81 deletions(-)
--
2.27.0
next reply other threads:[~2021-03-21 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 3:28 Takashi Sakamoto [this message]
2021-03-21 3:28 ` [PATCH 1/3] ALSA: bebob: code refactoring for stream format detection Takashi Sakamoto
2021-03-21 3:28 ` [PATCH 2/3] ALSA: bebob: detect the number of available MIDI ports Takashi Sakamoto
2021-03-21 3:28 ` [PATCH 3/3] ALSA: bebob: enable to deliver MIDI messages for multiple ports Takashi Sakamoto
2021-03-22 11:23 ` [PATCH 0/3] ALSA: bebob: enable MIDI message transmission " Takashi Iwai
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=20210321032831.340278-1-o-takashi@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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.