From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Cc: aford@beaconembedded.com, Adam Ford <aford173@gmail.com>,
Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
"Ariel D'Alessandro" <ariel.dalessandro@collabora.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Tim Harvey <tharvey@gateworks.com>
Subject: [PATCH 0/7] arm: dts: Create common imx8mn-u-boot
Date: Sun, 31 Jul 2022 18:45:50 -0500 [thread overview]
Message-ID: <20220731234557.602391-1-aford173@gmail.com> (raw)
Every imx8mn board has a bunch of similar entries on their
respective board-u-boot.dtsi file to make the board bootable.
Instead of maintaining multiple files with duplicate code,
have them all point to a new, common file. This file includes
the necessary nodes that were common to nearly all boards
and added spba1 to help faciliate SPL_DM_SERIAL. This also
adds support for CONFIG_FSPI_CONF_HEADER which can be used
to generate flash.bin files for booting from FlexSPI.
Adam Ford (7):
arm: dts: imx8mn-u-boot: Create common imx8mn-u-boot.dtsi
arm: dts: imx8mn-beacon-kit: Consolidate with imx8mn-u-boot
arm: dts: imx8mn-bsh-smm-s2: Consolidate with imx8mn-u-boot
arm: dts: imx8mn-ddr4-evk: Consolidate with imx8mn-u-boot
arm: dts: imx8mn-evk: Consolidate with imx8mn-u-boot
arm: dts: imx8mn-var-som-symphony: Consolidate with imx8mn-u-boot
arm: dts: imx8mn-venice: Consolidate with imx8mn-u-boot
arch/arm/dts/imx8mn-beacon-kit-u-boot.dtsi | 180 +------------
.../dts/imx8mn-bsh-smm-s2-u-boot-common.dtsi | 172 +-----------
arch/arm/dts/imx8mn-ddr4-evk-u-boot.dtsi | 180 +------------
arch/arm/dts/imx8mn-evk-u-boot.dtsi | 108 --------
arch/arm/dts/imx8mn-u-boot.dtsi | 248 ++++++++++++++++++
.../dts/imx8mn-var-som-symphony-u-boot.dtsi | 188 +------------
arch/arm/dts/imx8mn-venice-u-boot.dtsi | 188 +------------
7 files changed, 254 insertions(+), 1010 deletions(-)
create mode 100644 arch/arm/dts/imx8mn-u-boot.dtsi
--
2.34.1
next reply other threads:[~2022-07-31 23:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 23:45 Adam Ford [this message]
2022-07-31 23:45 ` [PATCH 1/7] arm: dts: imx8mn-u-boot: Create common imx8mn-u-boot.dtsi Adam Ford
2022-08-14 16:32 ` Adam Ford
2022-10-04 2:01 ` Fabio Estevam
2022-10-04 6:40 ` Michael Nazzareno Trimarchi
2022-07-31 23:45 ` [PATCH 2/7] arm: dts: imx8mn-beacon-kit: Consolidate with imx8mn-u-boot Adam Ford
2022-07-31 23:45 ` [PATCH 3/7] arm: dts: imx8mn-bsh-smm-s2: " Adam Ford
2022-07-31 23:45 ` [PATCH 4/7] arm: dts: imx8mn-ddr4-evk: " Adam Ford
2022-07-31 23:45 ` [PATCH 5/7] arm: dts: imx8mn-evk: " Adam Ford
2022-07-31 23:45 ` [PATCH 6/7] arm: dts: imx8mn-var-som-symphony: " Adam Ford
2022-07-31 23:45 ` [PATCH 7/7] arm: dts: imx8mn-venice: " Adam Ford
2022-08-04 17:15 ` [PATCH 0/7] arm: dts: Create common imx8mn-u-boot Tim Harvey
2022-08-14 22:56 ` Fabio Estevam
2022-08-15 11:43 ` Adam Ford
2022-09-11 16:36 ` Adam Ford
2022-10-21 12:10 ` Adam Ford
2022-10-21 12:13 ` Michael Nazzareno Trimarchi
2022-10-21 12:27 ` Stefano Babic
2022-10-21 12:28 ` Adam Ford
2022-10-24 10:30 ` Stefano Babic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220731234557.602391-1-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=ariel.dalessandro@collabora.com \
--cc=festevam@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=sbabic@denx.de \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox