Enanle PINCTRL_SINGLE for bcm2712_defconfig

[Cyanoxygen]

Raspberry Pi 5B will not boot from SD card without PINCTRL_SINGLE since Linux 7.0:

[ 17.888687] platform 107d50c000.serial: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d504100/bt_shutdown_pins
[ 17.888693] platform pwr_button: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d504100/pwr_button_pins
[ 17.888697] platform 107d004000.spi: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d504100/spi10_cs_gpio1
[ 17.888699] platform wl-on-reg: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d504100/wl_on_pins
[ 17.888701] platform 1000fff000.mmc: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d510700/emmc_aon_cd_pins
[ 17.888704] platform 1001100000.mmc: deferred probe pending: platform: wait for supplier /soc@107c000000/pinctrl@7d504100/sdio2_30_pins
[ 30.688427] vcc-sd: disabling

[pelwell]

My Raspberry Pi 5 is booting happily from SD with top-of-tree rpi-7.0.y. I can't see any way in which the presence of the pinctrl-single (pcs) driver would make any difference - it's a platform driver, and the compatible string is not mentioned in the Pi 5 dts files. To be sure I'd not missed anything, I rebuilt with CONFIG_PINCTRL_SINGLE=y and found that the driver's probe function is never called.

Please explain how you came to this diagnosis and remedy.

[Cyanoxygen]

Hi,

My Raspberry Pi 5 is booting happily from SD with top-of-tree rpi-7.0.y. I can't see any way in which the presence of the pinctrl-single (pcs) driver would make any difference - it's a platform driver, and the compatible string is not mentioned in the Pi 5 dts files.

I was wondering the same thing, but I at the time I couldn't find out why it happened.

To be sure I'd not missed anything, I rebuilt with CONFIG_PINCTRL_SINGLE=y and found that the driver's probe function is never called.

Please explain how you came to this diagnosis and remedy.

I came to this conclusion by trial and error, and came to this conclusion after a few configuration changes.

I cleaned up the boot partition, reapplied the device tree, overlay files and the kernel, after then it booted fine, so now I think it is a fluke 😂 . I will dig deeply tomorrow. Thanks!