From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: chihhao.chen@mediatek.com, 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: Sat, 24 Jul 2021 15:20:47 +0000 [thread overview]
Message-ID: <CAEsQvcu3jXa4fXJAu7nvT+G+-S2bZ1BPkcuwnT4VjbrnW1Pkog@mail.gmail.com> (raw)
In-Reply-To: <CAEsQvcs3P+TqQFzQetPfRycpo66eJFwnzwhk2JyCXFaCLFHmFg@mail.gmail.com>
> Dr. Iwai, perhaps we could restrict the generalized fix for the
> Behringer UFX1604 / UFX1204 with some simple logic to devices that
> only have *one* clock source.
Okay, rereading the original commit log from Cihhao Chen I gather
Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051) actually has
two clock selectors and only one clock source.
Correct me if I'm wrong.
This is complicated by the fact I haven't been able to find a lsusb -v
of Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051)
Even so, my proposition still stands: devices with only one clock
source and only one clock selector should be able to handle us
selecting the clock selector to the only clock source.
WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, wsd_upstream@mediatek.com,
damien@zamaudio.com, linux-kernel@vger.kernel.org,
tiwai@suse.com, chihhao.chen@mediatek.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: Sat, 24 Jul 2021 15:20:47 +0000 [thread overview]
Message-ID: <CAEsQvcu3jXa4fXJAu7nvT+G+-S2bZ1BPkcuwnT4VjbrnW1Pkog@mail.gmail.com> (raw)
In-Reply-To: <CAEsQvcs3P+TqQFzQetPfRycpo66eJFwnzwhk2JyCXFaCLFHmFg@mail.gmail.com>
> Dr. Iwai, perhaps we could restrict the generalized fix for the
> Behringer UFX1604 / UFX1204 with some simple logic to devices that
> only have *one* clock source.
Okay, rereading the original commit log from Cihhao Chen I gather
Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051) actually has
two clock selectors and only one clock source.
Correct me if I'm wrong.
This is complicated by the fact I haven't been able to find a lsusb -v
of Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051)
Even so, my proposition still stands: devices with only one clock
source and only one clock selector should be able to handle us
selecting the clock selector to the only clock source.
WARNING: multiple messages have this Message-ID (diff)
From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: chihhao.chen@mediatek.com, 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: Sat, 24 Jul 2021 15:20:47 +0000 [thread overview]
Message-ID: <CAEsQvcu3jXa4fXJAu7nvT+G+-S2bZ1BPkcuwnT4VjbrnW1Pkog@mail.gmail.com> (raw)
In-Reply-To: <CAEsQvcs3P+TqQFzQetPfRycpo66eJFwnzwhk2JyCXFaCLFHmFg@mail.gmail.com>
> Dr. Iwai, perhaps we could restrict the generalized fix for the
> Behringer UFX1604 / UFX1204 with some simple logic to devices that
> only have *one* clock source.
Okay, rereading the original commit log from Cihhao Chen I gather
Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051) actually has
two clock selectors and only one clock source.
Correct me if I'm wrong.
This is complicated by the fact I haven't been able to find a lsusb -v
of Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051)
Even so, my proposition still stands: devices with only one clock
source and only one clock selector should be able to handle us
selecting the clock selector to the only clock source.
_______________________________________________
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: Takashi Iwai <tiwai@suse.de>
Cc: chihhao.chen@mediatek.com, 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: Sat, 24 Jul 2021 15:20:47 +0000 [thread overview]
Message-ID: <CAEsQvcu3jXa4fXJAu7nvT+G+-S2bZ1BPkcuwnT4VjbrnW1Pkog@mail.gmail.com> (raw)
In-Reply-To: <CAEsQvcs3P+TqQFzQetPfRycpo66eJFwnzwhk2JyCXFaCLFHmFg@mail.gmail.com>
> Dr. Iwai, perhaps we could restrict the generalized fix for the
> Behringer UFX1604 / UFX1204 with some simple logic to devices that
> only have *one* clock source.
Okay, rereading the original commit log from Cihhao Chen I gather
Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051) actually has
two clock selectors and only one clock source.
Correct me if I'm wrong.
This is complicated by the fact I haven't been able to find a lsusb -v
of Samsung USBC Headset (AKG) with VID/PID (0x04e8/0xa051)
Even so, my proposition still stands: devices with only one clock
source and only one clock selector should be able to handle us
selecting the clock selector to the only clock source.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-24 18:21 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 [this message]
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
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=CAEsQvcu3jXa4fXJAu7nvT+G+-S2bZ1BPkcuwnT4VjbrnW1Pkog@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.