From: Takashi Iwai <tiwai@suse.de>
To: Nicholas Hobson <nicholas.hobson@outlook.com>
Cc: "clemens@ladisch.de" <clemens@ladisch.de>,
"perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: usb-audio: keep MIDI input running for Roland TD-11
Date: Mon, 14 Sep 2026 18:26:07 +0200 [thread overview]
Message-ID: <87zexjn6jk.wl-tiwai@suse.de> (raw)
In-Reply-To: <MN2PR15MB3472557AF39DC3A4CA9E753FF8BD2@MN2PR15MB3472.namprd15.prod.outlook.com>
On Sat, 12 Sep 2026 05:28:42 +0200,
Nicholas Hobson wrote:
>
> From cbb4e446c3278aa99b34e622ac7ccef3e6d98d5b Mon Sep 17 00:00:00 2001
> From: Nicholas Hobson <nicholas.hobson@outlook.com>
> Date: Fri, 11 Sep 2026 21:58:09 -0400
> Subject: [PATCH] ALSA: usb-audio: keep MIDI input running for Roland TD-11
(Those lines look superfluous. Please avoid it at the next time.)
> The TD-11 hands MIDI handling off to the host once connected via
> USB. If no MIDI input port is opened on the host, the device itself
> becomes unusable as a standalone instrument until its input is
> serviced, independent of anything happening on the computer.
>
> Add a per-device keep_input_running flag, set for the TD-11 in
> snd_usbmidi_detect_roland(), and check it alongside the existing
> opened[1] check in snd_usbmidi_input_start()/snd_usbmidi_input_stop()
> so that input is started at device creation and never stopped for
> these devices, regardless of whether a client has the input port
> open.
>
> Signed-off-by: Nicholas Hobson <nicholas.hobson@outlook.com>
Applied to for-next branch now. Thanks.
Takashi
prev parent reply other threads:[~2026-09-14 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 3:28 Nicholas Hobson
2026-09-14 16:26 ` Takashi Iwai [this message]
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=87zexjn6jk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicholas.hobson@outlook.com \
--cc=perex@perex.cz \
--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®