From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julian Sikorski Subject: Re: model needed for Clevo P150HM (Realtek ALC892) Date: Fri, 01 Jul 2011 09:07:47 +0200 Message-ID: <4E0D7243.7030202@gmail.com> References: <4E036C8F.3080709@gmail.com> <4E047441.4010003@gmail.com> <4E05C1B1.50302@gmail.com> <4E05C704.4080806@gmail.com> <4E05CE02.1070801@gmail.com> <4E082166.5060902@gmail.com> <4E08E33D.3060608@gmail.com> <4E0B62B6.6000007@gmail.com> <4E0B6BE0.1010003@gmail.com> <4E0B7D22.3040009@gmail.com> <4E0C17F2.5070704@gmail.com> <4E0CABBC.3070801@gmail.com> <4E0CBBED.9050501@gmail.com> <4E0CD984. 9050408@gmail.com> <4E0D65C2.7070106@gmail.com> <4E0D68EB.5020909@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ww0-f51.google.com (mail-ww0-f51.google.com [74.125.82.51]) by alsa0.perex.cz (Postfix) with ESMTP id 77DDA10394D for ; Fri, 1 Jul 2011 09:07:51 +0200 (CEST) Received: by wwj26 with SMTP id 26so2249120wwj.20 for ; Fri, 01 Jul 2011 00:07:51 -0700 (PDT) In-Reply-To: <4E0D68EB.5020909@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org List-Id: alsa-devel@alsa-project.org W dniu 01.07.2011 08:27, Julian Sikorski pisze: > W dniu 01.07.2011 08:24, Takashi Iwai pisze: >> At Fri, 01 Jul 2011 08:14:26 +0200, >> Julian Sikorski wrote: >>> >>> W dniu 01.07.2011 07:21, Takashi Iwai pisze: >>>> At Thu, 30 Jun 2011 22:16:04 +0200, >>>> Julian Sikorski wrote: >>>>> >>>>> W dniu 30.06.2011 21:28, Takashi Iwai pisze: >>>>>> At Thu, 30 Jun 2011 20:09:49 +0200, >>>>>> Julian Sikorski wrote: >>>>>>> >>>>>>> $ dmesg | grep XXX >>>>>>> [ 14.813013] XXX alc662_auto_fill_dac_nids called >>>>>>> [ 14.813015] XXX line_outs=1, 14/0/0 >>>>>>> [ 14.813016] XXX hp_outs=1, 1b/0/0 >>>>>>> [ 14.813018] XXX spk_outs=0, 0/0/0 >>>>>>> [ 14.813186] XXX filled dacs: 2/0/0/0/0, hp 0, ext 0/0/0 >>>>>>> [ 14.813187] XXX swap primary out to HP >>>>>>> [ 14.813188] XXX spk=14 >>>>>>> [ 14.813190] XXX line=1b >>>>>>> [ 14.813191] XXX alc662_auto_fill_dac_nids called >>>>>>> [ 14.813192] XXX line_outs=1, 1b/0/0 >>>>>>> [ 14.813194] XXX hp_outs=0, 0/0/0 >>>>>>> [ 14.813195] XXX spk_outs=1, 14/0/0 >>>>>>> [ 14.813311] XXX filled dacs: 2/0/0/0/0, hp 0, ext 0/0/0 >>>>>>> [ 14.813560] XXX added multi-io pin 1a, dac 3 >>>>>>> [ 14.813814] XXX added multi-io pin 18, dac 4 >>>>>>> [ 14.813818] XXX create mixer ch 0 pin 1b dac 2 mix c >>>>>>> [ 14.813821] XXX create mixer ch 1 pin 1a dac 3 mix d >>>>>>> [ 14.813825] XXX create mixer ch 2 pin 18 dac 4 mix e >>>>>> >>>>>> How about the fix below? >>>>>> >>>>>> >>>>>> Takashi >>>>> >>>>> It works, thanks! In more detail, the Speaker/Headphone situation is >>>>> back to 2.6.38 state - you can regulate them independently, but muting >>>>> one mutes the other. LFE/Center and Surround keep working correctly too. >>>>> The new output of alsa-info.sh: >>>>> http://www.alsa-project.org/db/?f=45bc0df9747371b348bde6c4aa508b2ba44aff47 >>>> >>>> Right, it's because ALC892 has no mute-control in pin widgets but >>>> only in the mixer widget. And HP and speaker paths share the same >>>> mixer, thus it's impossible to mute independently. >>> >>> I assume that the auto-mute function uses a different approach then - it >>> disables the speakers sound when headphone jack is plugged in. >> >> Yes, it changes the pin-control value. > > Thanks for clarification. > >>>>> So it seems that the only things remaining are the SPDIF/rear channel >>>>> jack and the coupled muting issue. >>>> >>>> It's a BIOS bug. It doesn't tell SPDIF is available. >>>> Ditto for the 4th stereo out. No pin is exposed by BIOS. >>> >>> I see. I can try updating the BIOS and see if it changes anything. If it >>> doesn't, is there a way to work the problem around in the driver? >> >> You need to figure out pins manually by yourself, then change the >> driver code. I leave it as a homework :) > > :) I cannot write code, so I would not count on myself doing that. I > will have a look into updating the BIOS though. > >> thanks, >> >> Takashi > > Once again thanks for all the work you have done, > > Julian Hmm, I googled a bit and it seems the way to find the pins is to write values to user_pin_configs. So no coding knowledge seems needed, could you give me some pointers on where to start? Thanks, Julian