From: Rob Herring <robh@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: Peter Rosin <peda@axentia.se>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mux: adg2404: add support for ADG2404 multiplexer
Date: Tue, 6 Jan 2026 13:05:10 -0600 [thread overview]
Message-ID: <20260106190510.GA2546640-robh@kernel.org> (raw)
In-Reply-To: <20260105120117.57607-1-antoniu.miclaus@analog.com>
On Mon, Jan 05, 2026 at 02:00:29PM +0200, Antoniu Miclaus wrote:
> This series adds support for the Analog Devices ADG2404, a 4:1 analog
> multiplexer with low 0.62Ω on-resistance.
>
> The ADG2404 features:
> - Low RON of 0.62Ω
> - Flat RON across signal range (0.003Ω)
> - Dual supply operation (±15V, ±5V)
> - Single supply operation (+12V)
> - Asymmetric supply support (+5V/-12V)
> - 1.8V/3.3V/5V logic compatibility
> - Break-before-make switching
>
> Applications include automatic test equipment, data acquisition,
> instrumentation, audio/video switching, and communication systems.
Isn't this just a gpio-mux with the addition of an enable GPIO line?
Wouldn't adding enable-gpios and support for it in the gpio-mux driver
work?
Rob
next prev parent reply other threads:[~2026-01-06 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 12:00 [PATCH v2 0/2] mux: adg2404: add support for ADG2404 multiplexer Antoniu Miclaus
2026-01-05 12:00 ` [PATCH v2 1/2] dt-bindings: mux: adg2404: add support Antoniu Miclaus
2026-01-05 12:00 ` [PATCH v2 2/2] mux: adg2404: add driver support Antoniu Miclaus
2026-01-06 19:05 ` Rob Herring [this message]
2026-01-07 8:33 ` [PATCH v2 0/2] mux: adg2404: add support for ADG2404 multiplexer Peter Rosin
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=20260106190510.GA2546640-robh@kernel.org \
--to=robh@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
/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