From: Takashi Iwai <tiwai@suse.de>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: perex@perex.cz, tiwai@suse.com, krzysztof.h1@wp.pl,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: question on sound/isa/msnd/msnd_midi.c
Date: Sun, 11 May 2025 16:13:43 +0200 [thread overview]
Message-ID: <87r00vxmjs.wl-tiwai@suse.de> (raw)
In-Reply-To: <aByXJKi2j7B4b0bH@gallifrey>
On Thu, 08 May 2025 13:36:04 +0200,
Dr. David Alan Gilbert wrote:
>
> Hi,
> I noticed that nothing calls snd_msndmidi_new in
> sound/isa/msnd/msnd_midi.c and was about to delete it, but I'm not
> too sure - I think it's actually a bug where it should be called.
>
> This code was added in 2009 by
> commit f6c638350275 ("ALSA: Turtle Beach Multisound Classic/Pinnacle driver")
> (Pretty new for an ISA card!)
>
> Looking at msnd_midi.c the only function in there that anything
> calls is snd_msndmidi_input_read() called by msnd_pinnacle.c but that
> is guarded by a check:
>
> 146 if (chip->msndmidi_mpu)
> 147 snd_msndmidi_input_read(chip->msndmidi_mpu);
>
> but I don't think anything sets that msndmidi_mpu, since the only
> thing that could is snd_msndmidi_new() which isn't called.
>
> I see that the original poster didn't test the external midi:
> https://mailman.alsa-project.org/hyperkitty/list/alsa-devel@alsa-project.org/message/CWPYLPLJQEK64UU3YFCAMVXGDY42QKF2/
> so I guess this has always been missing.
>
> I don't have the hardware to test.
>
> Thoughts?
Well, it's a very old code on an old interface, and if it's not used
(even because of a typo or an overlook), then it's basically no chance
to be used in future. Let's rip off.
thanks,
Takashi
next prev parent reply other threads:[~2025-05-11 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 11:36 question on sound/isa/msnd/msnd_midi.c Dr. David Alan Gilbert
2025-05-11 14:13 ` Takashi Iwai [this message]
2025-05-11 16:47 ` Dr. David Alan Gilbert
2025-05-11 17:31 ` Dr. David Alan Gilbert
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=87r00vxmjs.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=krzysztof.h1@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux@treblig.org \
--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