From: Takashi Iwai <tiwai@suse.de>
To: Peter Allen <peter.allenm@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Nux Mighty Plug USB - no clock source
Date: Tue, 02 Feb 2021 21:33:53 +0100 [thread overview]
Message-ID: <s5ha6smciq6.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHa6N62V2PiZZFNpxELwPgJrxoDOa-6Byw6Oj8xwBrmFRjDzuw@mail.gmail.com>
On Tue, 02 Feb 2021 19:52:57 +0100,
Peter Allen wrote:
>
> Thank you for taking the time to look at this.
> I've tried your latest 5.12 branch, and sure enough it works perfectly without
> any problems.
> So I'm really happy. Thank you!
Good to hear!
Takashi
>
> Pete
>
> On Mon, 1 Feb 2021, 14:24 Takashi Iwai, <tiwai@suse.de> wrote:
>
> On Sat, 30 Jan 2021 09:30:50 +0100,
> Peter Allen wrote:
> >
> > I have a NUX Mighty Plug guitar effects which has a USB Audio interface.
> > Unfortunately it doesn't work in Linux, and I'd love to fix it.
> > It gets registered with Alsa, except it ends up without any valid sample
> > rates (by the look of it due to a buggy clock source descriptor).
> >
> > This is on Ubuntu-Studio 20.04 LTS _Focal Fossa with kernel
> > 5.4.0-62-lowlatency
> > on a HP Omen 15 with i5-7300HQ
> >
> > I don't know what I'm doing (but did a little module development rather
> a
> > long time ago in the 2.2 days :-)) Help is greatly appreciated.
> >
> > When plugged in I get:
> > [12476.413792] usb 1-1: New USB device found, idVendor=1fc9,
> > idProduct=8260, bcdDevice= 1.00
> > [12476.413797] usb 1-1: New USB device strings: Mfr=1, Product=2,
> > SerialNumber=3
> > [12476.413800] usb 1-1: Product: MIGHTY PLUG USB
> > [12476.413804] usb 1-1: Manufacturer: NUX
> > [12476.413807] usb 1-1: SerialNumber: 2007151403
> > [12476.444988] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.444992] usb 1-1: parse_audio_format_rates_v2v3(): unable to find
> > clock source (clock -22)
> > [12476.445413] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.445479] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.447095] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.447098] usb 1-1: parse_audio_format_rates_v2v3(): unable to find
> > clock source (clock -22)
> > [12476.447459] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.447684] usb 1-1: __uac_clock_find_source(): selector reported
> > illegal value, id 40, ret 0
> > [12476.450397] usbcore: registered new interface driver snd-usb-audio
>
> This might be covered by the recent fixes for 5.12 kernel, found in
> for-next branch of my sound git tree.
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
>
> Also, as both playback and capture streams are ASYNC, those might be
> supposed to be running in the implicit feedback. With the very latest
> kernel, this can be enabled via implicit_fb=1 module option. If this
> works better, we can set up a static quirk table entry for the device,
> too.
>
> Takashi
>
>
prev parent reply other threads:[~2021-02-02 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 8:30 Nux Mighty Plug USB - no clock source Peter Allen
2021-02-01 14:24 ` Takashi Iwai
2021-02-02 18:52 ` Peter Allen
2021-02-02 20:33 ` 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=s5ha6smciq6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=peter.allenm@gmail.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