Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: linux-sound@vger.kernel.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH 0/8] ALSA: Small extensions for UMP
Date: Fri, 10 Jan 2025 16:59:33 +0100	[thread overview]
Message-ID: <20250110155943.31578-1-tiwai@suse.de> (raw)

Hi,

this is a series of changes for rawmidi and sequencer APIs for
handling the missing piece for UMP v1.1.

UMP v1.1 allows the device updating the Endpoint and the Function
Block information dynamically.  The current driver already handles it,
but a few things are still missing:
* The update of rawmidi name
* Notification of EP and FB update via sequencer
The patches cover those missing info.

Also, the current implementation doesn't give a clear idea which UMP
rawmidi device is tied with the legacy rawmidi.  The rawmidi info is
extended to indicated the tied device number.

Last but not least, the UMP EP and FB info strings are copied as-is,
which isn't good for the id strings.  The copy operation is changed to
be a safer form.


Takashi

===

Takashi Iwai (8):
  ALSA: rawmidi: Expose the tied device number in info ioctl
  ALSA: rawmidi: Show substream activity in info ioctl
  ALSA: rawmidi: Bump protocol version to 2.0.5
  ALSA: ump: Copy FB name string more safely
  ALSA: ump: Copy safe string name to rawmidi
  ALSA: ump: Update rawmidi name per EP name update
  ALSA: seq: Allow system notification in atomic
  ALSA: seq: Notify UMP EP and FB changes

 Documentation/sound/designs/midi-2.0.rst |  18 ++++
 include/sound/rawmidi.h                  |   2 +
 include/sound/ump.h                      |   1 +
 include/uapi/sound/asequencer.h          |  12 ++-
 include/uapi/sound/asound.h              |   8 +-
 sound/core/rawmidi.c                     |   4 +
 sound/core/seq/seq_clientmgr.c           |  12 ++-
 sound/core/seq/seq_system.c              |   9 +-
 sound/core/seq/seq_system.h              |  31 +++++--
 sound/core/seq/seq_ump_client.c          |  40 +++++++-
 sound/core/ump.c                         | 113 ++++++++++++++++++-----
 11 files changed, 211 insertions(+), 39 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-01-10 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 15:59 Takashi Iwai [this message]
2025-01-10 15:59 ` [PATCH 1/8] ALSA: rawmidi: Expose the tied device number in info ioctl Takashi Iwai
2025-01-14 10:25   ` Jaroslav Kysela
2025-01-14 10:37     ` Takashi Iwai
2025-01-10 15:59 ` [PATCH 2/8] ALSA: rawmidi: Show substream activity " Takashi Iwai
2025-01-10 15:59 ` [PATCH 3/8] ALSA: rawmidi: Bump protocol version to 2.0.5 Takashi Iwai
2025-01-10 15:59 ` [PATCH 4/8] ALSA: ump: Copy FB name string more safely Takashi Iwai
2025-01-10 15:59 ` [PATCH 5/8] ALSA: ump: Copy safe string name to rawmidi Takashi Iwai
2025-01-10 15:59 ` [PATCH 6/8] ALSA: ump: Update rawmidi name per EP name update Takashi Iwai
2025-01-10 15:59 ` [PATCH 7/8] ALSA: seq: Allow system notification in atomic Takashi Iwai
2025-01-10 15:59 ` [PATCH 8/8] ALSA: seq: Notify UMP EP and FB changes 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=20250110155943.31578-1-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.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