From: Joseph Guo <qijian.guo@nxp.com>
To: 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>
Cc: Justin Jiang <justin.jiang@nxp.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
qijian.guo@oss.nxp.com, Joseph Guo <qijian.guo@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Francesco Valla <francesco@valla.it>,
Tom Zheng <haidong.zheng@nxp.com>,
Steven Yang <steven.yang@nxp.com>, Andrew Lunn <andrew@lunn.ch>
Subject: [PATCH v3 0/2] Add FRDM i.MX 91 Development board support
Date: Tue, 30 Dec 2025 16:58:52 +0900 [thread overview]
Message-ID: <20251230-imx91_frdm-v3-0-60cac61c96ec@nxp.com> (raw)
FRDM-IMX91 board is a low cost development platform based on i.MX91 SoC:
https://www.nxp.com/design/design-center/development-boards-and-designs/FRDM-IMX91
Add device tree and dt-binding for FRDM-IMX91.
Signed-off-by: Joseph Guo <qijian.guo@nxp.com>
---
Changes in v3:
- end property list with 'status'
- add newline between property list and child node
- add code-review trailers
- Link to v2: https://lore.kernel.org/r/20251212-imx91_frdm-v2-0-4dd6d289e81d@nxp.com
Changes in v2:
- rename compatible 'frdm-imx91' to 'imx91-11x11-frdm'
- rename 'sw-keys' to 'gpio-keys'
- rename 'user_btn' to 'button-k'
- drop lpspi3 node
- rename iomuxc 'grpsleep' to 'sleepgrp'
- move dt-binding patch before the dts patch
- add board page link in cover letter
- use CAN PHY to manage the stby gpio of flexcan2
- drop realtek property
- add pcf2131 aliase
- add bootph- property for nodes should be kept in bootloader phase
- add reset-gpio and assert for eqos and fec
- delete unused alias
- Link to v1: https://lore.kernel.org/r/20251114-imx91_frdm-v1-0-e5763bdf9336@nxp.com
---
Joseph Guo (2):
dt-bindings: arm: imx Add FRDM-IMX91 board
arm64: dts: freescale: Add FRDM-IMX91 basic support
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
arch/arm64/boot/dts/freescale/imx91-11x11-frdm.dts | 906 +++++++++++++++++++++
3 files changed, 908 insertions(+)
---
base-commit: 73f1e611b076de705c2f1c26cfdfc5b8e96f4733
change-id: 20251114-imx91_frdm-add2b2c07e78
Best regards,
--
Joseph Guo <qijian.guo@nxp.com>
next reply other threads:[~2025-12-30 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 7:58 Joseph Guo [this message]
2025-12-30 7:58 ` [PATCH v3 1/2] dt-bindings: arm: imx Add FRDM-IMX91 board Joseph Guo
2025-12-30 7:58 ` [PATCH v3 2/2] arm64: dts: freescale: Add FRDM-IMX91 basic support Joseph Guo
2025-12-31 3:05 ` [PATCH v3 0/2] Add FRDM i.MX 91 Development board support Shawn Guo
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=20251230-imx91_frdm-v3-0-60cac61c96ec@nxp.com \
--to=qijian.guo@nxp.com \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco@valla.it \
--cc=haidong.zheng@nxp.com \
--cc=imx@lists.linux.dev \
--cc=justin.jiang@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qijian.guo@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=steven.yang@nxp.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
all inboxes | Powered by JetHome®