Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp4930557ybv; Tue, 11 Feb 2020 06:07:05 -0800 (PST) X-Google-Smtp-Source: APXvYqyDXhKS2e3Zli1mL97ztDN8xQzfhPoYBbANzILLmv0+LSlLaQvN7xuD1uFyNUM9IGXoAuZo X-Received: by 2002:a05:6830:1218:: with SMTP id r24mr5509338otp.144.1581430025497; Tue, 11 Feb 2020 06:07:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581430025; cv=none; d=google.com; s=arc-20160816; b=CvzCNuzf6pFCduEBOdAfZFVSMQ0uZuZ2aTCBseXlUTUS8oS7x7NDXIu33MjYMqjW+7 zvJ8rtM0yjrBHGyGwlohV21sJ7AWo609QSnVigIZRznKIeiSJLMMp0cOoEsrDnJA0mQR pssrpcqITVz/cTp+GCDqW1YDc3BEgf3J4Fo6UkROXWQcexD1sbgPc6xfF/NGpiXoUKZs TqjBQKDr0lY0k02Oqvp4TCgbsF/jtwPiRRqI90wFK+vXQqOdqw52sP1fAg6w5BA6xVGy lsxWUblH8Efs/29iAMM6IoufHI2iO7AgXjRhAw7lFKKyvHkrdRKfBOVz89F3IpCoOuVp QiFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature:dkim-filter; bh=0Efa0Tgr98zcPceZ4tbN4DZiSyq5I8m4PkCL59yHp3o=; b=ShFRP+geuPzryRQjZ1gSuGaeHTLvxnS/mBYcFRctVES3yW2g9xalQP/VPzIPz0o4kU Ol3As33cPQgW8EmCDhBFH8tCwaNhkKCSAJM/rTLMKgk6tb5w1T0IrfWyqluyo23Do5NT tLPanG7TDa6U4jYOBbPKKv8KyXso3Vg5SjHNSPddqOq5iRYptJdU1aJ63JdVTWaolA1O HAlQ6Ek0xXNVu4rC9IhNJjwQQROid8WE3PBg2KzaGN+JU13MyN62quv5bhFwxzpLsc8q mW3I9s5/VigQAkh7XPnr+9uvVdawNXl9GTCT5BvhAKh+afq9tdS/eFGzpR9k/wXgNy1r pnJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@perex.cz header.s=default header.b=NN8HG1D2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=perex.cz Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j20si1922514otp.147.2020.02.11.06.06.43; Tue, 11 Feb 2020 06:07:05 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@perex.cz header.s=default header.b=NN8HG1D2; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=perex.cz Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729335AbgBKN47 (ORCPT + 99 others); Tue, 11 Feb 2020 08:56:59 -0500 Received: from mail1.perex.cz ([77.48.224.245]:57312 "EHLO mail1.perex.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729940AbgBKN45 (ORCPT ); Tue, 11 Feb 2020 08:56:57 -0500 Received: from mail1.perex.cz (localhost [127.0.0.1]) by smtp1.perex.cz (Perex's E-mail Delivery System) with ESMTP id 7D989A003F; Tue, 11 Feb 2020 14:56:54 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.perex.cz 7D989A003F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=perex.cz; s=default; t=1581429414; bh=0Efa0Tgr98zcPceZ4tbN4DZiSyq5I8m4PkCL59yHp3o=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=NN8HG1D2L/3gEJ/meRsyWd/7KBVTrXmjMaIcYTXyVfkFDnO1MS8+732vArByas6dR Bl4sYldTseqMeA2YjD2Rh6QswFfDPRFCeNicytb4Kk3DCLIzAco8ygmmrPNgac1SFj zkkTGQrTt5PtbL120pT1SlmEEAx7V2OHqecum6+g= Received: from p50.perex-int.cz (unknown [192.168.100.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: perex) by mail1.perex.cz (Perex's E-mail Delivery System) with ESMTPSA; Tue, 11 Feb 2020 14:56:49 +0100 (CET) Subject: Re: [PATCH 2/2] ALSA: hda/realtek - Fix Lenovo Thinkpad X1 Carbon 7th quirk value To: Benjamin Poirier Cc: Takashi Iwai , Kailang Yang , alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org References: <20200211055651.4405-1-benjamin.poirier@gmail.com> <20200211055651.4405-2-benjamin.poirier@gmail.com> <20200211081604.GA8286@f3> <901c395a-7fb5-5672-5955-d6d211824177@perex.cz> <20200211114236.GA2691@f3> From: Jaroslav Kysela Message-ID: <1274df6a-010c-0e84-d916-f59c36ae3993@perex.cz> Date: Tue, 11 Feb 2020 14:56:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <20200211114236.GA2691@f3> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dne 11. 02. 20 v 12:42 Benjamin Poirier napsal(a): > On 2020/02/11 10:35 +0100, Jaroslav Kysela wrote: >> Dne 11. 02. 20 v 9:16 Benjamin Poirier napsal(a): > [...] >>>> >>>> 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: >> >> Yes, but does the volume control work (does PA change the appropriate ALSA >> mixer volume)? Sometimes, it's difficult to see the difference between soft >> volume attenuation and the hardware volume control. > > I see what you mean. > When set to the "Analog Surround 4.0 Output", pulseaudio didn't change > the "Bass Speaker" mixer (always at 0dB gain). It used a combination of > Master, Front and sometimes PCM mixers to control all four speakers. Yes, that was the reason to keep only one volume control in the driver until we have a solution for this. > For example: > pacmd list-sinks > name: > volume: front-left: 10349 / 16% / -48.09 dB, front-right: > 39377 / 60% / -13.27 dB, rear-left: 23979 / 37% / -26.20 dB, > rear-right: 47974 / 73% / -8.13 dB > balance 0.61 > alsactl -f /tmp/output store 0 > iface MIXER > name 'Front Playback Volume' > value.0 33 > value.1 79 > range '0 - 87' > > name 'Bass Speaker Playback Volume' > value.0 87 > value.1 87 > range '0 - 87' > > name 'Master Playback Volume' > value 77 > range '0 - 87' > > name 'PCM Playback Volume' > value.0 255 > value.1 255 > range '0 - 255' > >>>> >>>> You should also test PA with UCM. >>> >>> Please let me know what do I need to test exactly? I'm not familiar with >>> UCM. >> >> Just install the latest pulseaudio (latest from repo), alsa-lib and >> alsa-ucm-conf (also from repo). If pulseaudio detects UCM, it has the >> preference. > > Using the packages in debian unstable, `pacmd list` shows "use_ucm=yes". > alsa-ucm-conf was already installed. Hopefully that's enough. > > ii alsa-ucm-conf 1.2.1.2-2 all ALSA Use Case Manager configuration files > ii libasound2:amd64 1.2.1.2-2 amd64 shared library for ALSA applications > ii pulseaudio 13.0-5 amd64 PulseAudio sound server You should use the latest code. I will release ALSA packages version 1.2.2 soon, but PA must be latest (not yet released 14.0). Previous versions do not handle the volume control and HDMI jack detection. There are many UCM changes in 14.0. Jaroslav > > pacmd list > name: > argument: card_name="alsa_card.pci-0000_00_1f.3" namereg_fail=false > tsched=yes fixed_latency_range=no ignore_dB=no > deferred_volume=yes use_ucm=yes avoid_resampling=no > card_properties="module-udev-detect.discovered=1"> > -- Jaroslav Kysela Linux Sound Maintainer; ALSA Project; Red Hat, Inc.