From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 13 Apr 2021 13:47:46 -0400 Subject: [PATCH 10/13] ARM: dts: synquacer: Add device trees for DeveloperBox In-Reply-To: <161832781487.562320.49203469390042692.stgit@localhost> References: <161832714362.562320.8024090839631691588.stgit@localhost> <161832781487.562320.49203469390042692.stgit@localhost> Message-ID: <20210413174746.GS1310@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Apr 14, 2021 at 12:30:15AM +0900, Masami Hiramatsu wrote: > Add device trees for 96boards EE DeveloperBox and basement SynQuacer > SoC dtsi. These files are imported from EDK2 with cosmetic change > and modified for accessing SPI NOR flash. > > Signed-off-by: Masami Hiramatsu > --- > arch/arm/dts/DeveloperBox.dts | 146 +++++++++ > arch/arm/dts/Makefile | 2 > arch/arm/dts/SynQuacer.dtsi | 590 +++++++++++++++++++++++++++++++++++++ > arch/arm/dts/SynQuacerCaches.dtsi | 72 +++++ This poses a bit of a naming challenge. I assume, but please correct me if I'm wrong, that you don't intend to push these dts files to the Linux kernel. So that means EDK2 is the primary source of the files, yes? We want to keep them as-is from the upstream project, and note that relevant git hash/tag/etc that matches where we pulled from, to make future syncs easier, in the commit message. I assume this is not part of the uniphier family, so we should start by naming these as arch/arm/dts/synquacer-... to fit with the general scheme. Perhaps -developerbox, -core and -caches ? And for any changes we do need, they go in a -u-boot.dtsi file and then potentially automatically included (if it fits in the logic we have today for that) or specifically #included otherwise. Thanks. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: