Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: 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>,
	Johan Hovold <johan+linaro@kernel.org>,
	 David Lechner <dlechner@baylibre.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] mux: gpio-mux: add enable GPIO support and ADG2404
Date: Fri, 16 Jan 2026 09:37:36 +0100	[thread overview]
Message-ID: <20260116-jumping-premium-crow-693a1c@quoll> (raw)
In-Reply-To: <20260115121943.23715-1-antoniu.miclaus@analog.com>

On Thu, Jan 15, 2026 at 02:18:18PM +0200, Antoniu Miclaus wrote:
> This series extends the gpio-mux driver with optional enable GPIO support
> to prevent glitches during channel transitions, then adds support for the
> Analog Devices ADG2404 multiplexer as the first user of this feature.
> 
> The enable GPIO allows the multiplexer to be disabled before changing
> address lines and re-enabled after, preventing brief activation of
> unintended channels during transitions. This is particularly important
> for precision analog applications.
> 
> The ADG2404 is a 4:1 analog multiplexer with low 0.62Ω on-resistance
> that requires this enable GPIO functionality for glitch-free operation.
> 
> Changes in v3:
>  * Extend gpio-mux driver instead of creating standalone adg2404 driver
>  * Make enable GPIO optional for backward compatibility
>  * Add MUX_IDLE_DISCONNECT support via enable GPIO

You are developing on some old kernel. You got stale Cc list of at least
three people! How could you for example get "johan+linaro@kernel.org" -
from which maintainer entry - but that at least is not bouncing like two
others.

You must use get_maintainers, not custom templates with fixed outdated
addresses.

Best regards,
Krzysztof


  parent reply	other threads:[~2026-01-16  8:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 12:18 [PATCH v3 0/4] mux: gpio-mux: add enable GPIO support and ADG2404 Antoniu Miclaus
2026-01-15 12:18 ` [PATCH v3 1/4] dt-bindings: mux: gpio-mux: add enable-gpios support Antoniu Miclaus
2026-01-16  8:30   ` Krzysztof Kozlowski
2026-01-15 12:18 ` [PATCH v3 2/4] mux: gpio-mux: add support for enable GPIO Antoniu Miclaus
2026-01-15 12:18 ` [PATCH v3 3/4] dt-bindings: mux: gpio-mux: add adi,adg2404 support Antoniu Miclaus
2026-01-16  8:29   ` Krzysztof Kozlowski
2026-01-16  8:34     ` Krzysztof Kozlowski
2026-01-15 12:18 ` [PATCH v3 4/4] " Antoniu Miclaus
2026-01-16  8:32   ` Krzysztof Kozlowski
2026-01-16  8:34     ` Krzysztof Kozlowski
2026-01-16  9:48     ` Miclaus, Antoniu
2026-01-16 10:42       ` Krzysztof Kozlowski
2026-01-16  8:37 ` Krzysztof Kozlowski [this message]
2026-01-16  9:00   ` [PATCH v3 0/4] mux: gpio-mux: add enable GPIO support and ADG2404 Johan Hovold
2026-01-16  9:39     ` Miclaus, Antoniu
2026-01-16 10:31       ` Krzysztof Kozlowski
2026-01-16 15:26         ` Miclaus, Antoniu
2026-01-16 16:06           ` Krzysztof Kozlowski
2026-01-16 16:17             ` Miclaus, Antoniu

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=20260116-jumping-premium-crow-693a1c@quoll \
    --to=krzk@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=johan+linaro@kernel.org \
    --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