From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
Peter Rosin <peda@axentia.se>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
David Lechner <dlechner@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: mux: gpio-mux: add enable-gpios support
Date: Fri, 16 Jan 2026 17:04:31 +0100 [thread overview]
Message-ID: <a5645b54-7e12-4a42-aac6-9fa517c45ecc@kernel.org> (raw)
In-Reply-To: <20260116152621.75205-2-antoniu.miclaus@analog.com>
On 16/01/2026 16:26, Antoniu Miclaus wrote:
> Add support for an optional enable GPIO that allows the multiplexer
> to be disabled before changing address lines and re-enabled after,
> preventing glitches during channel transitions.
>
> This is useful for devices like the Analog Devices ADG2404 (4:1 mux)
> that benefit from enable control to ensure clean channel switching.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> Changes in v4:
> * Add ADG2404 to binding description for discoverability
> * Add dedicated ADG2404 example showing enable-gpios usage
> * Update commit message to reference ADG2404 as use case
>
> ---
> .../devicetree/bindings/mux/gpio-mux.yaml | 25 +++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mux/gpio-mux.yaml b/Documentation/devicetree/bindings/mux/gpio-mux.yaml
> index ef7e33ec85d4..2d9f32012127 100644
> --- a/Documentation/devicetree/bindings/mux/gpio-mux.yaml
> +++ b/Documentation/devicetree/bindings/mux/gpio-mux.yaml
> @@ -17,6 +17,9 @@ description: |+
> multiplexer GPIO pins, where the first pin is the least significant
> bit. An active pin is a binary 1, an inactive pin is a binary 0.
>
> + This binding supports GPIO-controlled multiplexers such as the Analog
> + Devices ADG2404 (4:1 mux with enable control).
> +
> properties:
> compatible:
> const: gpio-mux
> @@ -25,6 +28,13 @@ properties:
> description:
> List of gpios used to control the multiplexer, least significant bit first.
>
> + enable-gpios:
> + description:
> + Optional GPIO to enable the multiplexer. When present, the mux will be
> + disabled before changing address lines and re-enabled after to prevent
> + glitches. Required for MUX_IDLE_DISCONNECT idle-state.
> + maxItems: 1
> +
> mux-supply:
> description:
> Regulator to power on the multiplexer.
> @@ -100,4 +110,19 @@ examples:
> };
> };
> };
> +
> + - |
> + /* Analog Devices ADG2404 4:1 multiplexer with enable control */
> + #include <dt-bindings/gpio/gpio.h>
> +
> + mux-controller {
I did not ask for this. I asked for upstreamed DTS. DTS is a format and
a file - see arch/*/boot/dts/. When I say - upstream DTS - it means you
should make your or any board using this hardware accepted by respective
maintainer. We do not add new examples per every new property, so just
add enable-gpios into existing example.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-16 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 15:26 [PATCH v4 0/2] mux: gpio-mux: add enable GPIO support Antoniu Miclaus
2026-01-16 15:26 ` [PATCH v4 1/2] dt-bindings: mux: gpio-mux: add enable-gpios support Antoniu Miclaus
2026-01-16 16:04 ` Krzysztof Kozlowski [this message]
2026-01-16 15:26 ` [PATCH v4 2/2] mux: gpio-mux: add support for enable GPIO Antoniu Miclaus
2026-01-18 23:18 ` [PATCH v4 0/2] mux: gpio-mux: add enable GPIO support Linus Walleij
2026-01-20 14:28 ` Miclaus, Antoniu
2026-01-21 12:37 ` Linus Walleij
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=a5645b54-7e12-4a42-aac6-9fa517c45ecc@kernel.org \
--to=krzk@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=srini@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
all inboxes | Powered by JetHome®