From: Yannic Moog <Y.Moog@phytec.de>
To: "Frank.li@nxp.com" <Frank.li@nxp.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Teresa Remmet <T.Remmet@phytec.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Benjamin Hahn <B.Hahn@phytec.de>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
Yashwanth Varakala <Y.Varakala@phytec.de>,
Jan Remmet <J.Remmet@phytec.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"festevam@gmail.com" <festevam@gmail.com>
Subject: Re: [PATCH 2/3] arm64: dts: add imx8mp-libra-rdk-fpsc board
Date: Tue, 1 Apr 2025 05:13:19 +0000 [thread overview]
Message-ID: <9dd51df2a8a8c914c229991cf1419983c9cbdfc3.camel@phytec.de> (raw)
In-Reply-To: <Z+qkcZOv09roa1v4@lizhi-Precision-Tower-5810>
Hi Frank,
On Mon, 2025-03-31 at 10:19 -0400, Frank Li wrote:
> On Fri, Mar 28, 2025 at 02:04:38PM +0100, Yannic Moog wrote:
> > Add device tree for the Libra-i.MX 8M Plus FPSC board. The Libra is
> > a
> > pure development board and has hardware to support FPSC-24-A.0 set
> > of
> > features. The phyCORE-i.MX 8M Plus FPSC [1] SoM uses only a subset
> > of
> > the hardware features of the Libra board. The phyCORE-i.MX8MP FPSC
> > itself is a System on Module based on the i.MX 8M Plus SoC
> > utilizing the
> > Future Proof Solder Core [2] standard.
> >
> > To be able to easily map FPSC interface names to SoC interfaces,
> > the
> > FPSC interface names are added as inline comments. Example:
> >
> > &i2c5 { /* I2C4 */
> > pinctrl-0 = <&pinctrl_i2c5>;
> > [...]
> > };
> >
> > Here, I2C4 is the FPSC interface name. The i2c5 instance of the
> > i.MX 8M Plus
> > SoC is used to fulfill the i2c functionality and its signals are
> > routed
> > to the FPSC I2C4 signal pins:
> >
> > pinctrl_i2c5: i2c5grp {
> > fsl,pins = <
> > MX8MP_IOMUXC_SPDIF_RX__I2C5_SDA 0x
> > 400001c2 /* I2C4_SDA */
> > MX8MP_IOMUXC_SAI5_RXD0__I2C5_SCL 0x400001c2
> > /* I2C4_SCL */
> > >;
> > };
> >
> > The features are almost identical to the existing phyCORE-i.MX 8M
> > Plus
> > SoM, but the pin muxing is different due to the FPSC standard as
> > well as
> > 1.8V IO voltage instead of 3.3V.
> >
> > [1]
> > https://www.phytec.eu/en/produkte/system-on-modules/phycore-imx-8m-plus-fpsc/
> > [2] https://www.phytec.eu/en/produkte/system-on-modules/fpsc/
> >
> > Signed-off-by: Yannic Moog <y.moog@phytec.de>
> > ---
> > arch/arm64/boot/dts/freescale/Makefile | 1 +
> > .../boot/dts/freescale/imx8mp-libra-rdk-fpsc.dts | 291 ++++++++
> > .../boot/dts/freescale/imx8mp-phycore-fpsc.dtsi | 796
> > +++++++++++++++++++++
>
> New dts file suggest run https://github.com/lznuaa/dt-format to make
> sure
> nodes correct order.
Thank you for the hint, will do.
Yannic
>
> Frank
>
>
[...]
next prev parent reply other threads:[~2025-04-01 5:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 13:04 [PATCH 0/3] Add new imx imx8mp-libra-rdk-fpsc SBC Yannic Moog
2025-03-28 13:04 ` [PATCH 1/3] dt-bindings: add imx8mp-libra-rdk-fpsc Yannic Moog
2025-03-28 13:58 ` Krzysztof Kozlowski
2025-03-31 6:03 ` Yannic Moog
2025-03-31 8:15 ` krzk
2025-03-28 13:04 ` [PATCH 2/3] arm64: dts: add imx8mp-libra-rdk-fpsc board Yannic Moog
2025-03-31 14:19 ` Frank Li
2025-04-01 5:13 ` Yannic Moog [this message]
2025-03-28 13:04 ` [PATCH 3/3] arm64: dts: add imx8mp-libra-rdk-fpsc LVDS panel overlay Yannic Moog
2025-03-30 0:27 ` [PATCH 0/3] Add new imx imx8mp-libra-rdk-fpsc SBC Rob Herring (Arm)
-- strict thread matches above, loose matches on Subject: below --
2025-03-29 9:28 [PATCH 2/3] arm64: dts: add imx8mp-libra-rdk-fpsc board kernel test robot
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=9dd51df2a8a8c914c229991cf1419983c9cbdfc3.camel@phytec.de \
--to=y.moog@phytec.de \
--cc=B.Hahn@phytec.de \
--cc=Frank.li@nxp.com \
--cc=J.Remmet@phytec.de \
--cc=T.Remmet@phytec.de \
--cc=Y.Varakala@phytec.de \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.