Hi, to clear up some confusion: On Qualcomm boards GPIOs that are used for "secure" (duh) peripherals, like a fingerprint scanner, are not allowed to be controlled from Linux (the "non-secure world"). Trying to do so causes an immediate reboot due to "attempting to violate the security". The GPIOs seem to all be iterated over on boot, except for the ones specified in "gpio-reserved-ranges". As a result, if such "secure" GPIOs are not declared in the DT, the board essentially dies on TLMM (pinctrl) probe (which happens veeeery early - so that all other peripherals can set the pins as they see fit) and that's very unpleasant to debug. Without this patch, Petr's device will simply not boot. So, why did it work before!? Well, either the GPIOs weren't iterated over, or the TLMM (pinctrl) driver wasn't in place back then. As for the initrd crash.. perhaps you have an Android initrd which dies as soon as it doesn't detect SELINUX and a couple of other options.. You might want to try postmarketOS's one, or any other Linux distro's armv7/aarch64 initrd. To replace it, simply use abootimg like so: abootimg -u boot.img -r ramdisk.img If it says something something "too small", add -c "bootsize=30000000" to make the boot.img exactly 30 million bytes (or change it as you see fit). Konrad
