From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: chihhao chen <chihhao.chen@mediatek.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, wsd_upstream@mediatek.com,
damien@zamaudio.com, tiwai@suse.com,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ALSA: usb-audio: fix incorrect clock source setting
Date: Mon, 26 Jul 2021 20:57:27 +0000 [thread overview]
Message-ID: <CAEsQvctJDnsaRTXAGAJ6==juKazoo2=AJrWabLzqE=jCfg5EEA@mail.gmail.com> (raw)
In-Reply-To: <2db5d44b88ace1c25af4a45b3469a425fe1d81a5.camel@mediatek.com>
On Mon, Jul 26, 2021 at 8:42 AM chihhao chen <chihhao.chen@mediatek.com> wrote:
>
> Hello,
>
> Attach USB descriptor of clock source and selectior for this earphone.
>
> AC Clock Source Descriptor:
> ------------------------------
>
> Value Valuename
> 0x08 bLength
> 0x24 bDescriptorType
> 0x0A bDescriptorSubtype
> 0x09 bClockID
> 0x03 bmAttributes
> 0x07 bmControls
> 0x00 bAssocTerminal
> 0x00 iClockSource
> Hex dump:
> 0x08 0x24 0x0A 0x09 0x03 0x07 0x00 0x00
>
> AC Clock Selector Descriptor:
> ------------------------------
>
> Value Valuename
> 0x09 bLength
> 0x24 bDescriptorType
> 0x0B bDescriptorSubtype
> 0x0B bClockID
> 0x02 bNrInPins
> 0x09 baCSourceID(1)
> 0x0A baCSourceID(2)
> 0x03 bmControls
> 0x00 iClockSelector
> Hex dump:
> 0x09 0x24 0x0B 0x0B 0x02 0x09 0x0A 0x03 0x00
>
> AC Clock Source Descriptor:
> ------------------------------
>
> Value Valuename
> 0x08 bLength
> 0x24 bDescriptorType
> 0x0A bDescriptorSubtype
> 0x0A bClockID
> 0x03 bmAttributes
> 0x07 bmControls
> 0x00 bAssocTerminal
> 0x00 iClockSource
> Hex dump:
> 0x08 0x24 0x0A 0x0A 0x03 0x07 0x00 0x00
>
> AC Clock Selector Descriptor:
> ------------------------------
>
> Value Valuename
> 0x09 bLength
> 0x24 bDescriptorType
> 0x0B bDescriptorSubtype
> 0x0C bClockID
> 0x02 bNrInPins
> 0x09 baCSourceID(1)
> 0x0A baCSourceID(2)
> 0x03 bmControls
> 0x00 iClockSelector
> Hex dump:
> 0x09 0x24 0x0B 0x0C 0x02 0x09 0x0A 0x03 0x00
>
> Thanks
> Chihhao
Thank you, Chihhao.
So I was wrong about Samsung USBC Headset (AKG) with VID/PID
(0x04e8/0xa051) having a Clock Multiplier.
There are two Clock Sources, both linked to the USB SOF with fixed sample rate.
Plus two Clock Selectors which are host-programmable and can be set to
either of the two Clock Sources.
I'm still at a loss to explain what is going wrong here.
Would a printk() reveal the first explicit
uac_clock_selector_set_val() on the Clock Selector associated with
USB_IN sets Clock Source ID to pin 1 with Clock Source ID 0x9?
Or is it the other way around, i.e. it sets the Clock Source ID to pin
2 with Clock ID 0xA for the capture stream Clock Selector?
Chihhao Chen, could you please try the following patch for debugging
purposes and share what is printed in dmesg?
Please try one time with your fix applied and one time without, i.e.
with an otherwise unmodified vanilla kernel.
Thank you,
Geraldo Nascimento
--- clock.c.orig 2021-07-17 12:15:06.416028360 -0000
+++ clock.c 2021-07-26 20:45:58.713881962 -0000
@@ -300,6 +300,7 @@ static int __uac_clock_find_source(struc
/* the entity ID we are looking for is a selector.
* find out what it currently selects */
ret = uac_clock_selector_get_val(chip, clock_id);
+ printk(KERN_ERR "FOR EP %x: Clock Selector %x has pin %d for
Clock Source ID %x selected\n", (unsigned int)fmt->endpoint, clock_id,
ret, sources[ret - 1]);
if (ret < 0) {
if (!chip->autoclock)
return ret;
@@ -324,6 +325,7 @@ static int __uac_clock_find_source(struc
sources[ret - 1],
visited, validate);
if (ret > 0) {
+ printk(KERN_ERR "FOR EP %x: Found Source! Clock Selector
%x has pin %d for Clock Source ID %x about to be reselected\n",
(unsigned int)fmt->endpoint, entity_id, cur, sources[cur - 1]);
err = uac_clock_selector_set_val(chip, entity_id, cur);
if (err < 0)
return err;
@@ -344,6 +346,7 @@ static int __uac_clock_find_source(struc
if (ret < 0)
continue;
+ printk(KERN_ERR "FOR EP %x: Found source by trial and
error! Clock Selector %x has pin %d for Clock Source ID %x about to be
selected\n", (unsigned int)fmt->endpoint, entity_id, i, sources[i -
1]);
err = uac_clock_selector_set_val(chip, entity_id, i);
if (err < 0)
continue;
next prev parent reply other threads:[~2021-07-26 23:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 4:23 [PATCH] ALSA: usb-audio: fix incorrect clock source setting chihhao.chen
2021-07-24 8:04 ` Takashi Iwai
2021-07-24 15:04 ` Geraldo Nascimento
2021-07-24 15:20 ` Geraldo Nascimento
2021-07-24 18:42 ` Geraldo Nascimento
2021-07-25 7:44 ` Takashi Iwai
2021-07-26 2:16 ` Geraldo Nascimento
2021-07-26 8:42 ` chihhao chen
2021-07-26 20:57 ` Geraldo Nascimento [this message]
2021-07-27 10:27 ` chihhao.chen
2021-07-27 17:56 ` Geraldo Nascimento
2021-07-28 1:19 ` Geraldo Nascimento
2021-08-05 7:54 ` chihhao.chen
2021-08-05 15:50 ` Geraldo Nascimento
[not found] ` <CAEsQvcvJeAXoVE9FE9vsKNvXMaQYgHZBoPyKfZLT=UA-4BMe_Q@mail.gmail.com>
2021-08-05 22:03 ` Geraldo Nascimento
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='CAEsQvctJDnsaRTXAGAJ6==juKazoo2=AJrWabLzqE=jCfg5EEA@mail.gmail.com' \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=chihhao.chen@mediatek.com \
--cc=damien@zamaudio.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=wsd_upstream@mediatek.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;
as well as URLs for NNTP newsgroup(s).