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]

Date:   Thu, 27 Apr 2023 10:03:07 +0300
From:   Tony Lindgren <tony@...mide.com>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Andreas Kemnade <andreas@...nade.info>,
        Aaro Koskinen <aaro.koskinen@....fi>,
        linux-omap@...r.kernel.org, linux-gpio@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [BISECTED REGRESSION] OMAP1 GPIO breakage

* Linus Walleij <linus.walleij@...aro.org> [230426 20:36]:
> On Wed, Apr 26, 2023 at 9:19 AM Tony Lindgren <tony@...mide.com> wrote:
> 
> > Not sure what the best way to fix this might be, adding Linus W to Cc too.
> > Maybe using gpio line names in the legacy platform data instead of numbers?
> 
> I sent a fat invasive fix which, if it works, will fix the problem once and
> for all on OSK1.
> 
> If it works, I can write the same fix for Nokia 770 or whatever.
> 
> I think it is best to just get rid of the static GPIO numbers from these
> boards so I took a stab at that.

OK makes sense to me thanks!

Tony