From: Frank Li <Frank.li@nxp.com>
To: Alexander Stein <alexander.stein@ew.tq-group.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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux@ew.tq-group.com
Subject: Re: [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa91xxCA/MBa91xxCA
Date: Thu, 28 Aug 2025 14:26:22 -0400 [thread overview]
Message-ID: <aLCfTswvqXDLtAhm@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250828094745.3733533-3-alexander.stein@ew.tq-group.com>
On Thu, Aug 28, 2025 at 11:47:43AM +0200, Alexander Stein wrote:
> This adds support for TQMa91xxCA module attached to MBa91xxCA board.
> TQMa91xx is a SOM using i.MX91 SOC. The SOM features PMIC, RAM, e-MMC and
> some optional peripherals like SPI-NOR, RTC, EEPROM, gyroscope and
> secure element.
>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
> ---
> arch/arm64/boot/dts/freescale/Makefile | 1 +
> .../freescale/imx91-tqma9131-mba91xxca.dts | 737 ++++++++++++++++++
> .../boot/dts/freescale/imx91-tqma9131.dtsi | 295 +++++++
> 3 files changed, 1033 insertions(+)
> create mode 100644 arch/arm64/boot/dts/freescale/imx91-tqma9131-mba91xxca.dts
> create mode 100644 arch/arm64/boot/dts/freescale/imx91-tqma9131.dtsi
>
> diff --git a/arch/arm64/boot/dts/freescale/Makefile b/arch/arm64/boot/dts/freescale/Makefile
> index 947de7f125caf..3a937232d6f29 100644
> --- a/arch/arm64/boot/dts/freescale/Makefile
> +++ b/arch/arm64/boot/dts/freescale/Makefile
> @@ -338,6 +338,7 @@ dtb-$(CONFIG_ARCH_MXC) += imx8qxp-tqma8xqps-mb-smarc-2.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8ulp-9x9-evk.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx8ulp-evk.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx91-11x11-evk.dtb
> +dtb-$(CONFIG_ARCH_MXC) += imx91-tqma9131-mba91xxca.dtb
> dtb-$(CONFIG_ARCH_MXC) += imx93-9x9-qsb.dtb
>
...
> +
> + pinctrl_jtag: jtaggrp {
> + fsl,pins = <MX91_PAD_DAP_TCLK_SWCLK__JTAG_MUX_TCK 0x051e>,
> + <MX91_PAD_DAP_TDI__JTAG_MUX_TDI 0x1200>,
> + <MX91_PAD_DAP_TDO_TRACESWO__JTAG_MUX_TDO 0x031e>,
> + <MX91_PAD_DAP_TMS_SWDIO__JTAG_MUX_TMS 0x1200>;
> + };
Any one use it?
> +
> + pinctrl_lpi2c3: lpi2c3grp {
> + fsl,pins = /* SION | HYS | OD | FSEL_3 | DSE X4 */
> + <MX91_PAD_GPIO_IO28__LPI2C3_SDA 0x4000199e>,
> + <MX91_PAD_GPIO_IO29__LPI2C3_SCL 0x4000199e>;
> + };
> +
...
> +
> + /* protectable identification memory (part of M24C64-D @57) */
> + eeprom@5f {
> + compatible = "atmel,24c64d-wl";
> + reg = <0x5f>;
> + vcc-supply = <&buck4>;
> + };
> +
> + imu@6a {
I am not if "imu" is common node name.
Frank
> + compatible = "st,ism330dhcx";
> + reg = <0x6a>;
> + vdd-supply = <&buck4>;
> + vddio-supply = <&buck4>;
> + };
> +};
> +
> +&usdhc1 {
> + pinctrl-names = "default", "state_100mhz", "state_200mhz";
> + pinctrl-0 = <&pinctrl_usdhc1>;
> + pinctrl-1 = <&pinctrl_usdhc1>;
> + pinctrl-2 = <&pinctrl_usdhc1>;
> + vmmc-supply = <&buck4>;
> + vqmmc-supply = <&buck5>;
> + bus-width = <8>;
> + non-removable;
> + no-sdio;
> + no-sd;
> + status = "okay";
> +};
> +
...
> +};
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-08-29 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 9:47 [PATCH 0/2] TQMa91xx support Alexander Stein
2025-08-28 9:47 ` [PATCH 1/2] dt-bindings: arm: fsl: add TQMa91xxLA SOM Alexander Stein
2025-08-28 18:17 ` Frank Li
2025-08-29 6:05 ` Max Merchel
2025-08-28 9:47 ` [PATCH 2/2] arm64: dts: freescale: add initial device tree for TQMa91xxCA/MBa91xxCA Alexander Stein
2025-08-28 18:26 ` Frank Li [this message]
2025-08-29 6:25 ` Alexander Stein
2025-09-01 4:07 ` Peng Fan
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=aLCfTswvqXDLtAhm@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=alexander.stein@ew.tq-group.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=linux@ew.tq-group.com \
--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;
as well as URLs for NNTP newsgroup(s).