From: Takashi Iwai <tiwai@suse.de>
To: Justin Bacle <justin.bacle@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: usb-audio: add sample-rate quirk for Yamaha 01V96i
Date: Mon, 05 Oct 2026 12:29:05 +0200 [thread overview]
Message-ID: <87qzi4saoe.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261004192102.59312-1-justin.bacle@gmail.com>
On Sun, 04 Oct 2026 21:20:50 +0200,
Justin Bacle wrote:
>
> The Yamaha 01V96i exposes its audio streaming interfaces as
> vendor-specific USB class 0xff and ships no class-specific endpoint
> descriptor. parse_uac_endpoint_attributes() therefore returns no
> attributes for the device, and without UAC_EP_CS_ATTR_SAMPLE_RATE the
> driver never issues the SET_CUR sampling-frequency request the hardware
> needs to start its USB audio stream. The playback and capture PCMs are
> reported as RUNNING and their pointers advance, but the mixer passes no
> audio in either direction.
>
> The vendor (Yamaha Steinberg) driver on Windows sends this request at
> startup; the generic driver does not. Add the 01V96i to
> snd_usb_audioformat_attributes_quirk() to force the attribute on, so the
> stream is initialised the same way.
>
> Confirmed against a usbmon capture of the Windows vendor driver: SET_CUR
> CS_SAMPLING_FREQ_CONTROL to endpoints 0x07 and 0x86 is the only
> non-standard control transfer it issues that completes successfully.
>
> Verified on a mainline 7.2.9 kernel with a loopback test: playing a
> 440 Hz tone on USB channels 1/2 and recording USB channels 9/10 returns
> the tone unchanged at 44100, 48000, 88200 and 96000 Hz.
>
> Tested-by: Justin Bacle <justin.bacle@gmail.com>
> Signed-off-by: Justin Bacle <justin.bacle@gmail.com>
Applied to for-next branch now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-05 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 19:20 Justin Bacle
2026-10-05 10:29 ` 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=87qzi4saoe.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=justin.bacle@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.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
all inboxes | Powered by JetHome®