Why doesn't the Linux kernel module load after the device-tree overlay is applied through configfs?

edit

There can be various reasons why the Linux kernel module does not load after the device-tree overlay is applied through configfs:

1. Configuration Errors: There can be some configuration errors in the device-tree overlay or configfs that may prevent the proper loading of the kernel module. For example, there may be errors in the syntax or structure of the overlay file, missing or incorrect properties in the device-tree, missing permissions for the overlay file, and so on.

2. Kernel Compatibility: The kernel module may not be compatible with the kernel version running on the system. The module may require a specific kernel version or architecture to run, and if the version or architecture does not match, the module may fail to load.

3. Conflicting Device Drivers: There may be conflicting device drivers that are preventing the module from loading. For example, there may be other drivers that are already loaded or bound to the same device, and these may be conflicting with the kernel module.

4. Missing Dependencies: The kernel module may have dependencies that are missing or not installed in the system. If the dependencies are not present, the module may fail to load or may load but not function properly.

5. Hardware or Firmware Issues: There may be some hardware or firmware issues with the device that are preventing the module from loading. For example, there may be some issues with the device driver firmware, hardware incompatibilities, or even issues with the device itself.