From: Dinesh kumar v <dineshkumarv85@gmail.com>
To: Frank.Li@nxp.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, s.hauer@pengutronix.de
Cc: imx@lists.linux.dev, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
festevam@gmail.com, Dinesh kumar v <dinesh.v@adlinktech.com>
Subject: [PATCH v2 0/3] Add ADLINK LEC-iMX95 board support
Date: Mon, 2 Nov 2026 15:56:50 +0530 [thread overview]
Message-ID: <20261102102653.272056-1-dinesh.v@adlinktech.com> (raw)
In-Reply-To: <20261102065645.121046-1-dinesh.v@adlinktech.com>
This patch series adds device tree support for the ADLINK LEC-iMX95
module on the I-Pi SMARC Plus carrier board.
The series includes:
- Add the ADLINK vendor prefix to vendor-prefixes.yaml.
- Add the ADLINK LEC-iMX95 compatible strings to the Freescale
i.MX device tree binding.
- Add the common device tree description for the LEC-iMX95 module.
- Add the I-Pi SMARC Plus carrier board device tree.
The module device tree describes the onboard peripherals and interfaces,
while the carrier board device tree describes the carrier-specific
hardware connections.
The device tree has been compiled and validated using DT schema checks.
Changes in v2:
- Add the ADLINK vendor prefix to vendor-prefixes.yaml.
- Move the ADLINK compatible entry before PHYTEC in alphabetical order.
- Enable open-drain configuration for LPI2C8 SCL and SDA pins.
Hardware: ADLINK LEC-iMX95
Carrier board: I-Pi SMARC Plus
SoC: NXP i.MX95
Signed-off-by: Dinesh kumar v <dinesh.v@adlinktech.com>
Dinesh kumar v (3):
dt-bindings: vendor-prefixes: Add ADLINK
dt-bindings: arm: fsl: Add ADLINK LEC-iMX95
arm64: dts: imx95: Add ADLINK LEC-iMX95 board support
.../devicetree/bindings/arm/fsl.yaml | 6 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../dts/freescale/imx95-lec-ipi-smarc.dts | 237 ++++++++++
arch/arm64/boot/dts/freescale/imx95-lec.dtsi | 414 ++++++++++++++++++
5 files changed, 660 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx95-lec-ipi-smarc.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx95-lec.dtsi
--
2.25.1
next prev parent reply other threads:[~2026-11-02 10:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 6:56 [PATCH 0/2] Add ADLINK LEC-iMX95 board support Dinesh kumar v
2026-11-02 6:56 ` [PATCH 1/2] dt-bindings: arm: fsl: Add ADLINK LEC-iMX95 Dinesh kumar v
2026-11-02 7:04 ` sashiko-bot
2026-11-02 6:56 ` [PATCH 2/2] arm64: dts: imx95: Add ADLINK LEC-iMX95 board support Dinesh kumar v
2026-11-02 7:10 ` sashiko-bot
2026-11-02 10:26 ` Dinesh kumar v [this message]
2026-11-02 10:26 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add ADLINK Dinesh kumar v
2026-11-02 10:32 ` sashiko-bot
2026-11-02 10:26 ` [PATCH v2 2/3] dt-bindings: arm: fsl: Add ADLINK LEC-iMX95 Dinesh kumar v
2026-11-02 10:26 ` [PATCH v2 3/3] arm64: dts: imx95: Add ADLINK LEC-iMX95 board support Dinesh kumar v
2026-11-02 10:45 ` sashiko-bot
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=20261102102653.272056-1-dinesh.v@adlinktech.com \
--to=dineshkumarv85@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinesh.v@adlinktech.com \
--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=robh@kernel.org \
--cc=s.hauer@pengutronix.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