All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: chihhao chen <chihhao.chen@mediatek.com>
Cc: alsa-devel@alsa-project.org, damien@zamaudio.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	matthias.bgg@gmail.com, tiwai@suse.com,
	Takashi Iwai <tiwai@suse.de>,
	wsd_upstream@mediatek.com
Subject: Re: [PATCH] ALSA: usb-audio: fix incorrect clock source setting
Date: Thu, 5 Aug 2021 15:50:58 +0000	[thread overview]
Message-ID: <CAEsQvcsvbJdgvAOxkv_kbLohGi676Zrgz4XSFW2o3CWU3Q68Dg@mail.gmail.com> (raw)
In-Reply-To: <20210805075401.21170-1-chihhao.chen@mediatek.com>

On Thu, Aug 5, 2021 at 7:54 AM <chihhao.chen@mediatek.com> wrote:
>
> From: chihhao chen <chihhao.chen@mediatek.com>
>
> Hi Geraldo Nascimento,

Hi Chihhao Chen!

>
> For echo test, it means we use this earphone to receive and play sounds at the same time.
> We found in this case serious noise problem happens.
>

That's what I understood initially, and only a little later I became
afraid echo test was the name of the debugging technique you used :)

Thanks for the clarification.

> Log as follows with your patch
> <6>[  175.960387][T401365] __uac_clock_find_source: Clock Selector 0xc has pin 2 selected
> <6>[  175.966980][T401365] __uac_clock_find_source: Clock Selector 0xb has pin 2 selected
> <6>[  176.026251][T400354] __uac_clock_find_source: Clock Selector 0xc has pin 1 selected
> <6>[  176.032406][T400354] __uac_clock_find_source: Clock Selector 0xb has pin 1 selected
>
> There is no noise and I think this should be a firmware bug.

From the log I'm afraid my worst assumptions were right.

Regardless of which Clock Selector we want to set, the firmware will
always set them both.

We should contact Samsung now that we have at least a sketch of a bug report...

Thanks,
Geraldo Nascimento

>
> Thanks
> Chihhao
>

WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: chihhao chen <chihhao.chen@mediatek.com>
Cc: alsa-devel@alsa-project.org, wsd_upstream@mediatek.com,
	Takashi Iwai <tiwai@suse.de>,
	damien@zamaudio.com, linux-kernel@vger.kernel.org,
	tiwai@suse.com, 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: Thu, 5 Aug 2021 15:50:58 +0000	[thread overview]
Message-ID: <CAEsQvcsvbJdgvAOxkv_kbLohGi676Zrgz4XSFW2o3CWU3Q68Dg@mail.gmail.com> (raw)
In-Reply-To: <20210805075401.21170-1-chihhao.chen@mediatek.com>

On Thu, Aug 5, 2021 at 7:54 AM <chihhao.chen@mediatek.com> wrote:
>
> From: chihhao chen <chihhao.chen@mediatek.com>
>
> Hi Geraldo Nascimento,

Hi Chihhao Chen!

>
> For echo test, it means we use this earphone to receive and play sounds at the same time.
> We found in this case serious noise problem happens.
>

That's what I understood initially, and only a little later I became
afraid echo test was the name of the debugging technique you used :)

Thanks for the clarification.

> Log as follows with your patch
> <6>[  175.960387][T401365] __uac_clock_find_source: Clock Selector 0xc has pin 2 selected
> <6>[  175.966980][T401365] __uac_clock_find_source: Clock Selector 0xb has pin 2 selected
> <6>[  176.026251][T400354] __uac_clock_find_source: Clock Selector 0xc has pin 1 selected
> <6>[  176.032406][T400354] __uac_clock_find_source: Clock Selector 0xb has pin 1 selected
>
> There is no noise and I think this should be a firmware bug.

From the log I'm afraid my worst assumptions were right.

Regardless of which Clock Selector we want to set, the firmware will
always set them both.

