linux-kernel - Re: [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl

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: <87plmf6cev.fsf@geanix.com>
Date: Thu, 28 Nov 2024 08:32:56 +0100
From: Esben Haabendal <esben@...nix.com>
To: Fabio Estevam <festevam@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,  Rasmus Villemoes <ravi@...vas.dk>,
  Guenter Roeck <linux@...ck-us.net>,  Linus Walleij
 <linus.walleij@...aro.org>,  Russell King <linux@...linux.org.uk>,  Shawn
 Guo <shawnguo@...nel.org>,  Sascha Hauer <s.hauer@...gutronix.de>,
  Pengutronix Kernel Team <kernel@...gutronix.de>,  Dong Aisheng
 <aisheng.dong@....com>,  Jacky Bai <ping.bai@....com>,
  linux-arm-kernel@...ts.infradead.org,  imx@...ts.linux.dev,
  linux-kernel@...r.kernel.org,  "open list:GPIO SUBSYSTEM"
 <linux-gpio@...r.kernel.org>,  Fabio Estevam <festevam@...x.de>
Subject: Re: [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl

Fabio Estevam <festevam@...il.com> writes:

> On Wed, Nov 27, 2024 at 8:30 AM Arnd Bergmann <arnd@...db.de> wrote:
>
>> Overall, my best advice here is still to not change the way
>> i.MX pinctrl works at all, but just fix Layerscape to not depend
>> on i.MX. The reason for the 'select' here is clearly that the
>> i.MX machines would fail to boot without pinctrl, and changing
>> that because of Layerscape seems backwards.
>
> The suggestion to make Layerscape independent of i.MX makes sense, but
> I don't know if it can be safely applied in 6.13-rc.
>
> This proposed change also has the risk of causing regressions.
>
> What if we revert the patch in Subject for now and then someone (maybe
> Esben) tries again for a proper fix targeting 6.14?

What about your fix to the in-tree imx defconfigs [1]? Was it dropped/rejected?

[1]
https://lore.kernel.org/imx/d718ddd2-d473-4455-b21a-15024e46787c@roeck-us.net/T/#mc71dc21d99e0b013c5ce46c0d90940fd8806ae9a

/Esben