[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOMZO5BY56N9Sfm1_qprQm7jeM+5bLgR0CPeu3kXK9rgmJN87Q@mail.gmail.com>
Date: Wed, 27 Nov 2024 11:36:46 -0300
From: Fabio Estevam <festevam@...il.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Rasmus Villemoes <ravi@...vas.dk>, Guenter Roeck <linux@...ck-us.net>,
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>,
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 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?
Powered by blists - more mailing lists