[alsa-devel] move alc892 to patch_alc882
Hi Takashi, The original was patch to patch_alc662. Move it into patch_alc882. Thanks. BR, Kailang
At Thu, 27 Mar 2014 17:47:11 +0800, Kailang wrote:
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
Could you give a bit more background *why* this change is necessary? It's the most important part. Please put into the patch description and resubmit. thanks, Takashi
Thanks.
BR, Kailang [2 0000-move-alc892-to-patch_alc882.patch <application/octet-stream (quoted-printable)>]
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ?
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ?
Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang. Takashi
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ?
Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
Takashi
------Please consider the environment before printing this e-mail.
At Mon, 7 Apr 2014 14:04:34 +0800, Kailang wrote:
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ?
Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog. Takashi
Takashi
------Please consider the environment before printing this e-mail.
Hi Takashi, In our test, it is better to set Mic2-vref control to manual mode. It will have better result for HP pop noise. So, I fill it back in this patch. BR, Kailang
At Mon, 7 Apr 2014 16:59:23 +0800, Kailang wrote:
Hi Takashi,
In our test, it is better to set Mic2-vref control to manual mode. It will have better result for HP pop noise. So, I fill it back in this patch.
OK, I applied it now. Thanks. Takashi
BR, Kailang [2 0000-improve-hp-pop-noise.patch <application/octet-stream (quoted-printable)>]
Hi Takashi, Chrome OS was use alc283-dac-wcaps module name as default in their kernel. I was create the change patch for future support. Thanks. BR, Kailang
At Tue, 8 Apr 2014 15:34:18 +0800, Kailang wrote:
Hi Takashi,
Chrome OS was use alc283-dac-wcaps module name as default in their kernel. I was create the change patch for future support.
You mean "model" name, right? If so, please correct and resubmit the patch. thanks, Takashi
Oh! sorry.. Attach again.
At Tue, 8 Apr 2014 15:34:18 +0800, Kailang wrote:
Hi Takashi,
Chrome OS was use alc283-dac-wcaps module name as default in their kernel. I was create the change patch for future support.
You mean "model" name, right? If so, please correct and resubmit the patch.
thanks,
Takashi
------Please consider the environment before printing this e-mail.
At Tue, 8 Apr 2014 16:06:22 +0800, Kailang wrote:
Oh! sorry.. Attach again.
Thanks, applied. Takashi
At Tue, 8 Apr 2014 15:34:18 +0800, Kailang wrote:
Hi Takashi,
Chrome OS was use alc283-dac-wcaps module name as default in their kernel. I was create the change patch for future support.
You mean "model" name, right? If so, please correct and resubmit the patch.
thanks,
Takashi
------Please consider the environment before printing this e-mail. [2 0000-change-model-name-for-chrome.patch <application/octet-stream (quoted-printable)>]
git clone git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git sound.git I use upper to download kernel source code. It only has master branch. If i run git pull, it couldn't update for-linus branch. Right? When is the for-linus or for-next will be merged into master? Thanks
At Tue, 8 Apr 2014 16:06:22 +0800, Kailang wrote:
Oh! sorry.. Attach again.
Thanks, applied.
Takashi
At Tue, 8 Apr 2014 15:34:18 +0800, Kailang wrote:
Hi Takashi,
Chrome OS was use alc283-dac-wcaps module name as default in their kernel. I was create the change patch for future support.
You mean "model" name, right? If so, please correct and resubmit the patch.
thanks,
Takashi
------Please consider the environment before printing this e-mail. [2 0000-change-model-name-for-chrome.patch <application/octet-stream (quoted-printable)>]
Hi Takashi, Maybe internal speaker will have pop noise when system enter to suspend. Add eapd shutup to alc283_shutup. Thanks. BR, Kailang
At Mon, 7 Apr 2014 14:04:34 +0800, Kailang wrote:
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
Hi Takashi,
The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ?
Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
Takashi
Takashi
------Please consider the environment before printing this e-mail.
2014-4-7 下午5:20 於 "Kailang" <kailang@realtek.com> 寫道：
At Mon, 7 Apr 2014 14:04:34 +0800, Kailang wrote:
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
> Hi Takashi, > > The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ? Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc... + { 0x10ec0892, 0xffff, 0x8020, "ALC661" }, + { 0x10ec0892, 0xffff, 0x8011, "ALC661" }, + { 0x10ec0892, 0xffff, 0x4011, "ALC656" }, Seem some codec were renamed as alc661 and alc656
2014-4-7 下午5:20 於 "Kailang" <kailang@realtek.com> 寫道：
At Mon, 7 Apr 2014 14:04:34 +0800, Kailang wrote:
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
> Hi Takashi, > > The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ? Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc...
+ { 0x10ec0892, 0xffff, 0x8020, "ALC661" }, + { 0x10ec0892, 0xffff, 0x8011, "ALC661" }, + { 0x10ec0892, 0xffff, 0x4011, "ALC656" }, Seem some codec were renamed as alc661 and alc656
Yes, it's the same body. IC mark shows different. ------Please consider the environment before printing this e-mail.
>> > > The original was patch to patch_alc662. > Move it into patch_alc882. > > is there any reason not including those PCI QUIRK for alc892 ? Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc...
+ { 0x10ec0892, 0xffff, 0x8020, "ALC661" }, + { 0x10ec0892, 0xffff, 0x8011, "ALC661" }, + { 0x10ec0892, 0xffff, 0x4011, "ALC656" }, Seem some codec were renamed as alc661 and alc656
Yes, it's the same body. IC mark shows different.
Can the driver assume all desktop with alc8xx codecs support multistreaming playback ? It seem that alc6xx does not support multistreaming playback
Hi Raymond, Your multi-streaming means muti channel out or separate output at the same time. BR, Kailang ----- Original Message ----- 寄件者: Raymond Yau 收件者: Kailang 副本: Takashi Iwai ; ALSA Development Mailing List 傳送日期: 2014年4月9日 下午 12:53 主旨: Re: [alsa-devel] move alc892 to patch_alc882
>> > > The original was patch to patch_alc662. > Move it into patch_alc882. > > is there any reason not including those PCI QUIRK for alc892 ? Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc...
+ { 0x10ec0892, 0xffff, 0x8020, "ALC661" }, + { 0x10ec0892, 0xffff, 0x8011, "ALC661" }, + { 0x10ec0892, 0xffff, 0x4011, "ALC656" }, Seem some codec were renamed as alc661 and alc656
Yes, it's the same body. IC mark shows different.
Can the driver assume all desktop with alc8xx codecs support multistreaming playback ? It seem that alc6xx does not support multistreaming playback ------Please consider the environment before printing this e-mail.
2014-4-9 下午2:30 於 "Kailang" <kailang@realtek.com> 寫道：
Hi Raymond,
Your multi-streaming means muti channel out or separate output at the
same time. Seem most 6 channels codecs does not support multisteaming playback The ALC892 provides ten DAC channels that simultaneously support 7.1 channel sound playback, plus 2 channels of independent stereo sound output (multiple streaming) through the front panel stereo outputs The ALC231 is a High Definition Audio Codec that integrates a 4-channel DAC, 4-channel ADC, and a mono and filter-less Class-D Speaker Amplifier with 2Watt (rms) output power. The 4-channel DAC and 4-channel ADC support two independent stereo sound outputs and two independent stereo inputs simultaneously; allowing multiple streaming playback and output for multimedia applications and voice communication.
At Sat, 5 Apr 2014 14:52:24 +0800, Raymond Yau wrote:
> Hi Takashi, > > The original was patch to patch_alc662. Move it into patch_alc882.
is there any reason not including those PCI QUIRK for alc892 ? Because it's not clarified why this must be applied. I'm waiting for the updated patch from Kailang.
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882.
The driver seem assume unique PCI ssid but it seem gigabyte motherboards use same ssid 0x1458, 0xa002 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc... https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc... https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pc...
Sorry! I just aligned the channel count. So, move the alc892 to patch_alc882.
As I already asked, could you resubmit the patch with the proper changelog? You have to clarify why the patch is needed and how it's solved in the patch changelog.
Yes, but it maybe doesn't solve any thing. But I remember I solve 8ch issue which run for patch_alc882. I will check alc892 for run with patch_alc882. Thanks.
AFAIK, 8ch is not yet supported by generic driver for those desktop motherboard 1) with 5 jacks at rear panel (retask line in as side) 2) 10 channel codec with 3 jacks at rear panel(retask front HP as side)
participants (3)
-
Kailang -
Raymond Yau -
Takashi Iwai