linux-kernel - Re: [PATCH] pinctrl: at91: make it work with current gpiolib

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: <CACRpkdZZu4i_DPx9hZp1NXBv=4YBvknrMdaKni1vDeHb5+_rFg@mail.gmail.com>
Date: Fri, 23 Aug 2024 17:32:37 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: thomas.blocher@...dev.de
Cc: Ludovic Desroches <ludovic.desroches@...rochip.com>, 
	Nicolas Ferre <nicolas.ferre@...rochip.com>, 
	Alexandre Belloni <alexandre.belloni@...tlin.com>, Claudiu Beznea <claudiu.beznea@...on.dev>, 
	linux-arm-kernel@...ts.infradead.org, linux-gpio@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pinctrl: at91: make it work with current gpiolib

On Wed, Jul 31, 2024 at 1:16 AM Thomas Blocher <thomas.blocher@...dev.de> wrote:

> pinctrl-at91 currently does not support the gpio-groups devicetree
> property and has no pin-range.
> Because of this at91 gpios stopped working since patch
> commit 2ab73c6d8323fa1e ("gpio: Support GPIO controllers without pin-ranges")
> This was discussed in the patches
> commit fc328a7d1fcce263 ("gpio: Revert regression in sysfs-gpio (gpiolib.c)")
> commit 56e337f2cf132632 ("Revert "gpio: Revert regression in sysfs-gpio (gpiolib.c)"")
>
> As a workaround manually set pin-range via gpiochip_add_pin_range() until
> a) pinctrl-at91 is reworked to support devicetree gpio-groups
> b) another solution as mentioned in
> commit 56e337f2cf132632 ("Revert "gpio: Revert regression in sysfs-gpio (gpiolib.c)"")
> is found
>
> Signed-off-by: Thomas Blocher <thomas.blocher@...dev.de>

No reaction from maintainers so patch applied for fixes now.

Yours,
Linus Walleij