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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 858D3C3DA59 for ; Mon, 15 Jul 2024 14:03:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:CC:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=DUKogu1jQnOGI+yRt7sMIp8u112mzxlrLc4tGaMpla8=; b=WdUC8ydouHpCTE6lrD8ESNRaPG dqN6NF1GbpkE5oOuawEpxw7RuiA16yXziNDNJQtaSYKaouX7l2fCOfEIoRlZoXxxMx6S3x6UZByAM dm+NAeHNfSee8LWdqSiKWbA0CqMnM8z3rJAaXaQLcnjfnhCQI++6D4Iql+gWJttkO9Ur2TaIwkFA6 WU8TVUeeAFKlPN6w5txdyS9ZmXHUZfSv2Y2/n0tByqtaDbIZdnL0ZC9tQihdKP0qdn27qVlJCFazY ZdUpsWiKMvNCJNgyAA+DN9Q7EBX3g6ee0Y9vQ32IemJjXk/Ecpn9cf2Me+fAFxhZ2+qpB/ud89H9o 4xS6BfGw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sTMIT-00000007JKg-0n3h; Mon, 15 Jul 2024 14:03:21 +0000 Received: from fllv0015.ext.ti.com ([198.47.19.141]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sTMHz-00000007JEY-2Hps for linux-arm-kernel@lists.infradead.org; Mon, 15 Jul 2024 14:03:03 +0000 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 46FE2d9K053380; Mon, 15 Jul 2024 09:02:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1721052159; bh=DUKogu1jQnOGI+yRt7sMIp8u112mzxlrLc4tGaMpla8=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=ZskHtPJ6PnRo0A1eD261cw2/H3NsAVCy1+mlnZ+Yl2KGdOaEZUixbFx5Q+gab+CUb DGU4YbRQ+LFzAwG+pZvvFWs/Odl6lScql6Mc3SeIj0lnpewXvx6pl5kLqDd032691a BM+tHcdp99dDqBLVZnAFYdITz3BmIi0Jt5HYNDsU= Received: from DLEE107.ent.ti.com (dlee107.ent.ti.com [157.170.170.37]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 46FE2dx1018610 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 15 Jul 2024 09:02:39 -0500 Received: from DLEE110.ent.ti.com (157.170.170.21) by DLEE107.ent.ti.com (157.170.170.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Mon, 15 Jul 2024 09:02:39 -0500 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DLEE110.ent.ti.com (157.170.170.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Mon, 15 Jul 2024 09:02:39 -0500 Received: from [128.247.75.151] (ula0511493.dhcp.ti.com [128.247.75.151]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 46FE2chG118703; Mon, 15 Jul 2024 09:02:38 -0500 Message-ID: <458e6141-abed-4301-ae76-c242c903ef61@ti.com> Date: Mon, 15 Jul 2024 09:02:38 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree To: Francesco Dolcini CC: Krzysztof Kozlowski , Bryan Brattlof , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Rob Herring , Krzysztof Kozlowski , , , References: <20220321155417.13267-1-bb@ti.com> <55e161d1-face-6958-1d86-8a85b82e8485@kernel.org> <766dceb1-222a-401b-95e3-69b7fb331411@ti.com> <20240710073811.GA4855@francesco-nb> Content-Language: en-US From: Logan Bristol In-Reply-To: <20240710073811.GA4855@francesco-nb> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240715_070251_877343_B21857EE X-CRM114-Status: GOOD ( 18.41 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello Francesco, On 7/10/24 02:38, Francesco Dolcini wrote: > Hello Logan > > On Tue, Jul 09, 2024 at 11:20:24AM -0500, Logan Bristol wrote: >> On 3/22/22 13:14, Krzysztof Kozlowski wrote: >>> On 21/03/2022 16:54, Bryan Brattlof wrote: >>>> Texas Instrument's am642 is one of many k3 based, low cost, low power, >>>> chips designed to work in a wide range of applications spanning an even >>>> wider range of industries that TI is actively developing >>>> >>>> With its pin-mux and peripheral rich designs, these chips will likely >>>> have a multitude of custom device trees that range wildly from one >>>> another and (hopefully) guarantee an influx of variants into the kernel >>>> in the coming years >>>> >>>> With overlays no longer a thing, I wanted to ask for opinions on how >>>> we can best help integrate these dt files as they begin to be developed >>>> >>>> I also wanted to introduce a skeletonized (nothing but uart) device tree >>>> to give others a good starting point while developing their projects. >>> >>> Real hardware as DTS please. There is no need to add some skeleton for >>> specific SoC. What if every SoC goes that way? >>> >>> Feel free to create re-usable components in DTSI ways, still reflecting >>> some hardware parts. >>> >> >> I am working on a project for the AM62 and came across this email thread. >> >> Following Krzysztof's direction, I am wanting to submit a DTSI to serve >> as a minimal configuration for the existing boards based on the AM62 >> SoC, which are currently defined by bloated DTS files. >> >> This DTSI file can be consumed by other board DTS files to reduce the >> configuration. Krzysztof, could this be merged upstream? > > Can you elaborate a little bit what you meant as bloated dts file? Why > would you need different DTSI files compared to the existing one? > Which problem are you trying to solve (make some example, be specific > please). > > My experience with verdin am62 (k3-am62-verdin*dts*) was pretty smooth, > I was just able to use the SOC dtsi file and use it to define my own > board (and I had the same good experience with other SOC/Vendors). > > Francesco > The resulting DTB after compiling AM62 SoC DTSI files initializes a large number of devices. A DTSI that initializes a minimal configuration that is immediately functional across SoC variations could be used on existing boards for test and debug purposes to isolate root cause of failure. It could also serve as a minimal configuration for board bringup. Thanks, Logan Bristol