ec3ec8cd2a
Add macro that allows registration of initialization functions that are called when LwM2M engine starts. On LwM2M engine starts up, it first executes all initialization functions in following priority order: 1. LWM2M_PRIO_ENGINE 2. LWM2M_PRIO_CORE, this is where all LwM2M core objects are initialized 3. LWM2M_PRIO_OBJ, this is where all other objects are initialized 4. LwM2M_PRIO_APP, application initialization. Now on the initialization phase, we could rely that certain objects have already been registered. For example custom objects can register callbacks to core objects. On application phase, we can initialize sensor objects and register their callbacks because objects have already been initialized. This LWM2M_ON_INIT() should replace all use of SYS_INIT() with the default CONFIG_KERNEL_INIT_PRIORITY_DEFAULT. Priority order is actually just alphabetical order of names, so the order is set on a linkin phase, and we don't need any runtime checking for it. Signed-off-by: Seppo Takalo <seppo.takalo@nordicsemi.no> |
||
---|---|---|
.. | ||
application_development | ||
arch | ||
benchmarks | ||
bluetooth | ||
boards | ||
boot | ||
bsim | ||
cmake | ||
crypto | ||
drivers | ||
kconfig/configdefault | ||
kernel | ||
lib | ||
misc | ||
modules | ||
net | ||
posix | ||
robot | ||
subsys | ||
unit | ||
ztest | ||
test_config.yaml |