From: Tapio Reijonen <tapio.reijonen@vaisala.com>
To: Peter Rosin <peda@axentia.se>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Tapio Reijonen <tapio.reijonen@vaisala.com>
Subject: [PATCH 0/2] mux: gpio: Add external mux enable gpio
Date: Wed, 05 Nov 2025 14:49:11 +0000 [thread overview]
Message-ID: <20251105-add-external-mux-enable-gpio-v1-0-e59cba6f9e47@vaisala.com> (raw)
The output state of a mux might be misinterpreted
during transition from one state to another.
Using a dedicated optional gpio pin, the validity
of the mux state can be communicated to connected devices.
This series adds support for defining the optional
gpio pin for this purpose, along with documentation.
Signed-off-by: Tapio Reijonen <tapio.reijonen@vaisala.com>
---
Tapio Reijonen (2):
dt-bindings: mux: Add description for enable GPIO
mux: gpio: Add external mux enable gpio
.../devicetree/bindings/mux/gpio-mux.yaml | 5 ++++
drivers/mux/gpio.c | 30 +++++++++++++++++-----
2 files changed, 29 insertions(+), 6 deletions(-)
---
base-commit: e53642b87a4f4b03a8d7e5f8507fc3cd0c595ea6
change-id: 20250925-add-external-mux-enable-gpio-c9ba5beddd49
Best regards,
--
Tapio Reijonen <tapio.reijonen@vaisala.com>
next reply other threads:[~2025-11-05 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:49 Tapio Reijonen [this message]
2025-11-05 14:49 ` [PATCH 1/2] dt-bindings: mux: Add description for enable GPIO Tapio Reijonen
2025-11-06 9:08 ` Krzysztof Kozlowski
2025-11-06 11:55 ` Tapio Reijonen
2025-11-06 12:18 ` Krzysztof Kozlowski
2025-11-05 14:49 ` [PATCH 2/2] mux: gpio: Add external mux enable gpio Tapio Reijonen
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=20251105-add-external-mux-enable-gpio-v1-0-e59cba6f9e47@vaisala.com \
--to=tapio.reijonen@vaisala.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).