We should contact Samsung now that we have at least a sketch of a bug report...

Thanks,
Geraldo Nascimento

>
> Thanks
> Chihhao
>

WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: chihhao chen <chihhao.chen@mediatek.com>
Cc: alsa-devel@alsa-project.org, damien@zamaudio.com,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
	tiwai@suse.com,  Takashi Iwai <tiwai@suse.de>,
	wsd_upstream@mediatek.com
Subject: Re: [PATCH] ALSA: usb-audio: fix incorrect clock source setting
Date: Thu, 5 Aug 2021 15:50:58 +0000	[thread overview]
Message-ID: <CAEsQvcsvbJdgvAOxkv_kbLohGi676Zrgz4XSFW2o3CWU3Q68Dg@mail.gmail.com> (raw)
In-Reply-To: <20210805075401.21170-1-chihhao.chen@mediatek.com>

On Thu, Aug 5, 2021 at 7:54 AM <chihhao.chen@mediatek.com> wrote:
>
> From: chihhao chen <chihhao.chen@mediatek.com>
>
> Hi Geraldo Nascimento,

Hi Chihhao Chen!

>
> For echo test, it means we use this earphone to receive and play sounds at the same time.
> We found in this case serious noise problem happens.
>

That's what I understood initially, and only a little later I became
afraid echo test was the name of the debugging technique you used :)

Thanks for the clarification.

> Log as follows with your patch
> <6>[  175.960387][T401365] __uac_clock_find_source: Clock Selector 0xc has pin 2 selected
> <6>[  175.966980][T401365] __uac_clock_find_source: Clock Selector 0xb has pin 2 selected
> <6>[  176.026251][T400354] __uac_clock_find_source: Clock Selector 0xc has pin 1 selected
> <6>[  176.032406][T400354] __uac_clock_find_source: Clock Selector 0xb has pin 1 selected
>
> There is no noise and I think this should be a firmware bug.

From the log I'm afraid my worst assumptions were right.

Regardless of which Clock Selector we want to set, the firmware will
always set them both.

We should contact Samsung now that we have at least a sketch of a bug report...

Thanks,
Geraldo Nascimento

>
> Thanks
> Chihhao
>

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: chihhao chen <chihhao.chen@mediatek.com>
Cc: alsa-devel@alsa-project.org, damien@zamaudio.com,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	 linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
	tiwai@suse.com,  Takashi Iwai <tiwai@suse.de>,
	wsd_upstream@mediatek.com
Subject: Re: [PATCH] ALSA: usb-audio: fix incorrect clock source setting
Date: Thu, 5 Aug 2021 15:50:58 +0000	[thread overview]
Message-ID: <CAEsQvcsvbJdgvAOxkv_kbLohGi676Zrgz4XSFW2o3CWU3Q68Dg@mail.gmail.com> (raw)
In-Reply-To: <20210805075401.21170-1-chihhao.chen@mediatek.com>

On Thu, Aug 5, 2021 at 7:54 AM <chihhao.chen@mediatek.com> wrote:
>
> From: chihhao chen <chihhao.chen@mediatek.com>
>
> Hi Geraldo Nascimento,

Hi Chihhao Chen!

>
> For echo test, it means we use this earphone to receive and play sounds at the same time.
> We found in this case serious noise problem happens.
>

That's what I understood initially, and only a little later I became
afraid echo test was the name of the debugging technique you used :)

Thanks for the clarification.

> Log as follows with your patch
> <6>[  175.960387][T401365] __uac_clock_find_source: Clock Selector 0xc has pin 2 selected
> <6>[  175.966980][T401365] __uac_clock_find_source: Clock Selector 0xb has pin 2 selected
> <6>[  176.026251][T400354] __uac_clock_find_source: Clock Selector 0xc has pin 1 selected
> <6>[  176.032406][T400354] __uac_clock_find_source: Clock Selector 0xb has pin 1 selected
>
> There is no noise and I think this should be a firmware bug.

