public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Frank Li <Frank.li@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Mikhail Anikin <mikhail.anikin@solid-run.com>,
	Yazan Shhady <yazan.shhady@solid-run.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v9 8/8] arm64: dts: add description for solidrun i.mx8mm som and evb
Date: Fri, 13 Mar 2026 10:01:08 +0000	[thread overview]
Message-ID: <ee743a02-103a-4f20-91da-99d6cba699ff@solid-run.com> (raw)
In-Reply-To: <aa8TvVC8KWBiVGrG@lizhi-Precision-Tower-5810>

Hi Frank,

Am 09.03.26 um 19:38 schrieb Frank Li:
> On Thu, Feb 26, 2026 at 06:36:37PM +0200, Josua Mayer wrote:
>> Add description for the SolidRun i.MX8M Mini SoM on HummingBoard Ripple.
>>
>> The SoM features:
>> - 1Gbps Ethernet with PHY
>> - eMMC
>> - 1/2GB DDR
>> - NPU (assembly option)
>> - WiFi + Bluetooth
>>
>> The HummingBoard Ripple features:
>> - 2x USB-2.0 Type-A connector
>> - 1Gbps RJ45 Ethernet with PoE
>> - microSD connector
>> - microHDMI connector
>> - mpcie connector with USB-2.0 interface + SIM card holder
>> - microUSB connector for console (using fdtdi chip)
>> - RTC with backup battery
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>> ---
>>  arch/arm64/boot/dts/freescale/Makefile             |   2 +
>>  .../dts/freescale/imx8mm-hummingboard-ripple.dts   | 335 ++++++++++++++++++
>>  arch/arm64/boot/dts/freescale/imx8mm-sr-som.dtsi   | 393 +++++++++++++++++++++
>>  3 files changed, 730 insertions(+)
> Please run https://github.com/lznuaa/dt-format for new dts(i) files.
>
>> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
>> index a61ed098ff8d..1314aec6634b 100644
>> --- a/arch/arm64/boot/dts/freescale/Makefile
>> +++ b/arch/arm64/boot/dts/freescale/Makefile
>> @@ -126,6 +126,8 @@ imx8mm-evk-pcie-ep-dtbs += imx8mm-evk.dtb imx-pcie0-ep.dtbo
>>  imx8mm-evkb-pcie-ep-dtbs += imx8mm-evkb.dtb imx-pcie0-ep.dtbo
>>  dtb-$(CONFIG_ARCH_MXC) += imx8mm-evk-pcie-ep.dtb imx8mm-evkb-pcie-ep.dtb
>> +
>> +	carrier_eeprom: eeprom@57{
> Need space before {, dt-format can fix this for you. patch 1-4 already
> picked, only need resent 5-8 after run dt-format.

I tried running the tool again, and it nicely re-ordereed the new imx8mm-hummingboard-ripple.dts

Yet it crashes on imx8mn-solidsense-n8-compact.dts:

❯ ./dt-format /opt/workspace/linux/arch/arm64/boot/dts/freescale/imx8mn-solidsense-n8-compact.dts
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr: __pos (which is 26) > this->size() (which is 18)
[1]    12030 IOT instruction (core dumped)  ./dt-format

Then I ran it on the iiot board dts and dtso, and it suggests one particular change I was not expecting:

-&{/} {
+& {};
+
+/ {

❯ find . -iname "*.dtso" -exec grep -H "&{/}" {} \; | wc -l
110

❯ find . -iname "*.dtso" -exec grep -H "/ {" {} \; | wc -l
15

Which one is preferred going forward?


  reply	other threads:[~2026-03-13 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 16:36 [PATCH v9 0/8] arm64: dts: add description for solidrun imx8mp hummingboard-iiot Josua Mayer
2026-02-26 16:36 ` [PATCH v9 1/8] dt-bindings: arm: fsl: Add various solidrun i.mx8m boards Josua Mayer
2026-02-26 16:36 ` [PATCH v9 2/8] arm64: dts: imx8mp-hummingboard-pulse/cubox-m: fix vmmc gpio polarity Josua Mayer
2026-02-26 16:36 ` [PATCH v9 3/8] arm64: dts: imx8mp-hummingboard-pulse: fix mini-hdmi dsi port reference Josua Mayer
2026-02-26 16:36 ` [PATCH v9 4/8] arm64: dts: imx8mp-sr-som: build dtbs with symbols for overlay support Josua Mayer
2026-02-26 16:36 ` [PATCH v9 5/8] arm64: dts: add description for SolidRun i.MX8MP HummingBoard IIoT Josua Mayer
2026-02-26 16:36 ` [PATCH v9 6/8] arm64: dts: imx8mp-hummingboard-iiot: add dt overlays for muxable ports Josua Mayer
2026-02-26 16:36 ` [PATCH v9 7/8] arm64: dts: add description for solidrun solidsense-n8 board Josua Mayer
2026-02-26 16:36 ` [PATCH v9 8/8] arm64: dts: add description for solidrun i.mx8mm som and evb Josua Mayer
2026-03-09 18:38   ` Frank Li
2026-03-13 10:01     ` Josua Mayer [this message]
2026-03-13 10:08       ` Josua Mayer
2026-03-09 17:09 ` (subset) [PATCH v9 0/8] arm64: dts: add description for solidrun imx8mp hummingboard-iiot Frank Li

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=ee743a02-103a-4f20-91da-99d6cba699ff@solid-run.com \
    --to=josua@solid-run.com \
    --cc=Frank.li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.anikin@solid-run.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=yazan.shhady@solid-run.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