mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [RFC PATCH] ARM: dts: i.MX8MP: remove barebox environment handling
Date: Tue, 10 Feb 2026 23:13:40 +0100	[thread overview]
Message-ID: <20260210221343.3431882-1-m.felsch@pengutronix.de> (raw)

While specifying the barebox environment within the barebox dts is very
helpful for standalone barebox development it's difficult for BSPs which
use this development platform and want to use the GPT mechanism.
As a result BSPs had to manually delete the nodes via a external
provided dts, because we wanted to keep the comfort for the standalone
development flow.

Lucky commit 86531d4bf7aa ("commands: create createnv command")
introduced a convenient helper to create a barebox environemnt on
demand exactly for this purpose:

| "We want to move away from describing the barebox environment explicitly
| in the device tree and instead motivate usage of GPT partitions.."

So start with the i.MX8MP-EVK to encourage the use of GPT partitions and
to make the BSP integration for these development platforms easier.

Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
 arch/arm/dts/imx8mp-evk.dts | 43 -------------------------------------
 1 file changed, 43 deletions(-)

diff --git a/arch/arm/dts/imx8mp-evk.dts b/arch/arm/dts/imx8mp-evk.dts
index e6f8c2d1b482..37798fa99efa 100644
--- a/arch/arm/dts/imx8mp-evk.dts
+++ b/arch/arm/dts/imx8mp-evk.dts
@@ -12,19 +12,6 @@
 / {
 	barebox,deep-probe;
 
-	chosen {
-		environment-sd {
-			compatible = "barebox,environment";
-			device-path = &env_sd2;
-			status = "disabled";
-		};
-		environment-emmc {
-			compatible = "barebox,environment";
-			device-path = &env_sd3;
-			status = "disabled";
-		};
-	};
-
 	gpio-leds {
 		status {
 			barebox,default-trigger = "heartbeat";
@@ -78,33 +65,3 @@ &usb_dwc3_0 {
 	usb-role-switch;
 	status = "okay";
 };
-
-&usdhc2 {
-	#address-cells = <1>;
-	#size-cells = <1>;
-
-	partition@0 {
-		label = "barebox";
-		reg = <0x0 0xe0000>;
-	};
-
-	env_sd2: partition@e0000 {
-		label = "barebox-environment";
-		reg = <0xe0000 0x20000>;
-	};
-};
-
-&usdhc3 {
-	#address-cells = <1>;
-	#size-cells = <1>;
-
-	partition@0 {
-		label = "barebox";
-		reg = <0x0 0xe0000>;
-	};
-
-	env_sd3: partition@e0000 {
-		label = "barebox-environment";
-		reg = <0xe0000 0x20000>;
-	};
-};
-- 
2.47.3




             reply	other threads:[~2026-02-10 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 22:13 Marco Felsch [this message]
2026-02-11  7:53 ` Sascha Hauer
2026-02-11  9:37   ` Ahmad Fatoum
2026-02-11  9:58     ` Sascha Hauer
2026-02-11 10:14     ` Marco Felsch
2026-02-11 12:53       ` Sascha Hauer
2026-02-11 12:56         ` Ahmad Fatoum

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=20260210221343.3431882-1-m.felsch@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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