From: Peng Fan <peng.fan@oss.nxp.com>
To: Primoz Fiser <primoz.fiser@norik.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
upstream@lists.phytec.de
Subject: Re: [PATCH v2 0/4] Initial PHYTEC i.MX93 overlays
Date: Mon, 7 Jul 2025 16:04:57 +0800 [thread overview]
Message-ID: <20250707080457.GB11488@nxa18884-linux> (raw)
In-Reply-To: <20250707061101.1194618-1-primoz.fiser@norik.com>
On Mon, Jul 07, 2025 at 08:10:57AM +0200, Primoz Fiser wrote:
>Add initial overlays for the PHYTEC phyCORE-i.MX93 SoM based boards,
>that is the phyBOARD-Segin-i.MX93 and phyBOARD-Nash-i.MX93.
>
>Overlay #1:
> - imx93-phycore-rpmsg.dtbo
> - add support for M33 core RPMsg on phyCORE-i.MX93 based boards
> - applicable to both phyBOARD-Nash and phyBOARD-Segin boards
>
>Overlay #2:
> - imx93-phyboard-segin-peb-eval-01.dtbo
> - add support for PHYTEC PEB-EVAL-01 evaluation adapter
> - applicable to phyBOARD-Segin board
>
>Overlay #3:
> - imx93-phyboard-segin-peb-wlbt-05.dtbo
> - add support for PHYTEC PEB-WLBT-05 WLAN/BT adapter
> - applicable to phyBOARD-Segin board
>
>Overlay #4:
> - imx93-phyboard-nash-peb-wlbt-07.dtbo
> - add support for PHYTEC PEB-WLBT-07 WLAN/BT adapter
> - applicable to phyBOARD-Nash board
>
>
>Changes in v2:
>- reorder reserved memory nodes by address
>
>Link to v1: https://lore.kernel.org/all/20250619063954.1730231-1-primoz.fiser@norik.com/
>
>Primoz Fiser (4):
> arm64: dts: imx93-phycore-som: Add RPMsg overlay
> arm64: dts: imx93-phyboard-segin: Add PEB-EVAL-01 overlay
> arm64: dts: imx93-phyboard-segin: Add PEB-WLBT-05 overlay
> arm64: dts: imx93-phyboard-nash: Add PEB-WLBT-07 overlay
I think it would be better to update License to
SPDX-License-Identifier: (GPL-2.0+ OR MIT)
But up to you, I am not sure whether dtso(GPL-2.0) could
work with dts(GPL-2.0 or MIT).
For the patchset
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Regards,
Peng
next prev parent reply other threads:[~2025-07-07 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 6:10 [PATCH v2 0/4] Initial PHYTEC i.MX93 overlays Primoz Fiser
2025-07-07 6:10 ` [PATCH v2 1/4] arm64: dts: imx93-phycore-som: Add RPMsg overlay Primoz Fiser
2025-07-07 6:10 ` [PATCH v2 2/4] arm64: dts: imx93-phyboard-segin: Add PEB-EVAL-01 overlay Primoz Fiser
2025-07-07 6:11 ` [PATCH v2 3/4] arm64: dts: imx93-phyboard-segin: Add PEB-WLBT-05 overlay Primoz Fiser
2025-07-07 6:11 ` [PATCH v2 4/4] arm64: dts: imx93-phyboard-nash: Add PEB-WLBT-07 overlay Primoz Fiser
2025-07-07 8:04 ` Peng Fan [this message]
2025-07-07 7:08 ` [PATCH v2 0/4] Initial PHYTEC i.MX93 overlays Primoz Fiser
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=20250707080457.GB11488@nxa18884-linux \
--to=peng.fan@oss.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=primoz.fiser@norik.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
/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