https://bugzilla.suse.com/show_bug.cgi?id=1215335 https://bugzilla.suse.com/show_bug.cgi?id=1215335#c11 --- Comment #11 from Macpaul Lin <macpaul.lin@mediatek.com> --- (In reply to Chester Lin from comment #8)
(In reply to Macpaul Lin from comment #7)
Thanks for the suggestion and the PR for enabling these regulators.
I've attempted to add these modules into /etc/initramfs-tools/modules. Most of them seem to work without the need for adding softdep. However, I still have some questions regarding this hardware enablement issue.
I assume that this should be in other distros, such as Ubuntu or Debian?
Yes, initramfs-tools is used by Ubuntu and Debian. I've found there are some problem when update driver's dependencies through update-initramfs (includes in package initramfs-tools). I've found dracut is much easier to use for probing drivers and dependencies! With dracut, most of the module dependencies could be detected automatically. Then I could take the dependencies result of 'lsmod' with the 'initrd.img' generated by 'dracut' as a reference for 'initramfs-tools'
Q2. I've discovered that the module mtk_wdt.ko (CONFIG_MEDIATEK_WATCHDOG) must be set as built-in to prevent the system from encountering a hardware reset during the boot process. I've tried building it as a module and installing it into initrd, and I've also attempted to set softdep for it. However, I still can't find it being probed in the initcall debug dump. The system also reboots around 10 seconds into the boot time. After setting CONFIG_MEDIATEK_WATCHDOG=y, the hardware reset issue was resolved and the system was able to boot into the console.
What's the expected timeout to kick the dog? 10 seconds? When did the watchdog device get probed and linked with a driver?
This issue has been clarified with firmware (TF-A) update. No need to built-in watchdog driver anymore. I'll create a new issue for updating recent debug result.
Should I modify it in config/arm64/default from https://github.com/openSUSE/kernel-source and then upload the patch for watchdog issue?
You could but please read the README file before doing it :-)
Got it! -- You are receiving this mail because: You are on the CC list for the bug.