From: Peng Fan <peng.fan@oss.nxp.com>
To: Frank Li <Frank.Li@nxp.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>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<imx@lists.linux.dev>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] arm64: dts: imx95-19x19-evk: adjust pinctrl settings for usdhc2
Date: Mon, 9 Jun 2025 18:01:14 +0800 [thread overview]
Message-ID: <20250609100114.GH13113@nxa18884-linux> (raw)
In-Reply-To: <20250606190045.1438740-3-Frank.Li@nxp.com>
On Fri, Jun 06, 2025 at 03:00:43PM -0400, Frank Li wrote:
>From: Luke Wang <ziniu.wang_1@nxp.com>
>
>The driver strength is too high for SDR104 mode. Change the driver strength
>to x3 according to hardware recommendation.
>
>Signed-off-by: Luke Wang <ziniu.wang_1@nxp.com>
>Signed-off-by: Frank Li <Frank.Li@nxp.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2025-06-09 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 19:00 [PATCH v2 1/4] arm64: dts: imx95-19x19-evk: add adc0 flexcan[1,2] i2c[2,3] uart5 spi3 and tpm3 Frank Li
2025-06-06 19:00 ` [PATCH v2 2/4] arm64: dts: imx95-evk: add USB3 PHY tuning properties Frank Li
2025-06-09 10:00 ` Peng Fan
2025-06-06 19:00 ` [PATCH v2 3/4] arm64: dts: imx95-19x19-evk: adjust pinctrl settings for usdhc2 Frank Li
2025-06-09 10:01 ` Peng Fan [this message]
2025-06-06 19:00 ` [PATCH v2 4/4] arm64: dts: imx95-19x19-evk: add GPIO reset for ethphy0 Frank Li
2025-06-09 10:01 ` Peng Fan
2025-06-09 10:00 ` [PATCH v2 1/4] arm64: dts: imx95-19x19-evk: add adc0 flexcan[1,2] i2c[2,3] uart5 spi3 and tpm3 Peng Fan
2025-07-01 14:02 ` 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=20250609100114.GH13113@nxa18884-linux \
--to=peng.fan@oss.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;
as well as URLs for NNTP newsgroup(s).