Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp3110078rwb; Fri, 9 Dec 2022 10:04:28 -0800 (PST) X-Google-Smtp-Source: AA0mqf6DNdFW3mbz1VyTM4q0lmFi7enpYPrq7Q4pQLFq01pq7pPrJNNZi4ImA3E71s/O/N+UffwW X-Received: by 2002:a05:6402:d:b0:45c:835b:8fa5 with SMTP id d13-20020a056402000d00b0045c835b8fa5mr5635648edu.16.1670609067809; Fri, 09 Dec 2022 10:04:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670609067; cv=none; d=google.com; s=arc-20160816; b=a1lRezk8qJZ/ZyVMZn1pbxD68xqmXehl8ZUTLWcr24xod3Lm3qVS4A6K6Cs2u9ooSS RlE8/++SxBZ/bWgwdZ5Rkcqht1fGkEM8D0t+yjNAwZIIvp/Sag6VUPwD/A4ZaMY0yaiS WbH8ZNXb0U0753aGELzprVlFDx0skeHvXypscnDJs2D04pPsw4/eFzHinLkyyGJs/DPT zsHh6vShqWMEuofXOLCR2TElQwzyqSLb/k0sFRMVYOOma8QFa1/aq2T9kiBPONRK1BKX zO2ljNiArNxY6nxu3tfdzLBMiuJr4r0rwD7ILJcP1dzqVz3TYViU6+PLqRhqIlwGvAXr sUXw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=Y+sfUqLOI+/eXjVwHk2FNz/lVH3gwLN+vN8n6apWcUI=; b=SMN7QM0AGKAuMEnyEJ/HtRy3AEPcH1fVbE/PCgQtWPTDGQzI8atArSfsFdCOexiKzo D1fOFniuIZQNnMGk7l2toIsCb2YN/AZw1eFEZt/Oeq1efZ/Zyd4jt6V87zk68kl8NiO6 HAGY6768EjGMRGTQuq6tHZyZFbtKpLpt3SITUKUVl7KvPJOc08ImQ0ZOlPQn30zIlt9S BKy1PKW0qkwaRibNxEk/1A9oxVguXiELKV45Mxf8hR8A2AjPNBv09LzyukCVcoenEcZI AUdHl9mg7RVtwvOh9aBmCyQvB2jecZ+1Gzo07mPBn1IjuMgIjle9D0eKtnndX2FFoac4 QHWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=aK4aLT8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u24-20020a50d518000000b0046b5f80f128si1834016edi.193.2022.12.09.10.04.07; Fri, 09 Dec 2022 10:04:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=aK4aLT8f; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229661AbiLIRb3 (ORCPT + 75 others); Fri, 9 Dec 2022 12:31:29 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229478AbiLIRb2 (ORCPT ); Fri, 9 Dec 2022 12:31:28 -0500 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4C5A115709 for ; Fri, 9 Dec 2022 09:31:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670607087; x=1702143087; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=6gaByd85Ir5jpC5TjpFdxoKpv9W8N2P7lwLZnGk0xEw=; b=aK4aLT8f04EgmqTPTsh1o2xVK8uuJ7rVcR4uBe8P+ful5SbfV6yyc2cS X3k2Jk0af1hrCzODoWfcgTXzM8rbuiZ795uKt3oY4rzzCC/GtsYDB1CS9 46jh5e8FBIx23iQP5lMvi1dfDL1GQbB0tba22bqIRXKb+BwYUtBhmaWUC 536AAnj/JYmMQhh2NAT9aRAE4rtjrBp/fkiMqmGKzoqt7Hj1qqVJbY8CR LOfRUZhyUbjNA5scZkfqArXUJCdVvaPX4185iAxm8Roga6Gy+lMVSG3zw sX33TyyFyGTgycRMsdraZmJhMja+Ue94vF2BqOS1iLEbg373QNCx6MFx8 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10556"; a="316213601" X-IronPort-AV: E=Sophos;i="5.96,230,1665471600"; d="scan'208";a="316213601" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Dec 2022 09:31:26 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10556"; a="625180439" X-IronPort-AV: E=Sophos;i="5.96,230,1665471600"; d="scan'208";a="625180439" Received: from bdmeredi-mobl2.amr.corp.intel.com (HELO [10.212.15.195]) ([10.212.15.195]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Dec 2022 09:31:25 -0800 Message-ID: <22043956-e18c-9ed6-5091-188ae40f3cd9@linux.intel.com> Date: Fri, 9 Dec 2022 11:31:24 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.4.2 Subject: Re: [PATCH v1] ASoC: Intel: sof_nau8825: add support for nau8825 with amp nau8318 To: Ajye Huang Cc: Libin Yang , "balamurugan . c" , Cezary Rojewski , Kai Vehmanen , Bard Liao , Takashi Iwai , linux-kernel@vger.kernel.org, Liam Girdwood , Mark Brown , Muralidhar Reddy , Ranjani Sridharan , Akihiko Odaki , ye xingchen , David Lin , alsa-devel@alsa-project.org, Peter Ujfalusi , Brent Lu , Yong Zhi References: <20221209150503.11875-1-ajye_huang@compal.corp-partner.google.com> Content-Language: en-US From: Pierre-Louis Bossart In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> This looks inconsistent with the commit message. There are separate >> Kconfigs for different codecs. >> >> SND_SOC_NAU8315 >> SND_SOC_NAU8825 >> >> Which is it? >> > > Sorry about confusing you, I think it is better to change the title as > ASoC: Intel: sof_nau8825: add combination of nau8825 headset codec > with nau8318 Amp. Suggested edit: ASoC: Intel: sof_nau8825: add variant with nau8318 amplifier. > > And add some information about Nuvoton chips in the comment message. > *** > The nau8315 and nau8318 are both Nuvoton Amp chips. They use the same > Amp driver nau8315.c. The acpi_device_id for nau8315 is "NVTN2010", > for nau8318 is "NVTN2012". That should be added in the commit message please. >> NAK for this v1. Please clarify which codec you are using and make sure >> all references are consistent. >> >> > > I apologize for the unclear comment message, please give me any > suggestions if needed, and I will send v2 for review. > thanks. Ok, makes sense now. Please do include the explanations on 8315/8318 variants, I couldn't figure out what chips were used. I would also not use the same topology name as a different platform with another amplifier. I appreciate you trying to reuse when possible, but it's just better to create a new topology file. That way if you want any update down the road you can do so, it's more maintainable and risk-free.