Lines Matching full:engine

237 * engine to process networking events and core functions
361 	 * Note the LWM2M_RES_DATA_FLAG_RO flag which stops the engine from
371 Lastly, we start the LwM2M RD client (which in turn starts the LwM2M engine).
386 When using DTLS with the LwM2M engine, PSK (Pre-Shared Key) and X.509 certificates are the security…
387 The engine uses LwM2M Security object (Id 0) to read the stored credentials and feed keys from the …
518 LwM2M engine have room for four resources that have cache enabled. Limit can be increased by
520 engine.
544 LwM2M engine and application events
547 The Zephyr LwM2M engine defines events that can be sent back to the application through callback
549 The engine state machine shows when the events are spawned.
554     :alt: LwM2M engine state machine
556     State machine for the LwM2M engine
622        LwM2M engine cannot recover and have stopped.
624 The LwM2M client engine handles most of the state transitions automatically. The application
658      - Engine have stopped as a result of calling :c:func:`lwm2m_rd_client_stop`.
665      - Engine can be resumed by calling :c:func:`lwm2m_engine_resume`.
680 In LwM2M engine, there are three Kconfig options and one runtime value that configures how often the
788     pause   :LwM2M engine thread pause
789     resume  :LwM2M engine thread resume