Re: pinctrl, probe order, and CONFIG_MODULES

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]




On Fri, Aug 29, 2025 at 12:37 PM Phil Elwell <phil@xxxxxxxxxxxxxxx> wrote:
> I eventually traced the failure back to this change:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/pinctrl/devicetree.c?h=next-20250829&id=d19c5e79d46efdf89306be99f3c8824cf58e35f6 
> It introduces a requirement for CONFIG_MODULES to be enabled in order
> to get an EPROBE_DEFER in the event that the pinctrl driver has not
> yet been probed. Without CONFIG_MODULES, the pinctrl requirements are
> waived. Removing the IS_ENABLED(CONFIG_MODULES) clause allows the
> probing of the I2C driver to be deferred, fixing the user's problem.
>
> Is this requirement for supporting modules reasonable? If so, how is
> one supposed to get the pinctrl to probe before the I2C driver?
No deferred probing of pin controllers should absolutely work also when
not using modules.
Send a patch for the above and let us discuss this.
Yours,
Linus Walleij

[Index of Archives] [Linux SPI] [Linux Kernel] [Linux ARM (vger)] [Linux ARM MSM] [Linux Omap] [Linux Arm] [Linux Tegra] [Fedora ARM] [Linux for Samsung SOC] [eCos] [Linux Fastboot] [Gcc Help] [Git] [DCCP] [IETF Announce] [Security] [Linux MIPS] [Yosemite Campsites]

(追記) (追記ここまで)
Powered by Linux

AltStyle によって変換されたページ (->オリジナル) /