From: Mike Oliphant <oliphant@nostatic.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support for NUX MG-300 USB interface
Date: Thu, 21 Jan 2021 11:04:07 -0800 [thread overview]
Message-ID: <CAHXb3beukZJ=r6dDS3fxd8MBtkFqt=qEFwHwRPhVgAJZXTzMrA@mail.gmail.com> (raw)
In-Reply-To: <CAHXb3be5Va8_K9YmObjTg+KGH3HZO9y_L4YrXvprbMY5J4fpsw@mail.gmail.com>
As a last ditch effort before returning the device, I tried the clock patch
on a Raspberry Pi 4 running an older kernel, and... it works.
The kernel version is "Linux raspberrypi 4.19.89-v7l+" and is from late
February 2020.
Maybe a change between then and now broke something? I know there have been
a *lot* of changes since then, though...
Mike
On Wed, Jan 20, 2021 at 1:47 PM Mike Oliphant <oliphant@nostatic.org> wrote:
> Yeah, I tried every possible permutation of mute/volumes on the mixer
> controls.
>
> Thanks for submitting the patches. Maybe someone else will have better
> luck down the road.
>
> Mike
>
> On Wed, Jan 20, 2021 at 1:38 PM Takashi Iwai <tiwai@suse.de> wrote:
>
>> On Wed, 20 Jan 2021 22:17:35 +0100,
>> Mike Oliphant wrote:
>> >
>> > I spent a fair bit of time debugging the code setting/getting mixer
>> control
>> > values, and I can't see anything that seems to be operating incorrectly.
>>
>> So, even if you unmute and raise both mixers, it didn't help, right?
>> I took a look at the lsusb output, but I couldn't find anything else
>> suspicious.
>>
>> > Unless you have any other suggestions, I'm going to admit defeat and
>> return
>> > the audio interface.
>> >
>> > It is probably worth committing the clock selector patch - it at least
>> made
>> > capture work, and it may help with other audio interfaces.
>>
>> OK, I'll submit two fix patches.
>>
>>
>> thanks,
>>
>> Takashi
>>
>
next prev parent reply other threads:[~2021-01-21 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 18:56 Support for NUX MG-300 USB interface Mike Oliphant
2021-01-18 7:43 ` Takashi Iwai
2021-01-18 16:33 ` Mike Oliphant
2021-01-18 17:54 ` Mike Oliphant
2021-01-18 19:19 ` Takashi Iwai
2021-01-18 21:15 ` Mike Oliphant
2021-01-18 21:59 ` Takashi Iwai
2021-01-19 0:26 ` Mike Oliphant
2021-01-19 9:05 ` Takashi Iwai
2021-01-19 17:40 ` Mike Oliphant
2021-01-20 14:33 ` Takashi Iwai
2021-01-20 21:17 ` Mike Oliphant
2021-01-20 21:38 ` Takashi Iwai
2021-01-20 21:47 ` Mike Oliphant
2021-01-21 19:04 ` Mike Oliphant [this message]
2021-01-21 20:18 ` Mike Oliphant
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='CAHXb3beukZJ=r6dDS3fxd8MBtkFqt=qEFwHwRPhVgAJZXTzMrA@mail.gmail.com' \
--to=oliphant@nostatic.org \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).