From: Dario Binacchi <dario.binacchi@amarulasolutions•com>
To: linux-kernel@vger•kernel.org
Cc: domenico.acri@engicam•com, francesco.utel@engicam•com,
michael@amarulasolutions•com, linux-amarula@amarulasolutions•com,
Dario Binacchi <dario.binacchi@amarulasolutions•com>,
Alexandre Torgue <alexandre.torgue@foss•st.com>,
Conor Dooley <conor+dt@kernel•org>,
Krzysztof Kozlowski <krzk+dt@kernel•org>,
Maxime Coquelin <mcoquelin.stm32@gmail•com>,
Rob Herring <robh@kernel•org>,
devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
linux-stm32@st-md-mailman•stormreply.com
Subject: [PATCH v2 12/15] arm64: dts: st: support Engicam MicroGEA-STM32MP257 SoM
Date: Fri, 29 May 2026 16:46:26 +0200 [thread overview]
Message-ID: <20260529144707.3931919-13-dario.binacchi@amarulasolutions.com> (raw)
In-Reply-To: <20260529144707.3931919-1-dario.binacchi@amarulasolutions.com>
Support Engicam MicroGEA-STM32MP257 SoM with:
- 8 GB eMMC Flash
- 2 GB LPDDR4 DRAM
The SoM also provides an Ethernet MAC, but Ethernet support is not
enabled at this stage due to a known silicon limitation documented in
[1].
This corresponds to section 2.21.2 ("ETH1 RMII mode could have CRC
errors"), where CRC errors may occur in ETH1 RMII direct mode when
directly connected to I/Os.
The workaround requires use of the Ethernet switch (ETHSW), which
introduces additional DT bindings and topology complexity. This is
intended to be addressed in a separate patch series.
[1] https://www.st.com/resource/en/errata_sheet/es0598-stm32mp23xx25xx-device-errata-stmicroelectronics.pd
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions•com>
---
(no changes since v1)
.../dts/st/stm32mp257-engicam-microgea.dtsi | 64 +++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 arch/arm64/boot/dts/st/stm32mp257-engicam-microgea.dtsi
diff --git a/arch/arm64/boot/dts/st/stm32mp257-engicam-microgea.dtsi b/arch/arm64/boot/dts/st/stm32mp257-engicam-microgea.dtsi
new file mode 100644
index 000000000000..67be66cd1930
--- /dev/null
+++ b/arch/arm64/boot/dts/st/stm32mp257-engicam-microgea.dtsi
@@ -0,0 +1,64 @@
+// SPDX-License-Identifier: GPL-2.0
+/*
+ * Copyright (C) 2026 Amarula Solutions, Dario Binacchi <dario.binacchi@amarulasolutions•com>
+ * Copyright (C) 2026 Engicam srl
+ */
+
+/dts-v1/;
+
+#include <dt-bindings/regulator/st,stm32mp25-regulator.h>
+#include "stm32mp257.dtsi"
+#include "stm32mp25xf.dtsi"
+#include "stm32mp25-pinctrl.dtsi"
+#include "stm32mp25xxai-pinctrl.dtsi"
+
+/ {
+ model = "Engicam MicroGEA STM32MP257 SoM";
+ compatible = "engicam,microgea-stm32mp257", "st,stm32mp257";
+
+ memory@80000000 {
+ device_type = "memory";
+ reg = <0x0 0x80000000 0x0 0x80000000>;
+ };
+};
+
+&scmi_regu {
+ scmi_vddio1: regulator@0 {
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ };
+ scmi_vddcore: regulator@b {
+ reg = <VOLTD_SCMI_STPMIC2_BUCK2>;
+ regulator-name = "vddcore";
+ };
+ scmi_v1v8: regulator@e {
+ reg = <VOLTD_SCMI_STPMIC2_BUCK5>;
+ regulator-name = "v1v8";
+ };
+ scmi_v3v3: regulator@10 {
+ reg = <VOLTD_SCMI_STPMIC2_BUCK7>;
+ regulator-name = "v3v3";
+ };
+ scmi_vdd3v3_usb: regulator@14 {
+ reg = <VOLTD_SCMI_STPMIC2_LDO4>;
+ regulator-name = "vdd3v3_usb";
+ };
+};
+
+/* eMMC */
+&sdmmc2 {
+ pinctrl-names = "default", "opendrain", "sleep";
+ pinctrl-0 = <&sdmmc2_b4_pins_a &sdmmc2_d47_pins_a>;
+ pinctrl-1 = <&sdmmc2_b4_od_pins_a &sdmmc2_d47_pins_a>;
+ pinctrl-2 = <&sdmmc2_b4_sleep_pins_a &sdmmc2_d47_sleep_pins_a>;
+ non-removable;
+ no-sd;
+ no-sdio;
+ st,neg-edge;
+ bus-width = <8>;
+ vmmc-supply = <&scmi_v3v3>;
+ vqmmc-supply = <&scmi_vddio2>;
+ mmc-ddr-1_8v;
+ mmc-hs200-1_8v;
+ status = "okay";
+};
--
2.43.0
next prev parent reply other threads:[~2026-05-29 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 14:46 [PATCH v2 00/15] arm64: support Engicam MicroGEA-STM32MP257-RMM board Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 01/15] dt-bindings: arm: stm32: " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 02/15] arm64: dts: st: add SDMMC2 support on stm32mp25 Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 03/15] arm64: dts: st: add CAN1 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 04/15] arm64: dts: st: add i2c1 pins for stm32mp25 Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 05/15] arm64: dts: st: add ltdc " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 06/15] arm64: dts: st: add can1 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 07/15] arm64: dts: st: add pwm2/pwm4 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 08/15] arm64: dts: st: add sai1 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 09/15] arm64: dts: st: add sdmmc2 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 10/15] arm64: dts: st: add spi1 " Dario Binacchi
2026-05-29 14:46 ` [PATCH v2 11/15] arm64: dts: st: add usart1 " Dario Binacchi
2026-05-29 14:46 ` Dario Binacchi [this message]
2026-05-29 14:46 ` [PATCH v2 13/15] arm64: dts: st: support Engicam MicroGEA-STM32MP257-RMM board Dario Binacchi
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=20260529144707.3931919-13-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions$(echo .)com \
--cc=alexandre.torgue@foss$(echo .)st.com \
--cc=conor+dt@kernel$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=domenico.acri@engicam$(echo .)com \
--cc=francesco.utel@engicam$(echo .)com \
--cc=krzk+dt@kernel$(echo .)org \
--cc=linux-amarula@amarulasolutions$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-stm32@st-md-mailman$(echo .)stormreply.com \
--cc=mcoquelin.stm32@gmail$(echo .)com \
--cc=michael@amarulasolutions$(echo .)com \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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