Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp1418437pxb; Fri, 10 Sep 2021 05:37:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxtBMIPppRoHowyRdng7x2zq0PtTitm3oURWMHn1TZk/Yw1i3LAHz6C0mfFRGejkddQHo/r X-Received: by 2002:a05:6602:2c07:: with SMTP id w7mr6819163iov.122.1631277475166; Fri, 10 Sep 2021 05:37:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631277475; cv=none; d=google.com; s=arc-20160816; b=ST6tOQiXdKcN7vTvY+TC7C82r7yrNClGN0L3Ek8UYVTAzDmNq/EOs3QGnWkxnu5Ia9 CkVq3110A2yVZi39+IUzi4lxDgwhZ9tab1utkVgwE19yNPYkWc0IpyQiUDBekMi+A7Vn v9O58XeT0mxTrmqkJGt9p1h7uQK8shuV23DaO0at9KbnS27jh9Ka8k9ThC2P2+BAoc76 uY+usjT6aR55cZ/I9hctVQ4udMz9/yPD/4eJZfb9x+L09ElaAHDWKoQFktiB7PFOuhah ac5WOZL/q21ozmx/Lyg0Kko1fBu8N9pe2jDzaK7SnXRBaEYhSr6FNgmeQruuIeVsZp5r 552w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=RXSycMIcQ+EY9/EM1dAMcSVP5jh/YHD0hrzISRBLejo=; b=NzcxkrOtJtPFYNDIrOPouBZmvGMPTD9FZv6njf3qQf67voxPpk6Xjervmw78vwDwDh koepfESJnMrLLsxTxkQ28ODvDJCU+MppzUFrAGxN9ug7Le+E4NfEVrSAD5k9+8sOsM80 EptwJ/+KLtoBs4/az6XjOCl714V4RMvIV++rZs1vkIwn6oY7nrg5/spt2u9CjO38niWa qj7YijTLdSW2/bjiFkOvS0bXZF0bqr1eJLvppBDcHYvtlr9ZU4p+VXjFM1825t8SCCvm J+W33zcK/uWUuWBm9ysAM+QICfk/8dV+6RHOhasdVDA14WYvZxH3yzcRqNJM6uY5dAsf D4ww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=o8w7uOGw; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v3si5182966jat.11.2021.09.10.05.37.43; Fri, 10 Sep 2021 05:37:55 -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; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=o8w7uOGw; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234873AbhIJMhO (ORCPT + 99 others); Fri, 10 Sep 2021 08:37:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:54634 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234434AbhIJMfw (ORCPT ); Fri, 10 Sep 2021 08:35:52 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id F314D61206; Fri, 10 Sep 2021 12:34:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1631277278; bh=WSnMHjzypwQ7Fjbes+Eoz5ZjFsK+4pYENgGUMoTuVxU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=o8w7uOGw9fakfG/ZwQ3UZD01dGQB6I6fsk3xr37vfc4+q03vBT5YxurVKjuu84msC Mtj1OWk7fuqMSBVr+EeGMz8jUTYEKUgRthNCf9jKM7zSGv3LDOIzAgCd3F71D79k0b Er9bjuyQcN+fjkbhJgPo5tWA5kR1Rgr8h5Wsox/Y= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Takashi Iwai Subject: [PATCH 5.4 18/37] ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 Date: Fri, 10 Sep 2021 14:30:21 +0200 Message-Id: <20210910122917.767802823@linuxfoundation.org> X-Mailer: git-send-email 2.33.0 In-Reply-To: <20210910122917.149278545@linuxfoundation.org> References: <20210910122917.149278545@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Takashi Iwai commit 13d9c6b998aaa76fd098133277a28a21f2cc2264 upstream. ASUS ROG Strix G17 has the very same PCI and codec SSID (1043:103f) as ASUS TX300, and unfortunately, the existing quirk for TX300 is broken on ASUS ROG. Actually the device works without the quirk, so we'll need to clear the quirk before applying for this device. Since ASUS ROG has a different codec (ALC294 - while TX300 has ALC282), this patch adds a workaround for the device, just clearing the codec->fixup_id by checking the codec vendor_id. It's a bit ugly to add such a workaround there, but it seems to be the simplest way. BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=214101 Cc: Link: https://lore.kernel.org/r/20210820143214.3654-1-tiwai@suse.de Signed-off-by: Takashi Iwai Signed-off-by: Greg Kroah-Hartman --- sound/pci/hda/patch_realtek.c | 10 ++++++++++ 1 file changed, 10 insertions(+) --- a/sound/pci/hda/patch_realtek.c +++ b/sound/pci/hda/patch_realtek.c @@ -9160,6 +9160,16 @@ static int patch_alc269(struct hda_codec snd_hda_pick_fixup(codec, alc269_fixup_models, alc269_fixup_tbl, alc269_fixups); + /* FIXME: both TX300 and ROG Strix G17 have the same SSID, and + * the quirk breaks the latter (bko#214101). + * Clear the wrong entry. + */ + if (codec->fixup_id == ALC282_FIXUP_ASUS_TX300 && + codec->core.vendor_id == 0x10ec0294) { + codec_dbg(codec, "Clear wrong fixup for ASUS ROG Strix G17\n"); + codec->fixup_id = HDA_FIXUP_ID_NOT_SET; + } + snd_hda_pick_pin_fixup(codec, alc269_pin_fixup_tbl, alc269_fixups, true); snd_hda_pick_pin_fixup(codec, alc269_fallback_pin_fixup_tbl, alc269_fixups, false); snd_hda_pick_fixup(codec, NULL, alc269_fixup_vendor_tbl,