From: Josua Mayer <josua@solid-run.com>
To: Shawn Guo <shawnguo2@yeah.net>
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>,
Yazan Shhady <yazan.shhady@solid-run.com>,
Mikhail Anikin <mikhail.anikin@solid-run.com>,
Jon Nettleton <jon@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 v3 3/3] arm64: dts: add description for solidrun imx8mp hummingboard variants
Date: Thu, 11 Sep 2025 09:21:31 +0000 [thread overview]
Message-ID: <3c52408e-da76-4545-b783-8c2f2abbcfa6@solid-run.com> (raw)
In-Reply-To: <aMIrKYBPF2kMctIE@dragon>
Am 11.09.25 um 03:51 schrieb Shawn Guo:
> On Sat, Aug 23, 2025 at 05:28:23PM +0300, Josua Mayer wrote:
>> Add descriptions for the SolidRun i.MX8M Plus System on Module based
>> HummingBoard product-line. They share a common designed based on the
>> "Pulse" version, defined by various assembly options.
>>
>> The HummingBoard Pulse features:
>> - 2x RJ45 Ethernet
>> - 2x USB-3.0 Type A
>> - HDMI connector
>> - mini-HDMI connector
>> - microSD connector
>> - mini-PCI-E connector with SIM slot supporting USB-2.0/3.0 interfaces
>> - M.2 connector with SIM slot supporting USB-2.0/3.0 interfaces
>> - MIPI-CSI Camera Connector (not described without specific camera)
>> - 3.5mm Analog Stereo Out / Microphone In Headphone Jack
>> - RTC with backup battery
>>
>> The variants Mate and Ripple are reduced versions of Pulse.
>>
>> The HummingBoard Pro extends Pulse with PCI-E on M.2 connector.
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
> It doesn't apply to imx/dt64 branch.
It looks like the Makefile has changed very slightly causing some fuzz.
Please see v4 - which I tried to rebase on imx/dt64 from earlier today.
>
> Shawn
>
>
prev parent reply other threads:[~2025-09-11 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 14:28 [PATCH v3 0/3] arm64: dts: add descriptions for solidrun i.mx8mp based boards Josua Mayer
2025-08-23 14:28 ` [PATCH v3 1/3] dt-bindings: arm: fsl: Add bindings for SolidRun i.MX8MP SoM and boards Josua Mayer
2025-09-11 1:50 ` Shawn Guo
2025-08-23 14:28 ` [PATCH v3 2/3] arm64: dts: add description for solidrun imx8mp som and cubox-m Josua Mayer
2025-09-11 1:50 ` Shawn Guo
2025-08-23 14:28 ` [PATCH v3 3/3] arm64: dts: add description for solidrun imx8mp hummingboard variants Josua Mayer
2025-09-11 1:51 ` Shawn Guo
2025-09-11 9:21 ` Josua Mayer [this message]
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=3c52408e-da76-4545-b783-8c2f2abbcfa6@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jon@solid-run.com \
--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=shawnguo2@yeah.net \
--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;
as well as URLs for NNTP newsgroup(s).