[qcom-next] configs: qcs615/qcs9100: Enable watchdog autostart

[balajiselvanathan]

Enable watchdog autostart for QCS615 and QCS9100 platforms to ensure the watchdog timer is automatically started during U-Boot initialization.

Please do not submit a Pull Request via github. Our project makes use of
mailing lists for patch submission and review. For more details please
see https://u-boot.readthedocs.io/en/latest/develop/sending_patches.html

Upstream link: https://lore.kernel.org/u-boot/20260526-wdt-v1-1-8236040fe56a@oss.qualcomm.com/

[b49020]

Enable watchdog autostart for QCS615 and QCS9100 platforms to ensure the watchdog timer is automatically started during U-Boot initialization.

Watchdog enabled during boot can be tricky especially if the OS doesn't properly pet in the given watchdog expiry duration. I suppose this is rather better for production environment and not these developer based defconfigs.

[balajiselvanathan]

Enable watchdog autostart for QCS615 and QCS9100 platforms to ensure the watchdog timer is automatically started during U-Boot initialization.

Watchdog enabled during boot can be tricky especially if the OS doesn't properly pet in the given watchdog expiry duration. I suppose this is rather better for production environment and not these developer based defconfigs.

qcom_lemans_defconfig is the production environment right? As customers will use these defconfigs? I agree that if OS doesnt pet its a problem, but 30s timeout is enough? Kernel should have its own watchdog driver to pet right?

[b49020]

Enable watchdog autostart for QCS615 and QCS9100 platforms to ensure the watchdog timer is automatically started during U-Boot initialization.

Watchdog enabled during boot can be tricky especially if the OS doesn't properly pet in the given watchdog expiry duration. I suppose this is rather better for production environment and not these developer based defconfigs.

qcom_lemans_defconfig is the production environment right? As customers will use these defconfigs? I agree that if OS doesnt pet its a problem, but 30s timeout is enough? Kernel should have its own watchdog driver to pet right?

Nope the default defconfig is a generic one which should allow for development as well. Look we aren't enabling secure boot by default in this defconfig too. So, the OEM vendor productizing U-Boot should be able to get these configurations enabled.