public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: sbabic@denx.de
Cc: oliver.graute@kococonnector.com, u-boot@lists.denx.de,
	Fabio Estevam <festevam@denx.de>
Subject: [PATCH] imx8qm-cgtqmx8: Introduce imx8qm-cgtqmx8-u-boot.dtsi
Date: Sat, 22 Oct 2022 08:52:27 -0300	[thread overview]
Message-ID: <20221022115227.2149043-1-festevam@gmail.com> (raw)

From: Fabio Estevam <festevam@denx.de>

Since commit 02682bf82568 ("imx: imx8qm: cgtqmx8: switch to binman")
the following build error is seen:

arch/arm/dts/.imx8qm-cgtqmx8.dtb.pre.tmp:15:10: fatal error: imx8qm-u-boot.dtsi: No such file or directory

This commit included "imx8qm-u-boot.dtsi", but this file does not exist.

Fix the problem by introducing the board specific imx8qm-cgtqmx8-u-boot.dtsi
instead.

Fixes: 02682bf82568 ("imx: imx8qm: cgtqmx8: switch to binman")
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
Oliver,

This applies against u-boot-imx master-next branch:
https://source.denx.de/u-boot/custodians/u-boot-imx/-/commits/master-next

I don't have access to this board, so I cannot test it.

I just tested that it builds fine now.

 arch/arm/dts/imx8qm-cgtqmx8-u-boot.dtsi | 164 ++++++++++++++++++++++++
 arch/arm/dts/imx8qm-cgtqmx8.dts         |   2 +-
 2 files changed, 165 insertions(+), 1 deletion(-)
 create mode 100644 arch/arm/dts/imx8qm-cgtqmx8-u-boot.dtsi

diff --git a/arch/arm/dts/imx8qm-cgtqmx8-u-boot.dtsi b/arch/arm/dts/imx8qm-cgtqmx8-u-boot.dtsi
new file mode 100644
index 000000000000..756762d6c7f5
--- /dev/null
+++ b/arch/arm/dts/imx8qm-cgtqmx8-u-boot.dtsi
@@ -0,0 +1,164 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright 2018, 2021 NXP
+ */
+
+&{/imx8qm-pm} {
+
+	u-boot,dm-spl;
+};
+
+&mu {
+	u-boot,dm-spl;
+};
+
+&clk {
+	u-boot,dm-spl;
+};
+
+&iomuxc {
+	u-boot,dm-spl;
+};
+
+&pd_lsio {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio0 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio1 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio2 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio3 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio4 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio5 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio6 {
+	u-boot,dm-spl;
+};
+
+&pd_lsio_gpio7 {
+	u-boot,dm-spl;
+};
+
+&pd_conn {
+	u-boot,dm-spl;
+};
+
+&pd_conn_sdch0 {
+	u-boot,dm-spl;
+};
+
+&pd_conn_sdch1 {
+	u-boot,dm-spl;
+};
+
+&pd_conn_sdch2 {
+	u-boot,dm-spl;
+};
+
+&pd_dma {
+	u-boot,dm-spl;
+};
+
+&pd_dma_lpuart0 {
+	u-boot,dm-spl;
+};
+
+&pd_caam {
+	u-boot,dm-spl;
+};
+
+&pd_caam_jr1 {
+	u-boot,dm-spl;
+};
+
+&pd_caam_jr2 {
+	u-boot,dm-spl;
+};
+
+&pd_caam_jr3 {
+	u-boot,dm-spl;
+};
+
+&gpio0 {
+	u-boot,dm-spl;
+};
+
+&gpio1 {
+	u-boot,dm-spl;
+};
+
+&gpio2 {
+	u-boot,dm-spl;
+};
+
+&gpio3 {
+	u-boot,dm-spl;
+};
+
+&gpio4 {
+	u-boot,dm-spl;
+};
+
+&gpio5 {
+	u-boot,dm-spl;
+};
+
+&gpio6 {
+	u-boot,dm-spl;
+};
+
+&gpio7 {
+	u-boot,dm-spl;
+};
+
+&lpuart0 {
+	u-boot,dm-spl;
+};
+
+&usdhc1 {
+	u-boot,dm-spl;
+	mmc-hs400-1_8v;
+};
+
+&usdhc2 {
+	u-boot,dm-spl;
+	sd-uhs-sdr104;
+	sd-uhs-ddr50;
+};
+
+&usdhc3 {
+	u-boot,dm-spl;
+};
+
+&crypto {
+	u-boot,dm-spl;
+};
+
+&sec_jr1 {
+	u-boot,dm-spl;
+};
+
+&sec_jr2 {
+	u-boot,dm-spl;
+};
+
+&sec_jr3 {
+	u-boot,dm-spl;
+};
diff --git a/arch/arm/dts/imx8qm-cgtqmx8.dts b/arch/arm/dts/imx8qm-cgtqmx8.dts
index 919d00644ff3..26e435dc96a7 100644
--- a/arch/arm/dts/imx8qm-cgtqmx8.dts
+++ b/arch/arm/dts/imx8qm-cgtqmx8.dts
@@ -12,7 +12,7 @@
 /memreserve/ 0x80000000 0x00020000;
 
 #include "fsl-imx8qm.dtsi"
-#include "imx8qm-u-boot.dtsi"
+#include "imx8qm-cgtqmx8-u-boot.dtsi"
 
 / {
 	model = "Congatec QMX8 Qseven series";
-- 
2.25.1


                 reply	other threads:[~2022-10-22 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221022115227.2149043-1-festevam@gmail.com \
    --to=festevam@gmail.com \
    --cc=festevam@denx.de \
    --cc=oliver.graute@kococonnector.com \
    --cc=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /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