linux-kernel - Re: [PATCH 1/7] pinctrl: armada-37xx: use correct OUTPUT

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: <d5fa1e79-8204-464c-b12d-de8e59411146@lunn.ch>
Date: Mon, 12 May 2025 23:28:25 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Gabor Juhos <j4g8y7@...il.com>
Cc: Gregory Clement <gregory.clement@...tlin.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	linux-arm-kernel@...ts.infradead.org, linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Imre Kaloz <kaloz@...nwrt.org>
Subject: Re: [PATCH 1/7] pinctrl: armada-37xx: use correct OUTPUT_VAL
 register for GPIOs > 31

On Mon, May 12, 2025 at 04:22:37PM +0200, Gabor Juhos wrote:
> The controller has two consecutive OUTPUT_VAL registers and both
> holds output value for 32 GPIOs. Due to a missing adjustment, the
> current code always uses the first register while setting the
> output value whereas it should use the second one for GPIOs > 31.
> 
> Add the missing armada_37xx_update_reg() call to adjust the register
> according to the 'offset' parameter of the function to fix the issue.
> 
> Cc: stable@...r.kernel.org
> Fixes: 6702abb3bf23 ("pinctrl: armada-37xx: Fix direction_output() callback behavior")
> Signed-off-by: Gabor Juhos <j4g8y7@...il.com>
> Signed-off-by: Imre Kaloz <kaloz@...nwrt.org>

Reviewed-by: Andrew Lunn <andrew@...n.ch>

    Andrew