lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <176734860604.22824.12173093761003845857.b4-ty@oss.qualcomm.com>
Date: Fri,  2 Jan 2026 11:10:11 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <brgl@...ev.pl>, Rob Herring <robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley <conor+dt@...nel.org>, Peter Rosin <peda@...ntia.se>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Jonas Jelonek <jelonek.jonas@...il.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>,
        linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Thomas Richard <thomas.richard@...tlin.com>
Subject: Re: [PATCH v7 0/2] add gpio-line-mux


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@....qualcomm.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