From: Tom Rini <trini@konsulko.com>
To: Sumit Garg <sumit.garg@kernel.org>
Cc: Aswin Murugan <aswin.murugan@oss.qualcomm.com>,
casey.connolly@linaro.org, neil.armstrong@linaro.org,
ilias.apalodimas@linaro.org, christopher.obbard@linaro.org,
quic_varada@quicinc.com, me@samcday.com,
marek.vasut+renesas@mailbox.org, alexeymin@postmarketos.org,
u-boot-qcom@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/2] pinctrl: qcom: Make pinctrl drivers default y
Date: Fri, 26 Dec 2025 08:56:29 -0600 [thread overview]
Message-ID: <20251226145629.GC710860@bill-the-cat> (raw)
In-Reply-To: <aU5JPlsbh-ER7Den@sumit-xelite>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
On Fri, Dec 26, 2025 at 02:07:18PM +0530, Sumit Garg wrote:
> On Mon, Dec 22, 2025 at 05:21:42PM +0530, Aswin Murugan wrote:
> > This is a follow-up patch series to address review feedback on the
> > QCS615 pinctrl driver addition:
> > https://lore.kernel.org/u-boot/20251112164758.1560041-1-aswin.murugan@oss.qualcomm.com/
> >
> > During review, it was suggested that since all Qualcomm pinctrl
> > drivers are already within a menu conditional on ARCH_SNAPDRAGON ||
> > ARCH_IPQ40XX, they should be made default y based on the appropriate
> > architecture rather than requiring manual enablement in defconfig
> > files.
> >
> > This series implements that suggestion by:
> > 1. Adding 'default y if ARCH_SNAPDRAGON' to all Snapdragon pinctrl
> > drivers and 'default y if ARCH_IPQ40XX' to all IPQ pinctrl
> > drivers in the Kconfig
>
> I see the usefullness of this feature but in turn it will limit the
> capability to reduce U-Boot size to an essential minimum. In scenarios
> where there are contraints on flash size or on-chip RAM for U-Boot SPL.
> I would rather favour something like following like:
>
> 'default y if PINCTRL_QCOM_GENERIC'
>
> where PINCTRL_QCOM_GENERIC can be enabled from generic Qcom defconfig.
If something is merely "default y" it can still be easily turned off. If
we want to make the "if ..." part more precise, OK. But I don't want to
go back to (nearly?) every snapdragon and ipq40xx defconfig being
modified, as it was in an earlier iteration.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-12-26 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 11:51 [PATCH v1 0/2] pinctrl: qcom: Make pinctrl drivers default y Aswin Murugan
2025-12-22 11:51 ` [PATCH v1 1/2] pinctrl: qcom: Make pinctrl drivers default y based on architecture Aswin Murugan
2025-12-22 11:51 ` [PATCH v1 2/2] configs: qcom_defconfig: Remove redundant pinctrl driver selections Aswin Murugan
2025-12-26 8:37 ` [PATCH v1 0/2] pinctrl: qcom: Make pinctrl drivers default y Sumit Garg
2025-12-26 14:56 ` Tom Rini [this message]
2025-12-29 4:16 ` Sumit Garg
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=20251226145629.GC710860@bill-the-cat \
--to=trini@konsulko.com \
--cc=alexeymin@postmarketos.org \
--cc=aswin.murugan@oss.qualcomm.com \
--cc=casey.connolly@linaro.org \
--cc=christopher.obbard@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=me@samcday.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_varada@quicinc.com \
--cc=sumit.garg@kernel.org \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/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