From: Wei Fang <wei.fang@nxp.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, Frank.Li@nxp.com
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] update NETC node of i.MX95
Date: Wed, 28 May 2025 16:34:30 +0800 [thread overview]
Message-ID: <20250528083433.3861625-1-wei.fang@nxp.com> (raw)
We found that NETC has an overshoot issue, so the drive strength of the
related pins needs to be reduced. The first two patches are used to fix
this issue. The third patch adds SMMU support for NETC.
Wei Fang (3):
arm64: dts: imx95-19x19-evk: fix the overshoot issue of NETC
arm64: dts: imx95-15x15-evk: fix the overshoot issue of NETC
arm64: dts: imx95: add SMMU support for NETC
.../boot/dts/freescale/imx95-15x15-evk.dts | 28 ++++++++++++-------
.../boot/dts/freescale/imx95-19x19-evk.dts | 12 ++++----
arch/arm64/boot/dts/freescale/imx95.dtsi | 8 ++++++
3 files changed, 32 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2025-05-28 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 8:34 Wei Fang [this message]
2025-05-28 8:34 ` [PATCH 1/3] arm64: dts: imx95-19x19-evk: fix the overshoot issue of NETC Wei Fang
2025-05-28 15:07 ` Frank Li
2025-05-28 8:34 ` [PATCH 2/3] arm64: dts: imx95-15x15-evk: " Wei Fang
2025-05-28 15:08 ` Frank Li
2025-05-28 8:34 ` [PATCH 3/3] arm64: dts: imx95: add SMMU support for NETC Wei Fang
2025-05-28 15:09 ` Frank Li
2025-05-29 2:43 ` Wei Fang
2025-06-25 5:05 ` [PATCH 0/3] update NETC node of i.MX95 Wei Fang
2025-06-30 3:35 ` 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=20250528083433.3861625-1-wei.fang@nxp.com \
--to=wei.fang@nxp.com \
--cc=Frank.Li@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=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