From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2A4F5C05027 for ; Wed, 1 Feb 2023 15:08:43 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 598E4832; Wed, 1 Feb 2023 16:07:50 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 598E4832 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1675264120; bh=d58t2J7M4cJC009oe8cHwuEZwsLyzQHFoAEOxTPLj8U=; h=Date:From:To:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Cc:From; b=FicPAMYTgZTMTNnV4VSVa5ESKxvYckXfXlbXcNGQTjdHNrYGni4thzwxP7CgYJbuH ZOLP6dusSjzb7HIOLD/fSnF/1ur/BmqgPOikFg9lTv1Kt5QPEeBZyqAnqp+2RYgO1J PYqh6XS2ur0SaAKlWO8NR5Zs23XwF10iCjJ6Cdzs= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id ED3FBF80155; Wed, 1 Feb 2023 16:07:49 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 947E1F80423; Wed, 1 Feb 2023 16:07:48 +0100 (CET) Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 00DB7F80155 for ; Wed, 1 Feb 2023 16:07:45 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 00DB7F80155 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key, unprotected) header.d=suse.de header.i=@suse.de header.a=rsa-sha256 header.s=susede2_rsa header.b=a7N88MBn; dkim=pass header.d=suse.de header.i=@suse.de header.a=ed25519-sha256 header.s=susede2_ed25519 header.b=TYrX0X1X Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id B323B1FD9A; Wed, 1 Feb 2023 15:07:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1675264065; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rCK8t0N+klofL5r+4F/N4Is+F5OlehSi4QaUBXRPs2w=; b=a7N88MBnJzF1CGL+PYcVLKonwdh6W6DRW9mcRWqcYJzKnVyuaXLftwAVUXjL9lsNzEbd5g 7snhXFym/O8nqHzfMra9/MKW/HTmmstxNhmlht7CdWcZGd+ikPC3py3dx+pQXKqvITHJdE Z/jqVdf1C7FRKRufm1hiikJ2ksKw1eI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1675264065; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rCK8t0N+klofL5r+4F/N4Is+F5OlehSi4QaUBXRPs2w=; b=TYrX0X1XTFPJRq6xSOjFg1SG79/MaqtFabuOZ+yz1PAhnXK1P29xAyBI1gGyqmrkCqXnn+ OL35mGG6yuaV8aDw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id A7DFE13A10; Wed, 1 Feb 2023 15:07:45 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 0namKEGA2mMTCgAAMHmgww (envelope-from ); Wed, 01 Feb 2023 15:07:45 +0000 Date: Wed, 01 Feb 2023 16:07:45 +0100 Message-ID: <87cz6twhj2.wl-tiwai@suse.de> From: Takashi Iwai To: Guillaume Pinot Subject: Re: [PATCH] ALSA: hda/realtek: Fix the speaker output on Samsung Galaxy Book2 Pro 360 In-Reply-To: <20230129171338.17249-1-texitoi@texitoi.eu> References: <20230129171338.17249-1-texitoi@texitoi.eu> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: alsa-devel@alsa-project.org, stable@vger.kernel.org Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Sun, 29 Jan 2023 18:13:38 +0100, Guillaume Pinot wrote: > > Samsung Galaxy Book2 Pro 360 (13" 2022 NP930QED-KA1FR) with codec SSID > 144d:ca03 requires the same workaround for enabling the speaker amp > like other Samsung models with ALC298 codec. > > Cc: > Signed-off-by: Guillaume Pinot > --- > I've tested this fix on my laptop with success. I've took "inspiration" from > https://lore.kernel.org/all/20221115170235.18875-1-tiwai@suse.de/ > > This is my first contribution, so feel free to give me feedbacks! Thanks, applied now. At the next time, though, please put maintainers to Cc. Takashi