From: Linus Walleij <linusw@kernel.org>
To: Frank Li <Frank.Li@nxp.com>, Peter Rosin <peda@axentia.se>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
"Haibo Chen" <haibo.chen@nxp.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Ahmad Fatoum" <a.fatoum@pengutronix.de>
Subject: Re: [PATCH v5 0/7] pinctrl: Add generic pinctrl for board-level mux chips
Date: Tue, 7 Apr 2026 08:48:53 +0200 [thread overview]
Message-ID: <CAD++jLmyf9mD4FgmLqNdrP1WdFgQptGZ7KbVOhwYCRrxZQXuHA@mail.gmail.com> (raw)
In-Reply-To: <CAD++jLmoHiJWV3J8f3TtpmQWLpUFD24icQEv2cbO3+x7775zxw@mail.gmail.com>
On Tue, Apr 7, 2026 at 8:42 AM Linus Walleij <linusw@kernel.org> wrote:
> > mux: add devm_mux_control_get_from_np() to get mux from child node
>
> Didn't get an ACK from the mux maintainer for this but this has been going
> on for long now so I applied it.
>
> Peter: protest if you don't like this and I will back it out.
I created an immutable branch for Peter to pull in if he want it:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/log/?h=ib-mux-pinctrl
(You can also pull in just the bottom commit which is just the mux change)
Yours,
Linus Walleij
prev parent reply other threads:[~2026-04-07 6:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:33 [PATCH v5 0/7] pinctrl: Add generic pinctrl for board-level mux chips Frank Li
2026-03-27 21:33 ` [PATCH v5 1/7] mux: add devm_mux_control_get_from_np() to get mux from child node Frank Li
2026-03-27 21:33 ` [PATCH v5 2/7] dt-bindings: pinctrl: Add generic pinctrl for board-level mux chips Frank Li
2026-03-27 21:34 ` [PATCH v5 3/7] pinctrl: extract pinctrl_generic_to_map() from pinctrl_generic_pins_function_dt_node_to_map() Frank Li
2026-03-30 15:33 ` Conor Dooley
2026-03-27 21:34 ` [PATCH v5 4/7] pinctrl: add optional .release_mux() callback Frank Li
2026-03-27 21:34 ` [PATCH v5 5/7] pinctrl: add generic board-level pinctrl driver using mux framework Frank Li
2026-03-27 21:34 ` [PATCH v5 6/7] arm64: dts: imx8mp-evk: add board-level mux for CAN2 and MICFIL Frank Li
2026-03-27 21:34 ` [PATCH v5 7/7] arm64: dts: imx8mp-evk: add flexcan2 overlay file Frank Li
2026-04-06 10:54 ` [PATCH v5 0/7] pinctrl: Add generic pinctrl for board-level mux chips Frank Li
2026-04-07 6:42 ` Linus Walleij
2026-04-07 6:48 ` Linus Walleij [this message]
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=CAD++jLmyf9mD4FgmLqNdrP1WdFgQptGZ7KbVOhwYCRrxZQXuHA@mail.gmail.com \
--to=linusw@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=a.fatoum@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--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=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=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).