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] [thread-next>] [day] [month] [year] [list]

Message-Id: <4af23996-a618-4816-8375-d00748be0700@app.fastmail.com>
Date: Wed, 27 Nov 2024 07:59:31 +0100
From: "Arnd Bergmann" <arnd@...db.de>
To: "Fabio Estevam" <festevam@...il.com>, "Guenter Roeck" <linux@...ck-us.net>
Cc: "Linus Walleij" <linus.walleij@...aro.org>,
 "Esben Haabendal" <esben@...nix.com>, "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>,
 "Rasmus Villemoes" <rasmus.villemoes@...vas.dk>,
 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

On Wed, Nov 27, 2024, at 01:12, Fabio Estevam wrote:
> However, after thinking more about it, I wonder if the patch in
> Subject is worth it.
>
> It can help reduce the kernel size for LS1021A that does not need
> pinctrl, but on the other
> hand, it will cause pain to lots of people who have i.MX products
> running custom defconfigs.

How about moving CONFIG_SOC_LS1021A out of arch/arm/mach-imx/Kconfig
entirely? As far as I can tell, the only file that is even
compiled in there is arch/arm/mach-imx/mach-ls1021a.c, and that
one is not actually required.

I think we can just have an ARCH_LAYERSCAPE entry in
arch/arm/Kconfig.platforms instead, or maybe keep it in
mach-imx/Kconfig but drop the CONFIG_IMX dependency.

The only thing that imx and layerscape seem to share is
the platsmp.c file, which has code for both, but nothing
in there seems shared. Maybe layerscape can just use
enable-method="psci" anyway, if that is implemented by
the firmware?

       Arnd