public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Adam Ford <aford173@gmail.com>
To: u-boot@lists.denx.de
Cc: Adam Ford <aford173@gmail.com>, Fabio Estevam <festevam@denx.de>,
	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 V2 0/7] arm: dts: Create common imx8mn-u-boot
Date: Fri, 21 Oct 2022 19:58:30 -0500	[thread overview]
Message-ID: <20221022005837.170357-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

For the series:

Reviewed-by: Fabio Estevam <festevam@denx.de>


 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      | 188 +------------
 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        | 196 +-------------
 7 files changed, 254 insertions(+), 1026 deletions(-)
 create mode 100644 arch/arm/dts/imx8mn-u-boot.dtsi

-- 
2.34.1


             reply	other threads:[~2022-10-22  0:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22  0:58 Adam Ford [this message]
2022-10-22  0:58 ` [PATCH V2 1/7] arm: dts: imx8mn-u-boot: Create common imx8mn-u-boot.dtsi Adam Ford
2022-10-24 13:56   ` sbabic
2022-10-22  0:58 ` [PATCH V2 2/7] arm: dts: imx8mn-beacon-kit: Consolidate with imx8mn-u-boot Adam Ford
2022-10-24 13:55   ` sbabic
2022-10-22  0:58 ` [PATCH V2 3/7] arm: dts: imx8mn-bsh-smm-s2: " Adam Ford
2022-10-24 13:55   ` sbabic
2022-10-22  0:58 ` [PATCH V2 4/7] arm: dts: imx8mn-ddr4-evk: " Adam Ford
2022-10-24 13:55   ` sbabic
2022-10-22  0:58 ` [PATCH V2 5/7] arm: dts: imx8mn-evk: " Adam Ford
2022-10-24 13:54   ` sbabic
2022-10-22  0:58 ` [PATCH V2 6/7] arm: dts: imx8mn-var-som-symphony: " Adam Ford
2022-10-24 13:54   ` sbabic
2022-10-22  0:58 ` [PATCH V2 7/7] arm: dts: imx8mn-venice: " Adam Ford
2022-10-24 13:56   ` sbabic

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=20221022005837.170357-1-aford173@gmail.com \
    --to=aford173@gmail.com \
    --cc=ariel.dalessandro@collabora.com \
    --cc=festevam@denx.de \
    --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