From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pali =?utf-8?B?Um9ow6Fy?= Date: Sun, 6 Sep 2020 18:11:47 +0200 Subject: [PATCH 1/2] arm64: dts: armada-3720-espressobin: sync with downstream In-Reply-To: References: <20200831033408.467699-1-a.heider@gmail.com> <20200831075354.tzjbwdf37qh5r3rg@pali> <9d4f5101-d517-8298-7c51-c80259ac6f26@gmail.com> Message-ID: <20200906161147.uy4744dsub4hgsif@pali> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sunday 06 September 2020 17:03:29 Peter Robinson wrote: > The way U-Boot usually deals with this is syncs as much of the Linux > ones as possible and if there's bits not in the Linux one that's > needed to make/keep U-Boot working they add it in a XXX-u-boot.dtsi > file. There's a number of examples in the arch/arm/dts directory. Hello Peter! The main issue is that U-Boot has different comphy driver as Linux kernel and these two different implementations also needs different DTS files. Marek is working on patches to replace U-Boot comphy driver from Linux and then U-Boot will also use comphy DTS definitions from Linux. I think it does not make sense to spend time on thinking and implementing how to semi-synchronize DTS files from kernel as after comphy U-Boot driver changes, DTS files would be again changed.