mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: HyeongJun An <sammiee5311@gmail.com>
To: Takashi Iwai <tiwai@suse.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Mark Brown <broonie@kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	linux-sound@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	HyeongJun An <sammiee5311@gmail.com>
Subject: [PATCH 0/2] ALSA: seq: ump: Convert MIDI 2.0 RPN and NRPN for MIDI 1.0 clients
Date: Sun, 22 Nov 2026 19:36:09 +0900	[thread overview]
Message-ID: <20261122103611.3264343-1-sammiee5311@gmail.com> (raw)

A UMP MIDI 1.0 client gets nothing when a UMP MIDI 2.0 client sends an
RPN or NRPN. Patch 1 converts them to CCs the way the core converter
does, and patch 2 adds a test.

A related question. In the other direction, CC 101, 100, 6 and 38 from
a UMP MIDI 1.0 client reach a MIDI 2.0 client as four MIDI 2.0 CC
messages. The same CCs from a legacy client are combined into one RPN
message by cc_ev_to_ump_midi2(). Should cvt_ump_midi1_to_midi2() do
that too? I can send it if you want it.

Tested in QEMU (x86_64) on sound/for-next 1afd6b7547b2. seq-ump-test
passes 28 of 29 without patch 1, where the new test gets no packets,
and 29 of 29 with it.

Prepared with Claude Code (Claude Opus 5.5).

HyeongJun An (2):
  ALSA: seq: ump: Don't drop MIDI 2.0 RPN and NRPN for MIDI 1.0 clients
  selftests/alsa: Test the sequencer UMP MIDI 2.0 RPN conversion

 sound/core/seq/seq_ump_convert.c            | 36 +++++++++++++++++++++
 tools/testing/selftests/alsa/seq-ump-test.c | 20 ++++++++++++
 2 files changed, 56 insertions(+)

-- 
2.43.0


             reply	other threads:[~2026-11-22 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-22 10:36 HyeongJun An [this message]
2026-11-22 10:36 ` [PATCH 1/2] ALSA: seq: ump: Don't drop " HyeongJun An
2026-11-22 10:36 ` [PATCH 2/2] selftests/alsa: Test the sequencer UMP MIDI 2.0 RPN conversion HyeongJun An

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=20261122103611.3264343-1-sammiee5311@gmail.com \
    --to=sammiee5311@gmail.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=shuah@kernel.org \
    --cc=tiwai@suse.com \
    /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

all inboxes | Powered by JetHome®