Merged for Linux 6.5 used to be preliminary MIDI 2.0 aid for the vital USB audio and uncooked MIDI drivers to aid this main MIDI replace. Being labored on now for merging right into a hour kernel let fall is the USB system driving force aid round MIDI 2.0.
Takashi Iwai of SUSE who maintains the Linux kernel’s tone subsystem and labored at the latest MIDI 2.0 enablement patches may be the only running in this USB system driving force aid. Inside tone.git he’s printed subject/midi20-gadget the place he’s queuing his paintings across the MIDI 2.0 USB system driving force aid. In the ones patches he explains:
This region provides the aid for USB MIDI 2.0 system serve as driving force. The driving force emulates a USB MIDI 2.0 interface with a number of UMP Endpoints, the place every of UMP Endpoint is a couple of MIDI Endpoints for dealing with MIDI 2.0 UMP packets. When the serve as driving force is certain, the driving force creates an ALSA card object with UMP rawmidi gadgets. This can be a more or less loop-back the place the incoming and then UMP packets from/to the MIDI 2.0 UMP Endpoints are transferred as-is. As well as, legacy (MIDI 1.0) rawmidi gadgets are created, in order that legacy programs can paintings within the system aspect, too.
When a USB MIDI 2.0 system interface seems, the hooked up host can worth it with the snd-usb-audio driving force the place MIDI 2.0 aid is enabled. Each system and hooked up hosts can have the alike UMP Endpoint and Serve as Forbid (or Crew Terminal Forbid) knowledge. Tiny variations are the course and UI-hint bits; it’s because of the character of system driving force, and the enter/output course is swapped in all sides (the enter for system is the output for host, and vice versa).
The driving force helps the brand-new UMP v1.1 trait, together with the UMP Flow message dealing with for offering UMP Endpoint and Serve as Forbid knowledge in addition to coping with the MIDI protocol transfer. The driving force responds to UMP Flow messages on its own. OTOH, MIDI-CI message dealing with isn’t carried out within the kernel driving force; it will have to be processed within the user-space in the course of the loopback UMP instrument.
Or put extra just by the up-to-date Kconfig textual content for this MIDI 2.0 system aid:
The MIDI 2.0 serve as driving force supplies the generic emulated USB MIDI 2.0 interface, looped again to ALSA UMP rawmidi instrument at the system host. It helps UMP 1.1 spec and responds UMP Flow messages for UMP Endpoint and Serve as Forbid knowledge / configuration.
We’ll see how this evolves and if the paintings manages to get into atmosphere for merging as a part of the USB adjustments come the week of the Linux v6.6 merge window.