From: Daniel Baluta <daniel.baluta@oss.nxp.com>
To: Frank Obergfell <frank.obergfell@bytesatwork.ch>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Frank Li <Frank.Li@nxp.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Michael Walle <mwalle@kernel.org>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Jessica Zhang <jesszhan0024@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Alexander Forsch <alexander.forsch@bytesatwork.ch>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/5] arm64: dts: freescale: Add support for bytesatwork i.MX93
Date: Wed, 11 Nov 2026 10:43:15 +0200 [thread overview]
Message-ID: <23bdf173-93ba-428d-8415-107f64e163ba@oss.nxp.com> (raw)
In-Reply-To: <20261111081150.950272-6-frank.obergfell@bytesatwork.ch>
Hi Frank,
Some comments inline.
On 11/11/26 10:11, Frank Obergfell wrote:
> Add support for the bytesatwork i.MX93 byteENGINE OSM module
> placed on the byteDEVKIT.
>
[...]
> +BYTESATWORK MODULES AND BOARDS
> +M: Alexander Forsch <alexander.forsch@bytesatwork.ch>
> +M: Frank Obergfell <frank.obergfell@bytesatwork.ch>
> +S: Maintained
> +F: arch/arm64/boot/dts/freescale/imx93-bytedevkit.dts
> +F: arch/arm64/boot/dts/freescale/imx93-byteengine.dtsi
Care to add imx list here?
L:» imx@lists.linux.dev
[..]
> +
> +&mu1 {
> + status = "okay";
> +};
> +
Should we enable the nodes in imx93-bytedevkit.dts ? Nodes
are rarely enabled in dtsi files.
Think if you add another revision of the board with just one MU unit.
Another idea would be to completely remove imx93-bytedevkit.dtsi and directly
include imx93.dtsi in imx93-bytedevkit.dts
prev parent reply other threads:[~2026-11-11 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 8:11 [PATCH v2 0/5] arm64: dts: freescale: Add support for bytesatwork byteDEVKIT i.MX93 Frank Obergfell
2026-11-11 8:11 ` [PATCH v2 1/5] dt-bindings: display: panel: ilitek,ili9806e: Add Youritech et050fw01-kt Frank Obergfell
2026-11-11 8:45 ` Daniel Baluta
2026-11-11 8:11 ` [PATCH v2 2/5] drm/panel: ilitek-ili9806e: Add support for Youritech et050fw01-kt panel Frank Obergfell
2026-11-11 8:11 ` [PATCH v2 3/5] arm64: dts: freescale: imx93: Add MIPI DSI controller node Frank Obergfell
2026-11-11 8:11 ` [PATCH v2 4/5] dt-bindings: arm: fsl: Add byteENGINE i.MX93 platforms Frank Obergfell
2026-11-11 8:11 ` [PATCH v2 5/5] arm64: dts: freescale: Add support for bytesatwork i.MX93 Frank Obergfell
2026-11-11 8:43 ` Daniel Baluta [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=23bdf173-93ba-428d-8415-107f64e163ba@oss.nxp.com \
--to=daniel.baluta@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=alexander.forsch@bytesatwork.ch \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=frank.obergfell@bytesatwork.ch \
--cc=imx@lists.linux.dev \
--cc=jesszhan0024@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®