44acfc22c7
When building the Surface Aggregator Module (SAM) core, registry, and
other SAM client drivers as builtin modules (=y), proper initialization
order is not guaranteed. Due to this, client driver registration
(triggered by device registration in the registry) races against bus
initialization in the core.
If any attempt is made at registering the device driver before the bus
has been initialized (i.e. if bus initialization fails this race) driver
registration will fail with a message similar to:
Driver surface_battery was unable to register with bus_type surface_aggregator because the bus was not initialized
Switch from module_init() to subsys_initcall() to resolve this issue.
Note that the serdev subsystem uses postcore_initcall() so we are still
able to safely register the serdev device driver for the core.
Fixes:
|
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| bus.c | ||
| bus.h | ||
| controller.c | ||
| controller.h | ||
| core.c | ||
| ssh_msgb.h | ||
| ssh_packet_layer.c | ||
| ssh_packet_layer.h | ||
| ssh_parser.c | ||
| ssh_parser.h | ||
| ssh_request_layer.c | ||
| ssh_request_layer.h | ||
| trace.h | ||