ANDROID: ion heap: init ion heaps in subsys_initcall

Some built-in modules will failed to use ion heap to allocate memory
if the ion heap drivers are too late to be initialized.
To fix this issue, move initialization of ion heap drivers in subsys_initcall()
which is more earlier to be called.

Bug: 203487618
Signed-off-by: Shuosheng Huang <huangshuosheng@allwinnertech.com>
Change-Id: If120225fd6c3b665053857cc9345db4521e76cf8
(cherry picked from commit eb4a5a5dbd5bcc33db06d4515653b7f67a2e927e)
This commit is contained in:
Shuosheng Huang
2021-10-19 15:32:13 +08:00
committed by shuosheng huang
parent 3dbc1d366e
commit 160ab93103
2 changed files with 2 additions and 2 deletions

View File

@@ -146,6 +146,6 @@ static void __exit ion_cma_heap_exit(void)
ion_device_remove_heap(&cma_heaps[nr].heap);
}
module_init(ion_cma_heap_init);
subsys_initcall(ion_cma_heap_init);
module_exit(ion_cma_heap_exit);
MODULE_LICENSE("GPL v2");

View File

@@ -293,6 +293,6 @@ static void __exit ion_system_heap_exit(void)
ion_system_heap_destroy_pools(system_heap.pools);
}
module_init(ion_system_heap_init);
subsys_initcall(ion_system_heap_init);
module_exit(ion_system_heap_exit);
MODULE_LICENSE("GPL v2");