From: Fabio Estevam <festevam@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Esben Haabendal <esben@geanix.com>,
Russell King <linux@armlinux.org.uk>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Dong Aisheng <aisheng.dong@nxp.com>,
Jacky Bai <ping.bai@nxp.com>, Arnd Bergmann <arnd@arndb.de>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl
Date: Tue, 26 Nov 2024 21:12:58 -0300 [thread overview]
Message-ID: <CAOMZO5DW3t-sof_uaFa_qJPE3WFq_155mFTxGMWh0m++csgopg@mail.gmail.com> (raw)
In-Reply-To: <1ff005f8-384d-465e-9597-b6d5fd903862@roeck-us.net>
On Tue, Nov 26, 2024 at 8:53 PM Guenter Roeck <linux@roeck-us.net> wrote:
> My understanding (which may be wrong) is that being able to disable
> PINCTRL was the whole point of the patch.
Exactly.
Adding back the "select PINCTRL" line defeats the purpose of the patch
in Subject.
> Fabio submitted a patch enabling PINCTRL for imx_v4_v5_defconfig and
> imx_v6_v7_defconfig explicitly [1]. I don't know if that fixes the
> problem for good - I see CONFIG_ARCH_MXC in other configurations as
> well.
Good point. I can send a v2 adding CONFIG_PINCTRL=y to the other defconfigs.
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.
When they update their kernel to 6.13-rc1 their i.MX will not boot and
that will be a very unpleasant experience.
What do you think?
Should we go with the approach of selecting CONFIG_PINCTRL=y or
should we revert this patch?
IMHO, the benefit of this patch does not justify the bad impact on users.
next prev parent reply other threads:[~2024-11-27 0:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 10:23 [PATCH v2 0/3] ARM: imx: only enable pinctrl as needed Esben Haabendal
2024-05-06 10:23 ` [PATCH v2 1/3] ARM: imx: Allow user to disable pinctrl Esben Haabendal
2024-06-03 2:50 ` Shawn Guo
2024-09-13 7:21 ` Esben Haabendal
2024-09-24 7:45 ` Linus Walleij
2024-09-26 7:28 ` Esben Haabendal
2024-09-26 8:40 ` Shawn Guo
2024-11-26 16:17 ` Guenter Roeck
2024-11-26 21:24 ` Linus Walleij
2024-11-26 23:53 ` Guenter Roeck
2024-11-27 0:12 ` Fabio Estevam [this message]
2024-11-27 6:59 ` Arnd Bergmann
2024-11-27 9:13 ` Rasmus Villemoes
2024-11-27 9:18 ` Arnd Bergmann
2024-11-27 10:13 ` Rasmus Villemoes
2024-11-27 11:29 ` Arnd Bergmann
2024-11-27 14:36 ` Fabio Estevam
2024-11-28 7:32 ` Esben Haabendal
2024-05-06 10:23 ` [PATCH v2 2/3] pinctrl: freescale: Use CONFIG_SOC_IMXRT to guard i.MX RT1xxx drivers Esben Haabendal
2024-05-06 11:29 ` Arnd Bergmann
2024-05-07 7:37 ` Esben Haabendal
2024-05-07 7:43 ` Arnd Bergmann
2024-05-06 10:23 ` [PATCH v2 3/3] pinctrl: freescale: enable use with COMPILE_TEST Esben Haabendal
2024-05-27 11:05 ` [PATCH v2 0/3] ARM: imx: only enable pinctrl as needed Linus Walleij
2024-10-01 11:55 ` Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOMZO5DW3t-sof_uaFa_qJPE3WFq_155mFTxGMWh0m++csgopg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=aisheng.dong@nxp.com \
--cc=arnd@arndb.de \
--cc=esben@geanix.com \
--cc=festevam@denx.de \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@roeck-us.net \
--cc=ping.bai@nxp.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).