linux-kernel - Re: (subset) [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors

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] [day] [month] [year] [list]

Message-ID: <176111605268.7660.15686618336635662485.b4-ty@linaro.org>
Date: Wed, 22 Oct 2025 08:54:22 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	William Breathitt Gray <wbg@...nel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Michael Walle <mwalle@...nel.org>,
	Ioana Ciornei <ioana.ciornei@....com>,
	Mark Brown <broonie@...nel.org>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Mark Cave-Ayland <mark.caveayland@...anix.com>,
	stable@...r.kernel.org
Subject: Re: (subset) [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Mon, 20 Oct 2025 17:51:43 +0900, William Breathitt Gray wrote:
> The migration of IDIO-16 GPIO drivers to the regmap API resulted in some
> regressions to the gpio-104-idio-16, gpio-pci-idio-16, and gpio-idio-16
> modules. Specifically, the 104-idio-16 and pci-idio-16 GPIO drivers
> utilize regmap caching and thus must set max_register for their
> regmap_config, while gpio-idio-16 requires fixed_direction_output to
> represent the fixed direction of the IDIO-16 GPIO lines. Fixes for these
> regressions are provided by this series.
> 
> [...]

Applied, thanks!

[3/3] gpio: idio-16: Define fixed direction of the GPIO lines
      https://git.kernel.org/brgl/linux/c/2ba5772e530f73eb847fb96ce6c4017894869552

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>