Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp591286pxx; Thu, 29 Oct 2020 09:37:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzWl0Iy28jAxvH/wSw0uV+jJsx6fiB0vw/JWQntM5TUVqEVWVtUIXeLfV2g0whfybDryMxD X-Received: by 2002:a50:bb25:: with SMTP id y34mr2693597ede.249.1603989459863; Thu, 29 Oct 2020 09:37:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603989459; cv=none; d=google.com; s=arc-20160816; b=nFPA76AqIY2zAuaQupBRGgjG2cm7/URC7NP70mfDOkxWxW31EwNhUlPgCkdt7iXg8Z mAd77vU8Ur2dLZ/e1Wvl/XsLGzpfp/M7WWg7GrMM9tR89X4JnKq8GO9p2seMVH+DE10C TGerrw2GHc43bgB3Ysvjs1X/fjLzLMOSlc+m2t9Yp/+XHzEbI7okWIq/qxJmq+MGCPko gd7OjWXkkk9ErMX+iQis3V48djSwgofWV9WhG13qUrbBD8zGE4PgKdJWQV89HaP+XKX5 l23j/dBW3+5U+nt/Cy0ozCfu97lAYYzKytvH6kIBMXZIutIL65Ngirdlkr5mMfUl/4Gk XUfg== 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; bh=XJo7ir+kAdb/unjehiA6alhtd6Dhstz9IsQMk1kcBLc=; b=iSMHd5iVnqMOHhWsK21clya4wZHmuuGEtfVBQvScZQrzxUUVXiRBG9af8cfNRG9k13 2frxvlAXqOHk9yzNOTm5HscXv6Ii6gUp7AXZdJY2jlcYd4z4vH2QJyfrQLX/zSQWN6Go EX+UagesaWXlMZiinUwx+Xu+1EdAIzlZF4bBnXUV9N9b5SZBYvUt33NS5SBuZs8VHvJV GMUZJXCXslwSZFl/iBScSP30Vk798uyOMrT5wj9UFjA2b2d/4AzFgnFSYvcCUHGf1HiA jdtP/nE/ao4fUE0dknTf8nZDd6qGBOvFee0LkEpPjDsmBaJLX6cL++GpTyDhyNmOqBPS dT8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r10si2042935ejx.127.2020.10.29.09.37.15; Thu, 29 Oct 2020 09:37:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726719AbgJ2Qft (ORCPT + 99 others); Thu, 29 Oct 2020 12:35:49 -0400 Received: from smtp1.de.adit-jv.com ([93.241.18.167]:47532 "EHLO smtp1.de.adit-jv.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbgJ2QeS (ORCPT ); Thu, 29 Oct 2020 12:34:18 -0400 Received: from localhost (smtp1.de.adit-jv.com [127.0.0.1]) by smtp1.de.adit-jv.com (Postfix) with ESMTP id 22C2D3C0588; Thu, 29 Oct 2020 17:34:15 +0100 (CET) Received: from smtp1.de.adit-jv.com ([127.0.0.1]) by localhost (smtp1.de.adit-jv.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KF1LO2lg9uMQ; Thu, 29 Oct 2020 17:34:09 +0100 (CET) Received: from HI2EXCH01.adit-jv.com (hi2exch01.adit-jv.com [10.72.92.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp1.de.adit-jv.com (Postfix) with ESMTPS id D97B93C009C; Thu, 29 Oct 2020 17:32:20 +0100 (CET) Received: from lxhi-065.adit-jv.com (10.72.94.11) by HI2EXCH01.adit-jv.com (10.72.92.24) with Microsoft SMTP Server (TLS) id 14.3.487.0; Thu, 29 Oct 2020 17:32:20 +0100 Date: Thu, 29 Oct 2020 17:32:13 +0100 From: Eugeniu Rosca To: Geert Uytterhoeven CC: Linux-Renesas , Magnus Damm , Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Kernel Mailing List , Steffen Pengel , Eugeniu Rosca , Eugeniu Rosca Subject: Re: [PATCH 2/2] arm64: dts: renesas: r8a77961: ulcb-kf: Initial device tree Message-ID: <20201029163213.GA12422@lxhi-065.adit-jv.com> References: <20201029133741.25721-1-erosca@de.adit-jv.com> <20201029133741.25721-2-erosca@de.adit-jv.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: X-Originating-IP: [10.72.94.11] Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, On Thu, Oct 29, 2020 at 03:09:10PM +0100, Geert Uytterhoeven wrote: > On Thu, Oct 29, 2020 at 2:38 PM Eugeniu Rosca wrote: > > Create a dedicated DTB for M3-ES3.0 + ULCB + Kingfisher combo. > > Inspire from the pre-existing ULCB-KF device trees: > > > > $ ls -1 arch/arm64/boot/dts/renesas/*ulcb-kf.dts > > arch/arm64/boot/dts/renesas/r8a77950-ulcb-kf.dts > > arch/arm64/boot/dts/renesas/r8a77951-ulcb-kf.dts > > arch/arm64/boot/dts/renesas/r8a77960-ulcb-kf.dts > > arch/arm64/boot/dts/renesas/r8a77965-ulcb-kf.dts > > > > Signed-off-by: Eugeniu Rosca > > Reviewed-by: Geert Uytterhoeven > i.e. will queue in renesas-devel for v5.11. Thank you for the prompt review! > > + compatible = "shimafuji,kingfisher", "renesas,m3ulcb", > > + "renesas,r8a77961"; > > Can you please send a patch to add this combo to > Documentation/devicetree/bindings/arm/renesas.yaml? I would happily do so if you resolve below concerns. Since the inception of the Kingfisher extension board description in v4.15-rc1 commit 5418a900412699 ("arm: shmobile: Document Kingfisher board DT bindings"), nobody attempted describing the SoC+ULCB+KF combinations in spite of four of such DT configurations being actively used and maintained, i.e. r8a779{50,51,60,65}-ulcb-kf. So, if we start documenting the r8a77961-ulcb-kf combo as a board, this raises below questions: => should the missing 4 SoC+ULCB+KF instances be documented as well? => should a new compatible string be created for each such HW combo, e.g. "renesas,-ulcb-kf"? I feel none of the above is really needed, based on the patterns established in Documentation/devicetree/bindings/arm/renesas.yaml, but I might be wrong. Thoughts/suggestions appreciated. IMHO one thing which is certainly worth clarifying and fixing is the KF revision currently documented in renesas.yaml, i.e. M03. Shimafuji released at least M04, M05 and M06 revisions of KF (nicely compared at https://elinux.org/R-Car/Boards/Kingfisher#Change_point). The question is, does the community intend to support M03 through M06 (in which case all of them might need an entry in the documentation) or anything which is earlier than M06 has to be considered deprecated (in which case renesas.yaml would need a simple s/M03/M06/ update)? -- Best regards, Eugeniu Rosca