From the log I'm afraid my worst assumptions were right.

Regardless of which Clock Selector we want to set, the firmware will
always set them both.

We should contact Samsung now that we have at least a sketch of a bug report...

Thanks,
Geraldo Nascimento

>
> Thanks
> Chihhao
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-08-05 18:51 UTC|newest]

Thread overview: 61+ 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  4:23 ` chihhao.chen
2021-07-24  4:23 ` chihhao.chen
2021-07-24  4:23 ` chihhao.chen
2021-07-24  8:04 ` Takashi Iwai
2021-07-24  8:04   ` Takashi Iwai
2021-07-24  8:04   ` Takashi Iwai
2021-07-24  8:04   ` Takashi Iwai
2021-07-24 15:04   ` Geraldo Nascimento
2021-07-24 15:04     ` Geraldo Nascimento
2021-07-24 15:04     ` Geraldo Nascimento
2021-07-24 15:04     ` Geraldo Nascimento
2021-07-24 15:20     ` Geraldo Nascimento
2021-07-24 15:20       ` Geraldo Nascimento
2021-07-24 15:20       ` Geraldo Nascimento
2021-07-24 15:20       ` Geraldo Nascimento
2021-07-24 18:42       ` Geraldo Nascimento
2021-07-24 18:42         ` Geraldo Nascimento
2021-07-24 18:42         ` Geraldo Nascimento
2021-07-24 18:42         ` Geraldo Nascimento
2021-07-25  7:44     ` Takashi Iwai
2021-07-25  7:44       ` Takashi Iwai
2021-07-25  7:44       ` Takashi Iwai
2021-07-25  7:44       ` Takashi Iwai
2021-07-26  2:16       ` Geraldo Nascimento
2021-07-26  2:16         ` Geraldo Nascimento
2021-07-26  2:16         ` Geraldo Nascimento
2021-07-26  2:16         ` Geraldo Nascimento
2021-07-26  8:42         ` chihhao chen
2021-07-26  8:42           ` chihhao chen
2021-07-26  8:42           ` chihhao chen
2021-07-26  8:42           ` chihhao chen
2021-07-26 20:57           ` Geraldo Nascimento
2021-07-26 20:57             ` Geraldo Nascimento
2021-07-26 20:57             ` Geraldo Nascimento
2021-07-26 20:57             ` Geraldo Nascimento
2021-07-27 10:27             ` chihhao.chen
2021-07-27 10:27               ` chihhao.chen
2021-07-27 10:27               ` chihhao.chen
2021-07-27 10:27               ` chihhao.chen
2021-07-27 17:56               ` Geraldo Nascimento
2021-07-27 17:56                 ` Geraldo Nascimento
2021-07-27 17:56                 ` Geraldo Nascimento
2021-07-27 17:56                 ` Geraldo Nascimento
2021-07-28  1:19                 ` Geraldo Nascimento
2021-07-28  1:19                   ` Geraldo Nascimento
2021-07-28  1:19                   ` Geraldo Nascimento
2021-07-28  1:19                   ` Geraldo Nascimento
2021-08-05  7:54             ` chihhao.chen
2021-08-05  7:54               ` chihhao.chen
2021-08-05  7:54               ` chihhao.chen
2021-08-05  7:54               ` chihhao.chen
2021-08-05 15:50               ` Geraldo Nascimento [this message]
2021-08-05 15:50                 ` Geraldo Nascimento
2021-08-05 15:50                 ` Geraldo Nascimento
2021-08-05 15:50                 ` Geraldo Nascimento
2021-08-05 23:31                 ` Geraldo Nascimento
2021-08-05 22:03                   ` Geraldo Nascimento
2021-08-05 22:03                     ` Geraldo Nascimento
2021-08-05 22:03                     ` Geraldo Nascimento
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=CAEsQvcsvbJdgvAOxkv_kbLohGi676Zrgz4XSFW2o3CWU3Q68Dg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.