linux-kernel - Re: [BISECTED REGRESSION] OMAP1 GPIO breakage

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: <20230425201117.457f224c@aktux>
Date:   Tue, 25 Apr 2023 20:11:17 +0200
From:   Andreas Kemnade <andreas@...nade.info>
To:     Aaro Koskinen <aaro.koskinen@....fi>
Cc:     linux-omap@...r.kernel.org, linux-gpio@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
        Tony Lindgren <tony@...mide.com>, linux-kernel@...r.kernel.org
Subject: Re: [BISECTED REGRESSION] OMAP1 GPIO breakage

Hi,

On Tue, 25 Apr 2023 20:32:41 +0300
Aaro Koskinen <aaro.koskinen@....fi> wrote:

> Hi,
> 
> It seems GPIOs on OMAP1 boards are somewhat broken after:
> 
> commit 92bf78b33b0b463b00c6b0203b49aea845daecc8
> Author: Andreas Kemnade <andreas@...nade.info>
> Date:   Fri Jan 13 21:59:22 2023 +0100
> 
>     gpio: omap: use dynamic allocation of base
> 
> E.g. on OSK1 the ethernet IRQ cannot (omap_gpio.0) no longer be requested:
> 
> [    0.277252] Error requesting gpio 0 for smc91x irq
> 
> Also the tps65010 (still using static allocation) will now conflict:
> 
> [    0.400726] gpio gpiochip5: Static allocation of GPIO base is deprecated, use dynamic allocation.
> [    0.400848] gpio gpiochip5: (tps65010): GPIO integer space overlap, cannot add chip
> [    0.400970] gpiochip_add_data_with_key: GPIOs 208..214 (tps65010) failed to register, -16
> [    0.401092] tps65010 i2c-tps65010: can't add gpiochip, err -16
> 
> I think this change should be reverted until the board files and other
> gpiochips are fixed accordingly.
> 
well, then just fix that tps65010 thing. 

that change is itself a regression fix for exactly the same kind of error.
twl4030 gpio registration conflicts with omap gpio registration.
Probably in former times, the dynamic allocation always started at 512, 
so no conflicts between static and dynamic.

So I see two options: either fix the remaining static allocation
or fix allocation so there are no overlaps between static and dynamic.

Regards,
Andreas