zephyr/dts/bindings/base
Ederson de Souza eeebb4d911 kernel: Device deferred initialization
Currently, all devices are initialized at boot time (following their
level and priority order). This patch introduces deferred
initialization: by setting the property `zephyr,deferred-init` on a
device on the devicetree, Zephyr will not initialized the device.

To initialize such devices, one has to call `device_init()`.

Deferred initialization is done by grouping all deferred devices on a
different ELF section. In this way, there's no need to consume more
memory to keep track of deferred devices. When `device_init()` is
called, Zephyr will scan the deferred devices section and call the
initialization function for the matching device. As this scanning is
done only during deferred device initialization, its cost should be
bearable.

Signed-off-by: Ederson de Souza <ederson.desouza@intel.com>
2024-04-11 15:50:44 -04:00
..
base.yaml kernel: Device deferred initialization 2024-04-11 15:50:44 -04:00
mutable.yaml device: support for mutable devices 2023-11-28 15:35:39 +01:00
pm.yaml pm: device_runtime: add zephyr,pm-device-runtime-auto 2023-03-29 12:21:13 -04:00
power.yaml dts: bindings: drop remaining "required: false" from bindings 2023-01-04 14:23:53 +01:00
zephyr,memory-attr.yaml dt: Make zephyr,memory-attr a capabilities bitmask 2023-09-15 12:46:54 +02:00
zephyr,memory-region.yaml dts: Move to 'zephyr,memory-attr' 2023-07-25 11:22:10 +02:00