From: Krzysztof Kozlowski <krzk@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Lee Jones <lee@kernel.org>,
Peter Rosin <peda@axentia.se>, Linus Walleij <linusw@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-gpio@vger.kernel.org, David Jander <david@protonic.nl>
Subject: Re: [PATCH v1 7/8] dt-bindings: mux: add NXP MC33978/MC34978 AMUX
Date: Thu, 26 Feb 2026 09:14:21 +0100 [thread overview]
Message-ID: <20260226-clever-rustling-dolphin-871aff@quoll> (raw)
In-Reply-To: <20260225171545.1980385-8-o.rempel@pengutronix.de>
On Wed, Feb 25, 2026 at 06:15:40PM +0100, Oleksij Rempel wrote:
> +description: |
> + The MC33978 and MC34978 include a 24-to-1 analog multiplexer (AMUX) that
> + routes one of the following signals to an external AMUX pin for measurement
> + by an external ADC:
> +
> + - Channels 0-13: SG0-SG13 switch input voltages
> + - Channels 14-21: SP0-SP7 switch input voltages
> + - Channel 22: Internal temperature diode
> + - Channel 23: Battery voltage (VBATP)
> +
> + The AMUX requires a settling time of up to 200 us for full-scale voltage
> + steps. Consumers (e.g., io-channel-mux) must configure this delay.
> +
> +properties:
> + compatible:
> + enum:
> + - nxp,mc33978-mux
> + - nxp,mc34978-mux
> +
> + '#mux-control-cells':
> + const: 0
No resources here, so this should not be separate device node but folded
into the parent.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-26 8:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 17:15 [PATCH v1 0/8] mfd: Add support for NXP MC33978/MC34978 MSDI Oleksij Rempel
2026-02-25 17:15 ` [PATCH v1 1/8] dt-bindings: mfd: add " Oleksij Rempel
2026-02-26 8:16 ` Krzysztof Kozlowski
2026-02-25 17:15 ` [PATCH v1 2/8] mfd: add NXP MC33978/MC34978 core driver Oleksij Rempel
2026-02-25 17:15 ` [PATCH v1 3/8] dt-bindings: pinctrl: add NXP MC33978/MC34978 pinctrl Oleksij Rempel
2026-02-26 23:00 ` Linus Walleij
2026-02-26 23:02 ` Linus Walleij
2026-02-27 10:41 ` Oleksij Rempel
2026-02-27 14:06 ` Linus Walleij
2026-02-27 10:04 ` Oleksij Rempel
2026-02-25 17:15 ` [PATCH v1 4/8] pinctrl: add NXP MC33978/MC34978 pinctrl driver Oleksij Rempel
2026-02-26 23:40 ` Linus Walleij
2026-02-27 10:58 ` Oleksij Rempel
2026-02-27 14:08 ` Linus Walleij
2026-02-25 17:15 ` [PATCH v1 5/8] dt-bindings: hwmon: add NXP MC33978/MC34978 hwmon Oleksij Rempel
2026-02-26 8:17 ` Krzysztof Kozlowski
2026-02-25 17:15 ` [PATCH v1 6/8] hwmon: add NXP MC33978/MC34978 driver Oleksij Rempel
2026-02-25 17:15 ` [PATCH v1 7/8] dt-bindings: mux: add NXP MC33978/MC34978 AMUX Oleksij Rempel
2026-02-26 8:14 ` Krzysztof Kozlowski [this message]
2026-02-25 17:15 ` [PATCH v1 8/8] mux: add NXP MC33978/MC34978 AMUX driver Oleksij Rempel
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=20260226-clever-rustling-dolphin-871aff@quoll \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=o.rempel@pengutronix.de \
--cc=peda@axentia.se \
--cc=robh@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