Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3904016rwb; Tue, 20 Sep 2022 06:24:29 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6XwF0rrA3huOsv+fYXtrJEctsNp3V0X8RiUXSvmEALcffispuNdSfJAT0MP/sRhnW70TrD X-Received: by 2002:a17:903:248:b0:172:7520:db04 with SMTP id j8-20020a170903024800b001727520db04mr4822316plh.99.1663680268869; Tue, 20 Sep 2022 06:24:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663680268; cv=none; d=google.com; s=arc-20160816; b=L6YUOHUzVVM40KZ1PDx8yoTsVhmeSG/kHmb3cigo82QEATkMGMQk+Pl5lRk8mCdJ0F tktp9gzZIqcaDHrSw9FEym76oEZ5FlL7zbbTxTO5LKmBslKpLgn7Hpi1sVpRmCdoaI91 uLuGWhJsFkJgUNw97lkiIbC4AZwKoMX6idmDZ6+hnwjbFd9nCMr66EJOM4tDfdH8ik0D 90RYmKl8ILM2Ei6/Qe9Mw4vbLBgPoW7agVMaH7l0Itmfa922S5em5k3v+iXhSSfMNzvZ PDTxDsPLOMreZA4DsaAgbosIwCPEiDI2dbhCKekMvkmhhC92aOj8j7OQP78Sz2GhJs/i 7R/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=uNyMq+8P7Zoo0GvejcbGzTW10QP0A0trZfakvvVZN88=; b=h0sI3w8/Y3pn9Asi8qiWbUssTkvUG+TorEM1j/SFxQhgD+ar7hZ0PJOGHW+WssfC8E 8/JQie88fRAWQPKc9TOtEqsh2IFdav7QU+6sFMsP3n5zcK25u9JbpNfsAU+ZvxI3ofWz zZQ0PY2+UaBC0vSm0oNKtGF++sIUaS191+iL81lS/x5GWcYblU4s37Vto4PIC0JJDAgj AMFplfWvghTmce02PzuD1QtsQ7OMduBZeJ9EcWFzGwvkhWd4xKbtMJlLZZ08x63G2fOP Ndlm7zyf+BsbWm65r1ptmSR62tRbmTTMyo/k+PwBazOyNw92QbJE/qFQ1ylnUFSqUoAk E2Dw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=CYVOcFtU; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i23-20020aa78d97000000b00542deddc4e0si1606859pfr.46.2022.09.20.06.24.15; Tue, 20 Sep 2022 06:24:28 -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; dkim=pass header.i=@microchip.com header.s=mchp header.b=CYVOcFtU; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229799AbiITMbc (ORCPT + 99 others); Tue, 20 Sep 2022 08:31:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229689AbiITMb3 (ORCPT ); Tue, 20 Sep 2022 08:31:29 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B1075AC40; Tue, 20 Sep 2022 05:31:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1663677088; x=1695213088; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=q/fZbisIvw+4RruEs9TBl1W84JkX1r956syzCxEZ1v4=; b=CYVOcFtUD8UCQuvmj4V/ueMclQN/0XcD7Q9NGdLRo/pLR4xaVvlsSg/c YZjYCRiGn9Bj40KJe2Z+YYTeaLzI0SYtTeWrRdfsOleWAFj/z7qenWDPT V62qdQ+GVv/O1gPcIx9CDDjLoUPCof//m0YEF0cxaQAqUeDNl7HQxV0Pr h2lerBbpM/jBbbIuGvPkvst7muR1epqP8Nsc0wHJ0Km+cNeEZ14f/UyAW 7hJW90ux0+EsbHGo74CmkQ85nirCf4Klg4xjGPv1bjYNipG1vs22v2XF6 36hxTr9nFOEKZC7bmEg+VGCy5hAyF+v73zihWmXmA/2WQLEy1W5nSPtWa g==; X-IronPort-AV: E=Sophos;i="5.93,330,1654585200"; d="scan'208";a="178026134" Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 20 Sep 2022 05:31:27 -0700 Received: from chn-vm-ex02.mchp-main.com (10.10.85.144) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12; Tue, 20 Sep 2022 05:31:26 -0700 Received: from wendy (10.10.115.15) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12 via Frontend Transport; Tue, 20 Sep 2022 05:31:24 -0700 Date: Tue, 20 Sep 2022 13:31:03 +0100 From: Conor Dooley To: Geert Uytterhoeven CC: Conor Dooley , "Lad, Prabhakar" , , , , , , , , , , , , , Subject: Re: [PATCH v3 07/10] riscv: boot: dts: r9a07g043: Add placeholder nodes Message-ID: References: <20220915181558.354737-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20220915181558.354737-8-prabhakar.mahadev-lad.rj@bp.renesas.com> <3693a3a1-5a2a-4cc5-fb55-f6ad9a4b3f72@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS 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 Tue, Sep 20, 2022 at 02:17:50PM +0200, Geert Uytterhoeven wrote: > Hi Conor, > > On Fri, Sep 16, 2022 at 12:40 AM Conor Dooley wrote: > > On 15/09/2022 23:26, Lad, Prabhakar wrote: > > > On Thu, Sep 15, 2022 at 10:36 PM wrote: > > >> On 15/09/2022 19:15, Prabhakar wrote: > > >>> riscv: boot: dts: r9a07g043: Add placeholder nodes > > >>> From: Lad Prabhakar > > >>> Add empty placeholder nodes to RZ/Five (R9A07G043) SoC DTSI. > > >> Can you explain why do you need placeholder nodes for this and > > >> cannot just directly include the other dtsis? > > >> > > > Since the RZ/G2UL SoC is ARM64 where it has a GIC and on RZ/Five SoC > > > we have PLIC for interrupts. Also the interrupt numbering for RZ/Five > > > SoC differs from RZ/G2UL SoC hence we are not directly using the > > > RZ/G2UL SoC DTSI [0]. > > > > > > [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/renesas/r9a07g043.dtsi?h=v6.0-rc5 > > > > > > For the RZ/Five SMARC EVK I am re-using the below files [1] (SoM) and > > > [2] (Carrier board) as the RZ/Five SMARC EVK is pin compatible. Since > > > I am re-using these when trying to compile the RZ/Five DTB I get > > > compilation errors since the nodes dont exist (and there is no way > > > currently we can delete the node reference when the actual node itself > > > isn't present) hence these place holders. > > > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/renesas/rzg2ul-smarc-som.dtsi?h=v6.0-rc5 > > > [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/renesas/rzg2ul-smarc.dtsi?h=v6.0-rc5 > > > > If this method is acceptable to Geert, this explanation 100% needs to > > go into the commit message. > > We've been using these placeholders a lot in Renesas SoC-specific > .dtsi files, as they allow us to introduce gradually support for a new SoC > that is mounted on an existing PCB, and thus shares a board-specific > .dtsi file. Hence I'm fine with this. Aye, if you're happy with it then I am too... > > However, I think more properties can be dropped from the placeholders. > There is no need to have e.g. 'reg-names' and 'status = "disabled"' > (there is no compatible value, so no matching is done). ...and this makes a lot of sense. I'd still like a comment in the commit message though explaining why placeholder nodes are needed as opposed to just leaving it blank etc. Thanks, Conor.