From: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Peter Rosin <peda@axentia.se>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jonas Jelonek <jelonek.jonas@gmail.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Richard <thomas.richard@bootlin.com>
Subject: Re: [PATCH v7 0/2] add gpio-line-mux
Date: Fri, 2 Jan 2026 11:10:11 +0100 [thread overview]
Message-ID: <176734860604.22824.12173093761003845857.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20251227180134.1262138-1-jelonek.jonas@gmail.com>
On Sat, 27 Dec 2025 18:01:32 +0000, Jonas Jelonek wrote:
> This proposes a new type of virtual GPIO controller and corresponding
> driver to provide a 1-to-many mapping between virtual GPIOs and a single
> real GPIO in combination with a multiplexer. Existing drivers apparently
> do not serve the purpose for what I need.
>
> I came across an issue with a switch device from Zyxel which has two
> SFP+ cages. Most similar switches either wire up the SFP signals
> (RX_LOS, MOD_ABS, TX_FAULT, TX_DISABLE) directly to the SoC (if it has
> enough GPIOs) or two a GPIO expander (for which a driver usually
> exists). However, Zyxel decided to do it differently in the following
> way:
> The signals RX_LOS, MOD_ABS and TX_FAULT share a single GPIO line to
> the SoC. Which one is actually connected to that GPIO line at a time
> is controlled by a separate multiplexer, a GPIO multiplexer in this
> case (which uses two other GPIOs). Only the TX_DISABLE is separate.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: gpio: add gpio-line-mux controller
commit: 2a7618ba8698874e9871a8ec5453e0068e94d9e5
[2/2] gpio: add gpio-line-mux driver
commit: 2b03d9a40cd1fea42fd65d2b66df80edc0f374c8
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
next prev parent reply other threads:[~2026-01-02 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-27 18:01 [PATCH v7 0/2] add gpio-line-mux Jonas Jelonek
2025-12-27 18:01 ` [PATCH v7 1/2] dt-bindings: gpio: add gpio-line-mux controller Jonas Jelonek
2025-12-27 18:01 ` [PATCH v7 2/2] gpio: add gpio-line-mux driver Jonas Jelonek
2026-01-07 8:40 ` Dan Carpenter
2026-01-07 8:52 ` Bartosz Golaszewski
2026-01-02 10:10 ` Bartosz Golaszewski [this message]
2026-01-04 12:11 ` [PATCH v7 0/2] add gpio-line-mux 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=176734860604.22824.12173093761003845857.b4-ty@oss.qualcomm.com \
--to=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jelonek.jonas@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh@kernel.org \
--cc=thomas.richard@bootlin.com \
/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