From: "Rob Herring (Arm)" <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: "Linus Walleij" <linusw@kernel.org>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Peter Rosin" <peda@axentia.se>,
"Conor Dooley" <conor+dt@kernel.org>,
"Haibo Chen" <haibo.chen@nxp.com>,
linux-kernel@vger.kernel.org,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 2/6] dt-bindings: pinctrl: Add generic pinctrl for board-level mux chips
Date: Thu, 5 Mar 2026 18:57:05 -0600 [thread overview]
Message-ID: <177275862503.886378.14653051699126465622.robh@kernel.org> (raw)
In-Reply-To: <20260225-pinctrl-mux-v2-2-1436a25fa454@nxp.com>
On Wed, 25 Feb 2026 18:55:06 -0500, Frank Li wrote:
> Add a generic pinctrl binding for board-level pinmux chips that are
> controlled through the multiplexer subsystem.
>
> On some boards, especially development boards, external mux chips are used
> to switch SoC signals between different peripherals (e.g. MMC and UART).
> The mux select lines are often driven by a GPIO expander over I2C,
> as illustrated below:
>
> ┌──────┐ ┌─────┐
> │ SOC │ │ │ ┌───────┐
> │ │ │ │───►│ MMC │
> │ │ │ MUX │ └───────┘
> │ ├─────►│ │ ┌───────┐
> │ │ │ │───►│ UART │
> │ │ └─────┘ └───────┘
> │ │ ▲
> │ │ ┌────┴──────────────┐
> │ I2C ├───►│ GPIO Expander │
> └──────┘ └───────────────────┘
>
> Traditionally, gpio-hog is used to configure the onboard mux at boot.
> However, the GPIO expander may probe later than consumer devices such as
> MMC. As a result, the MUX might not be configured when the peripheral
> driver probes, leading to initialization failures or data transfer errors.
>
> Introduce a generic pinctrl binding that models the board-level MUX as a
> pin control provider and builds proper device links between the MUX, its
> GPIO controller, and peripheral devices. This ensures correct probe
> ordering and reliable mux configuration.
>
> The implementation leverages the standard multiplexer subsystem, which
> provides broad support for onboard mux controllers and avoids the need for
> per-driver custom MUX handling.
>
> Allow pinctrl-* pattern as node name because this pinctrl device have not
> reg property.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> change in v2:
> - change descriptions for device, not for driver
> - add missed additionalProperties: false
> ---
> .../bindings/pinctrl/pinctrl-multiplexer.yaml | 57 ++++++++++++++++++++++
> .../devicetree/bindings/pinctrl/pinctrl.yaml | 2 +-
> 2 files changed, 58 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-03-06 0:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 23:55 [PATCH v2 0/6] pinctrl: Add generic pinctrl for board-level mux chips Frank Li
2026-02-25 23:55 ` [PATCH v2 1/6] mux: add devm_mux_control_get_from_np() to get mux from child node Frank Li
2026-02-25 23:55 ` [PATCH v2 2/6] dt-bindings: pinctrl: Add generic pinctrl for board-level mux chips Frank Li
2026-02-27 9:02 ` Linus Walleij
2026-03-06 0:57 ` Rob Herring (Arm) [this message]
2026-02-25 23:55 ` [PATCH v2 3/6] pinctrl: add optional .release_mux() callback Frank Li
2026-02-27 9:07 ` Linus Walleij
2026-02-27 15:32 ` Frank Li
2026-03-02 10:12 ` Linus Walleij
2026-02-25 23:55 ` [PATCH v2 4/6] pinctrl: add generic board-level pinctrl driver using mux framework Frank Li
2026-02-27 9:09 ` Daniel Baluta
2026-02-27 9:20 ` Linus Walleij
2026-02-27 15:22 ` Frank Li
2026-03-02 10:11 ` Linus Walleij
2026-03-05 17:37 ` Frank Li
2026-03-08 23:49 ` Linus Walleij
2026-02-25 23:55 ` [PATCH v2 5/6] arm64: dts: imx8mp-evk: add board-level mux for CAN2 and MICFIL Frank Li
2026-02-25 23:55 ` [PATCH v2 6/6] arm64: dts: imx8mp-evk: add flexcan2 overlay file 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=177275862503.886378.14653051699126465622.robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=rafal@milecki.pl \
--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