Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp5533093pxv; Wed, 28 Jul 2021 13:04:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrjicwVtGjGv+dif3KuU0LNx/u8JVMveoWh0n7ToSFtgjzAXWpCiE4yVUr5Ye+aEtaTn09 X-Received: by 2002:a02:380b:: with SMTP id b11mr1268393jaa.83.1627502696686; Wed, 28 Jul 2021 13:04:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627502696; cv=none; d=google.com; s=arc-20160816; b=OPpZ3lm4GvQRc9rSXyeP8L+UQaMU9pAwk+7C/Q2NZ/qUNbi9R7XIGbgJ5/rFru7JVJ pcp6/cfvFQM3vLGz4XzL31UgVeggpxDXJN6E7/U9O8kgbIfqViqLeUF/f1V9NA2gH0VV jZ9dQUJug1AtmK5TASkGvyAvIJWqVcDe0pKaKnXYzdvcA7IBdRTUHSKAKrxOkH3llfLt PKutYJddLARi4BCvPlC6JY20H3/0fnoxR0QvQRQrL7q8ZTtc+2YKy1UuM7+gFeb4+a82 2QIBMop/trl1gJClZ0IlpJe9cp2VvTQvpGSdk/TnnemYLsoiqx1YRwyw5+CdRW3HXxeE 675g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:message-id :in-reply-to:subject:cc:to:from:date; bh=FVvVuTlC9A2H+CWNPRO+OIIqK1TrGtuxPg0nZA+dL40=; b=ZL5l55QjQVl+59h6wmOYb8Cp238xffOQSggYVDZgpFMqvhWU+chjE1C7pO9EuxjmhN nP/WvQsJaMBOXaiTNVWd8O/NMtVR4dmnLi7aYl10el7UR8ckVepf5bucVkVasiIJlKeS CrzlXCRxmPJBwfxzpuiMagxVs5lb946NB5Guk40U5soGKgrK4jDRojIH8FQ5g+micXwT B/GxdbC8YPWPClMh/0splThjmxy5ZMIAyF1/8rCdMKmrc/8SAbRsFLk0CCZ1vyXanD0s R9NuM9fBjS3GvQFhlX5iwAg+iX+O7umQ9I6FkkeBfaCiwF2KDlY7FobXGoXZcVe7jLVM sNBA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ispras.ru Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y11si854727jai.105.2021.07.28.13.04.44; Wed, 28 Jul 2021 13:04:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ispras.ru Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231243AbhG1UDv (ORCPT + 99 others); Wed, 28 Jul 2021 16:03:51 -0400 Received: from mail.ispras.ru ([83.149.199.84]:35726 "EHLO mail.ispras.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231126AbhG1UDv (ORCPT ); Wed, 28 Jul 2021 16:03:51 -0400 Received: from monopod.intra.ispras.ru (unknown [10.10.3.121]) by mail.ispras.ru (Postfix) with ESMTPS id 6F2F340755F2; Wed, 28 Jul 2021 20:03:45 +0000 (UTC) Date: Wed, 28 Jul 2021 23:03:45 +0300 (MSK) From: Alexander Monakov To: Takashi Iwai cc: linux-kernel@vger.kernel.org, Jaroslav Kysela , Takashi Iwai , Hui Wang , Kailang Yang , Jeremy Szu , Jian-Hong Pan , Chris Chiu , PeiSen Hou , alsa-devel@alsa-project.org Subject: Re: [PATCH] ALSA: hda/realtek: add mic quirk for Acer SF314-42 In-Reply-To: Message-ID: References: <20210721170141.24807-1-amonakov@ispras.ru> User-Agent: Alpine 2.20.13 (LNX 116 2015-12-14) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Jul 2021, Takashi Iwai wrote: > > 1) at high enough gain, recording the microphone is picking up what is > > being played via the headphones; maybe it's supposed to be like that, > > but it surprised me; > > Hrm, that doesn't sound right. Some internal loopback in the codec? > Dunno. It doesn't pick up the sound physically, right? How can I tell? If I don't have anything plugged into the jack, playback uses the built-in speakers. In that case there's no feedback. And if I plug in a headset or common headphones, then built-in speakers are automatically muted, and recording the mic can pick up the output signal. Is there a way to forcefully direct output to the jack instead of built-in speakers even when there isn't anything plugged in? I am sure it is not picking the sound over the air, but I'm considering it's picking it up electrically near the jack somehow. > > 2) there is a very noticeable "pop" when plugging the headset in/out, > > accompanied by > > > > pcieport 0000:00:08.1: PME: Spurious native interrupt! > > pcieport 0000:00:08.1: PME: Spurious native interrupt! > > > > in dmesg. I'd appreciate info and any help about this issue. > > The pop noise is often a thing with the codec and there are a bunch of > different workarounds found in the driver. But the spurious interrupt > is more worrisome. Is the PCI slot corresponding to the HD-audio > controller? No, it's actually the PCI bridge under which the HDA core resides: 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:08.1/03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller Note that I have autosuspend enabled for PCI devices. If I disable PCI autosuspend for the 03:00.6 HDA device, there's no "pop" and no spurious interrupt. My understanding that the chip generates a power management event when it senses a jack plug/unplug event while suspended. Apparently something about the PME interrupt is not fully in order? > As of now, I'm inclined to take your patch as is, at least as a > first-aid workaround. Let's see whether we get a better development > soonish. *nod*, I will appreciate it! Thank you. Alexander