Home
last modified time | relevance | path

Searched refs:autohandler (Results 1 – 6 of 6) sorted by relevance

/Zephyr-latest/subsys/mgmt/hawkbit/
Dhawkbit_autohandler.c15 static void autohandler(struct k_work *work);
17 static K_WORK_DELAYABLE_DEFINE(hawkbit_work_handle, autohandler);
18 static K_WORK_DELAYABLE_DEFINE(hawkbit_work_handle_once, autohandler);
22 static void autohandler(struct k_work *work) in autohandler() function
DKconfig38 bool "hawkBit autohandler"
42 Activate autohandler to handle the update process automatically.
/Zephyr-latest/subsys/mgmt/updatehub/
Dupdatehub.c998 static void autohandler(struct k_work *work) in autohandler() function
1044 k_work_init_delayable(&updatehub_work_handle, autohandler); in z_impl_updatehub_autohandler()
/Zephyr-latest/doc/releases/
Drelease-notes-4.0.rst1248 autohandler will reshedule itself after running. If the argument is set to false, the
1249 autohandler will not reshedule itself. Both variants are scheduled independent of each other.
1250 The autohandler always runs in the system workqueue.
1252 * Use the :c:func:`hawkbit_autohandler_wait` function to wait for the autohandler to finish.
1256 * Use the :c:func:`hawkbit_autohandler_cancel` function to cancel the autohandler.
1259 autohandler.
1262 ``<zephyr/mgmt/hawkbit/hawkbit.h>``, the autohandler header file is now
1263 ``<zephyr/mgmt/hawkbit/autohandler.h>`` and the configuration header file is now
Dmigration-guide-4.0.rst540 The hawkbit autohandler has been separated into ``<zephyr/mgmt/hawkbit/autohandler.h>``.
Drelease-notes-3.7.rst1664 * When using the hawkBit autohandler and an update is installed, the device will now