QCLINUX: qcom-dcc: use late_initcall and build as built-in for boot debug

The DCC device stub driver was registered with module_init(), which runs
during the initcall sequence before late_initcall(). The DCC hardware
depends on resources that are not yet available at that point, causing
the driver to fail silently during early boot.

Switch to late_initcall() so the driver initialises after all subsystem
dependencies are ready. Remove the module_exit() registration since the
driver is now built-in only.

Update qcom_debug.config to build CONFIG_QCOM_DCC and CONFIG_QCOM_DCC_DEV
as built-in (=y) instead of loadable modules (=m) to match the
late_initcall() requirement and allow early boot debugging.

Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>

Author: jiegan0107

arch/arm64/configs/qcom_debug.config

@@ -1,4 +1,4 @@
-CONFIG_QCOM_DCC=m
-CONFIG_QCOM_DCC_DEV=m
+CONFIG_QCOM_DCC=y
+CONFIG_QCOM_DCC_DEV=y
 CONFIG_QCOM_MEMORY_DUMP_V2=y
 CONFIG_QCOM_MEMORY_DUMP_DEV=m

drivers/misc/qcom-dcc-dev.c

@@ -959,7 +959,6 @@ static void __exit dcc_dev_exit(void)
 	platform_device_unregister(dcc_pdev);
 }
 
-module_init(dcc_dev_init);
-module_exit(dcc_dev_exit);
+late_initcall(dcc_dev_init);
 MODULE_LICENSE("GPL");
 MODULE_DESCRIPTION("Qualcomm Technologies Inc. DCC driver, device stub");