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 X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2B53EC433ED for ; Fri, 16 Apr 2021 16:26:04 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id ED1A1613B0 for ; Fri, 16 Apr 2021 16:26:02 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org ED1A1613B0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id AF83016B8; Fri, 16 Apr 2021 18:25:10 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz AF83016B8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1618590360; bh=Oy062SqzNLRd6yDxAsAWtiU2WdhY57eu138/wIMGoTs=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=lo5ARovMGrBOlRW6rlrAEgOVnJ5wVDcbA69a88MIjdwVXYsw9ftP5BNEiSgnzig9S sRDBMhoo+fMZiRVUgbSswGMxKZGUcnhgvDCKVKcUDEDkOWC4rhN7mQ/ewzEc4DZvbF OQvyxoYX5r8a+D7laIg2vvC/zLwO6N+DIjDaEFtc= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 3AA2EF80254; Fri, 16 Apr 2021 18:25:10 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 1CBAAF8025B; Fri, 16 Apr 2021 18:25:09 +0200 (CEST) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id A6CA2F80128 for ; Fri, 16 Apr 2021 18:25:06 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz A6CA2F80128 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 912ECB1C9; Fri, 16 Apr 2021 16:25:05 +0000 (UTC) Date: Fri, 16 Apr 2021 18:25:05 +0200 Message-ID: From: Takashi Iwai To: Pierre-Louis Bossart Subject: Re: [PATCH] ALSA: hda/realtek: Add quirk for Lenovo Ideapad S740 In-Reply-To: References: <20210416081211.20059-1-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: alsa-devel@alsa-project.org, Kailang Yang , Ryan Prescott X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 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: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Fri, 16 Apr 2021 18:05:17 +0200, Pierre-Louis Bossart wrote: > > > > On 4/16/21 3:47 AM, Jaroslav Kysela wrote: > > Dne 16. 04. 21 v 10:12 Takashi Iwai napsal(a): > >> Lenovo Ideapad S740 requires quite a few COEF setups to make its > >> speakers working. The verb table was provided from Ryan Prescott as > >> the result of investigation via qemu: > >> https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver > > > > [Cc: to Kailang / Realtek] > > > > I believe that this sequence contains I2C writes to amplifier chips. It would > > be really helpful, if Realtek can provide more information for the I2C master > > interface for their codecs (describe basic I2C I/O). > > The biggest problem is to figure what address/value pairs to write > with I2C into the amplifiers, and here the catch is that those I2C/I2S > amplifiers may or may not be sourced from Realtek, and it'd be > difficult for Realtek to provide documentation on their competition, > wouldn't it? Sure, that's another problem. But currently it's not clear even how to communicate via I2C/whatever to the underlying chip, as it's done via the vendor-specific COEF verb. At least this could be opened, I hope. Takashi