All of lore.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: "Alexander Stein" <alexander.stein@ew.tq-group.com>
Cc: "Catalin Marinas" <catalin.marinas@arm.com>,
	 "Will Deacon" <will@kernel.org>,
	 "Stefan Wahren" <wahrenst@gmx.net>,
	<linux-arm-kernel@lists.infradead.org>,
	 <linux-kernel@vger.kernel.org>,
	"Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [PATCH 1/1] arm64: Kconfig: Enable PINCTRL on i.MX platforms
Date: Thu, 08 May 2025 08:44:22 +0200	[thread overview]
Message-ID: <87ikmby52x.fsf@geanix.com> (raw)
In-Reply-To: <8259306.DvuYhMxLoT@steina-w> (Alexander Stein's message of "Thu, 08 May 2025 07:52:58 +0200")

"Alexander Stein" <alexander.stein@ew.tq-group.com> writes:

> Hi Stefan,
>
> Am Mittwoch, 7. Mai 2025, 16:30:33 CEST schrieb Stefan Wahren:
>> Hi Alexander,
>>
>> [add Shawn and Esben]
>>
>> Am 07.05.25 um 14:44 schrieb Alexander Stein:
>> > Select PINCTRL for NXP i.MX SoCs.
>> could you please explain the motivation behind your change?
>>
>> Is it related to this commit 17d21001891402 ("ARM: imx: Allow user to
>> disable pinctrl")?
>
> Ah, thanks for the pointer. It might be the case.

The goal of the patch mentioned above was to be able to build a kernel
for LS1021A without pinctrl framework enabled, as LS1021A does not have
a pinctrl driver.

With your patch, that would not be possible anymore.

> I noticed that, when using arch/arm64/defconfig and disabling all
> platforms despite ARCH_MXC before running make olddefconfig,
> CONFIG_PINCTRL gets disabled as well. No platform is enabling it. I
> noticed this when building in yocto and non-IMX platforms are disabled
> for build time reasons.

But is that something that needs to be fixed?

It sounds like quite a special use-case, and why not simply enable
CONFIG_PINCTRL in that case then?

/Esben

>> > Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
>> > ---
>> >   arch/arm64/Kconfig.platforms | 1 +
>> >   1 file changed, 1 insertion(+)
>> >
>> > diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
>> > index a541bb029aa4e..49c3bc25e5f68 100644
>> > --- a/arch/arm64/Kconfig.platforms
>> > +++ b/arch/arm64/Kconfig.platforms
>> > @@ -219,6 +219,7 @@ config ARCH_MXC
>> >   	select ARM64_ERRATUM_845719 if COMPAT
>> >   	select IMX_GPCV2
>> >   	select IMX_GPCV2_PM_DOMAINS
>> > +	select PINCTRL
>> >   	select PM
>> >   	select PM_GENERIC_DOMAINS
>> >   	select SOC_BUS


  reply	other threads:[~2025-05-08  6:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 12:44 [PATCH 1/1] arm64: Kconfig: Enable PINCTRL on i.MX platforms Alexander Stein
2025-05-07 14:30 ` Stefan Wahren
2025-05-08  5:52   ` Alexander Stein
2025-05-08  6:44     ` Esben Haabendal [this message]
2025-05-08  8:07       ` Alexander Stein
2025-05-08  8:18         ` Esben Haabendal
2025-05-08 12:25           ` Alexander Stein
2025-05-08 12:43             ` Esben Haabendal
2025-05-08 13:18               ` Alexander Stein
2025-05-08 17:09                 ` Esben Haabendal
  -- strict thread matches above, loose matches on Subject: below --
2025-05-14 12:19 Alexander Stein

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=87ikmby52x.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=wahrenst@gmx.net \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.