Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp8209050rwr; Wed, 10 May 2023 20:29:15 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ58s6JpQbBCLJ/Q+zKJ5s6TW8y7XU0Y6GMmJGXDIxZorJNV3nLxTyK0a91phnTjkja4s1FK X-Received: by 2002:a17:903:2292:b0:1a2:3108:5cc9 with SMTP id b18-20020a170903229200b001a231085cc9mr27169529plh.40.1683775755521; Wed, 10 May 2023 20:29:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683775755; cv=none; d=google.com; s=arc-20160816; b=LMdaNCTTd1AByyXNTndPR3kybTRqoOPV4CTrTSVamg7O62hhc9V3lQt+vmWgcYFCHB U0+jcTICpKwsANf5geSE21JOTB7ojI5fCDky5WfjYOgOcr22i15/BQPwKuizP+zi+yBs bNSr+KUJhFBGMYQwdTHW28Vbhrv2Mz0ME1BkRTl3/lbmyIkqqrcltAoL1Vlh8/lAzjdC 4u0KRf/YaiEaJaSuOWJUushWlWAPTKM0Oqecv7nBUOwKt2oi1+7mL7Ck4/gN3Sr8PPbU NWAm2WefATVyaAQLRsIVGSKxhg86l1BtRwyFjVqo4gPyqizwIV7V9LoGyKCrQC52Exho mNmQ== 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; bh=rk+62qPlFabfZnLDuO2ZQAkcXkKZNRYueascWtHbHac=; b=yUIvj/DdPQsDs6MuGzwo+QfdR8lLZUB5qfRWR+AuNwouidRp84uDWoQ57QZkJlTryS c7Yv7rSKU9IUM5CtniiNhfzvDRMRCCmOWNXMJktHXmbXoQR/7yRus6NjrFqF97L6Lwz6 oaaIUElbsYELJYuc0e8CFFWuuB8J4a74KyftnDeCbvQvUTtbowmdEpYVyw2V/YhiG89s QZgJyWeAPrXd00i10bBMDSxoLCXRfxYNzVOubK4QaazjO1RshMmr43OwygWdmiIJf9pf UPyYr7QE4oJbZjtxYmiMcG1z2JCgPlgCUzYNAhFD1Jt9FzBKSjQ6rrGw9aHzCC5Mww1Q h9rQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b18-20020a170902b61200b00198ff2d6543si5470284pls.117.2023.05.10.20.28.38; Wed, 10 May 2023 20:29:15 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235583AbjEKDVn (ORCPT + 99 others); Wed, 10 May 2023 23:21:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36016 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232261AbjEKDVl (ORCPT ); Wed, 10 May 2023 23:21:41 -0400 Received: from fd01.gateway.ufhost.com (fd01.gateway.ufhost.com [61.152.239.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 97CA81719; Wed, 10 May 2023 20:21:35 -0700 (PDT) Received: from EXMBX166.cuchost.com (unknown [175.102.18.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "EXMBX166", Issuer "EXMBX166" (not verified)) by fd01.gateway.ufhost.com (Postfix) with ESMTP id EB91682D4; Thu, 11 May 2023 11:21:33 +0800 (CST) Received: from EXMBX168.cuchost.com (172.16.6.78) by EXMBX166.cuchost.com (172.16.6.76) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 11 May 2023 11:21:34 +0800 Received: from [192.168.125.124] (113.72.146.187) by EXMBX168.cuchost.com (172.16.6.78) with Microsoft SMTP Server (TLS) id 15.0.1497.42; Thu, 11 May 2023 11:21:33 +0800 Message-ID: Date: Thu, 11 May 2023 11:21:32 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: [PATCH v3 3/3] riscv: dts: starfive: add tdm node and sound card To: Conor Dooley CC: Emil Renner Berthing , Mark Brown , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Rob Herring , Krzysztof Kozlowski , Conor Dooley , , , , References: <20230506090116.9206-1-walker.chen@starfivetech.com> <20230506090116.9206-4-walker.chen@starfivetech.com> <20230509-overheat-pliable-00d60523637e@spud> <20230510-riveter-ridden-3f056251e623@spud> Content-Language: en-US From: Walker Chen In-Reply-To: <20230510-riveter-ridden-3f056251e623@spud> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [113.72.146.187] X-ClientProxiedBy: EXCAS064.cuchost.com (172.16.6.24) To EXMBX168.cuchost.com (172.16.6.78) X-YovoleRuleAgent: yovoleflag X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,NICE_REPLY_A, SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 On 2023/5/11 4:22, Conor Dooley wrote: > On Wed, May 10, 2023 at 05:21:21PM +0800, Walker Chen wrote: >> On 2023/5/10 16:33, Emil Renner Berthing wrote: >> > On Tue, 9 May 2023 at 20:05, Conor Dooley wrote: >> >> >> >> On Tue, May 09, 2023 at 08:52:48PM +0800, Walker Chen wrote: >> >> > Hi Conor/Emil, >> >> > >> >> > DT overlay is used to describe combinations of VF2 and hat. >> >> > Do you have any comments on this patch ? >> >> >> >> I seem to recall that he said at the linux-riscv sync-up call that we >> >> have* that he was not in favour of overlays for hats like this. >> >> I'll let him confirm that though, I might very well be misinterpreting or >> >> misremembering what he said. >> > >> > What probably meant was that I didn't want a bunch of different device >> > trees for each combination board * hat. An overlay makes a lot more >> > sense. However, looking through the kernel tree there is a surprising >> > lack of overlays for hats committed already, so I suspect there is >> > some sort of policy around overlays already in place. > >> About the specific usage of overlay for this board + hat, referenced to the following example in kernel: >> linux/arch/arm64/boot/dts/freescale/imx8mm-venice-gw73xx-0x-imx219.dtso >> That board is connected with imx219 sensor via mipi_csi interface. That patch was accepted in 2022. > > Hmm, so spoke to Emil again today about it. In the interest of being > fair, I did go looking at that particular board & looked through their > documentation for more information on why there are overlays. > They do actually sell the bits required to use the overlays, based on > what I saw in their datasheet for the board & wiki. That said, what is > done for one arm64 platform does not necessarily apply elsewhere ;) > > I'm not against allowing in-tree overlays for hats/capes/daughter-boards > that come bundled with a board, but accepting ones for a hat that > someone decided to use theoretically has no limit! The "someone" in this > case might be a StarFive developer, but it could be any random one of > your customers next! > We've got to draw a line somewhere, so my answer to the overlay *in this > case* is a no. Sorry. > When you submit your next version, please drop the overlay from this > patch. I'm trying to understand what you mean. so the conclusion is that I need to drop the file 'jh7110-starfive-visionfive-2-wm8960.dtso' from this patch. When I submit the next version, just keep the TDM node and the pins configuration for TDM in patch [3/3], need to drop the wm8960 stuff. Right ? Best regards, Walker