> -----Original Message----- > From: Takashi Iwai <tiwai@xxxxxxx> > Sent: Tuesday, February 11, 2020 5:20 PM > To: Kailang <kailang@xxxxxxxxxxx> > Cc: Benjamin Poirier <benjamin.poirier@xxxxxxxxx>; Jaroslav Kysela > <perex@xxxxxxxx>; alsa-devel@xxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 2/2] ALSA: hda/realtek - Fix Lenovo Thinkpad X1 Carbon > 7th quirk value > > On Tue, 11 Feb 2020 10:10:50 +0100, > Kailang wrote: > > > > Hi, > > > > Speaker 2 connect to DAC 0x2 was Lenovo requested. > > This was tune for EQ setting. > > I didn't know more for this. > > Thanks, that was my expectation, too. Applying EQ to built-in speakers is an > oft-seen workaround for laptops to avoid the possible hardware damage. > > Now the question is whether this obvious level of lowering is the expected > result. > > Kailang, could you try to ask Lenovo about it? I have confirmed with our Lenovo AE. > > > Takashi > > > > > BR, > > Kailang > > > > > -----Original Message----- > > > From: Benjamin Poirier <benjamin.poirier@xxxxxxxxx> > > > Sent: Tuesday, February 11, 2020 4:16 PM > > > To: Jaroslav Kysela <perex@xxxxxxxx> > > > Cc: Takashi Iwai <tiwai@xxxxxxx>; Kailang <kailang@xxxxxxxxxxx>; > > > alsa-devel@xxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx > > > Subject: Re: [PATCH 2/2] ALSA: hda/realtek - Fix Lenovo Thinkpad X1 > > > Carbon 7th quirk value > > > > > > On 2020/02/11 08:40 +0100, Jaroslav Kysela wrote: > > > [...] > > > > > > > > > > In summary, Node 0x17 DAC connection 0x3 offers the loudest max > > > > > volume and the most detailed mixer controls. That connection is > > > > > obtained with quirk ALC295_FIXUP_DISABLE_DAC3. Therefore, change > > > > > the ThinkPad X1 Carbon 7th to use ALC295_FIXUP_DISABLE_DAC3. > > > > > > > > The volume split (individual volume control) will cause trouble > > > > for the UCM volume control at the moment which is the target for > > > > this device to get the digital microphone working. If there is no > > > > possibility to share DAC, it would be probably more nice to join > > > > the volume > > > control in the driver. > > > > > > > > Have you tried to use 0x03 as source for all four speakers? > > > > > > Front speakers are fixed to 0x02. Node 0x14 > > > Connection: 1 > > > 0x02 > > > > > > > > > > > Why PA handles the rear volume control with the current driver > > > > code in the legacy ALSA driver? It should be handled like standard > > > > stereo device. I'll check. > > > > > > The device comes up with "Analog Stereo Output" profile by default. > > > I changed it to "Analog Surround 4.0 Output" to test controlling each > channel individually: > > > > > > > > pavucontrol controls are reported with the device configured > > > > > with the "Analog Surround 4.0 Output" profile. > > > > > > > > > > > You should also test PA with UCM. > > > > > > Please let me know what do I need to test exactly? I'm not familiar with > UCM. > > > > > > ------Please consider the environment before printing this e-mail. > > _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
