linux-kernel - Re: [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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdZyyjLjnfqT7Vq8VvzP7bbT+b1s0y142ODEhiK-thButw@mail.gmail.com>
Date: Tue, 21 Oct 2025 09:15:50 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: William Breathitt Gray <wbg@...nel.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	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: [PATCH v2 0/3] gpio: idio-16: Fix regmap initialization errors

On Mon, Oct 20, 2025 at 10:52 AM William Breathitt Gray <wbg@...nel.org> 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.
>
> Link: https://lore.kernel.org/r/cover.1680618405.git.william.gray@linaro.org
> Closes: https://lore.kernel.org/r/9b0375fd-235f-4ee1-a7fa-daca296ef6bf@nutanix.com
> Signed-off-by: William Breathitt Gray <wbg@...nel.org>

The series:
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij