From: Sherry Sun <sherry.sun@nxp.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Frank.Li@nxp.com, s.hauer@pengutronix.de, festevam@gmail.com
Cc: imx@lists.linux.dev, kernel@pengutronix.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/2] arm64: dts: imx8mp-evk: Add usdhc1 for SDIO WiFi support
Date: Thu, 5 Feb 2026 15:34:52 +0800 [thread overview]
Message-ID: <20260205073454.3709673-1-sherry.sun@nxp.com> (raw)
This patch set adds usdhc1 support to enable M.2 SDIO WiFi on the
i.MX8MP EVK. The M.2 connector on this board can operate in both PCIe
and SDIO modes, and SDIO-based WLAN modules require proper power control
through the same M.2 WLAN enable line (W_DISABLE1 on pin 56).
Patch 1 corrects the IOMUX configuration by enabling the pull-select bit
for the M.2 regulator GPIO, ensuring that the weak pull-up is actually
applied.
Patch 2 enables usdhc1 and associated pinctrl settings needed for SDIO
WiFi operation on the M.2 connector.
---
Changes in V2:
1. Add fixes tag for patch#1.
2. Remove the patch which renames the regulator node from reg_pcie0 to
reg_m2_wlan, instead add second label reg_m2_wlan to simply code.
---
Sherry Sun (2):
arm64: dts: imx8mp-evk: Enable pull select bit for PCIe regulator GPIO
(M.2 W_DISABLE1)
arm64: dts: imx8mp-evk: Add usdhc1 for SDIO WiFi support
arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 63 +++++++++++++++++++-
1 file changed, 61 insertions(+), 2 deletions(-)
--
2.37.1
next reply other threads:[~2026-02-05 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 7:34 Sherry Sun [this message]
2026-02-05 7:34 ` [PATCH V2 1/2] arm64: dts: imx8mp-evk: Enable pull select bit for PCIe regulator GPIO (M.2 W_DISABLE1) Sherry Sun
2026-02-05 15:14 ` Frank Li
2026-02-05 7:34 ` [PATCH V2 2/2] arm64: dts: imx8mp-evk: Add usdhc1 for SDIO WiFi support Sherry Sun
2026-02-05 15:15 ` Frank Li
2026-03-02 19:28 ` Frank Li
2026-03-02 16:17 ` [PATCH V2 0/2] " Frank Li
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=20260205073454.3709673-1-sherry.sun@nxp.com \
--to=sherry.sun@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 \
/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