linux-kernel - Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240715145503.GA32273@francesco-nb>
Date: Mon, 15 Jul 2024 16:55:03 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Logan Bristol <l-bristol@...com>
Cc: Francesco Dolcini <francesco@...cini.it>,
	Krzysztof Kozlowski <krzk@...nel.org>, Bryan Brattlof <bb@...com>,
	Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>,
	Tero Kristo <kristo@...nel.org>, Rob Herring <robh+dt@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] arm64: dts: ti: introduce a minimal am642 device tree

On Mon, Jul 15, 2024 at 09:02:38AM -0500, Logan Bristol wrote:
> 
> 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).
> > 
> 
> The resulting DTB after compiling AM62 SoC DTSI files initializes a
> large number of devices.

I do not understand the issue. The SOC dtsi enables (or should enable) only
IP that are self contained within the SOC, everything else is disabled.

If you need something like that it means you are debugging the silicon,
am I wrong?

Francesco