Home
last modified time | relevance | path

Searched refs:handler (Results 201 – 225 of 548) sorted by relevance

12345678910>>...22

/Zephyr-latest/doc/kernel/services/threads/
Dworkqueue.rst66 A work item is assigned a **handler function**, which is the function
72 item's handler function and marks it as not pending.
78 item from the queue and invoke the work item's handler function. Depending on
101 A handler function can use any kernel API available to threads. However,
104 its queue until the handler function finishes executing.
106 The single argument that is passed to a handler function can be ignored if it
107 is not required. If the handler function requires additional information about
109 structure. The handler function can then use the argument value to compute the
119 A handler function is permitted to re-submit its work item argument
121 This allows the handler to execute work in stages, without unduly delaying
[all …]
/Zephyr-latest/drivers/usb_c/ppc/
Dusbc_ppc_numaker.c178 static int numaker_ppc_set_event_handler(const struct device *dev, usbc_ppc_event_cb_t handler, in numaker_ppc_set_event_handler() argument
184 return numaker_tcpc_ppc_set_event_handler(tcpc_dev, handler, data); in numaker_ppc_set_event_handler()
/Zephyr-latest/tests/drivers/smbus/smbus_api/src/
Dtest_smbus.c56 .handler = (void *)&dummy, in ZTEST()
101 .handler = (void *)&dummy, in ZTEST()
/Zephyr-latest/drivers/sensor/st/lps2xdf/
Dlps22df.c126 sensor_trigger_handler_t handler) in lps22df_trigger_set() argument
138 lps22df->handler_drdy = handler; in lps22df_trigger_set()
140 if (handler) { in lps22df_trigger_set()
Dlps28dfw.c130 sensor_trigger_handler_t handler) in lps28dfw_trigger_set() argument
145 lps28dfw->handler_drdy = handler; in lps28dfw_trigger_set()
147 if (handler) { in lps28dfw_trigger_set()
/Zephyr-latest/drivers/sensor/st/lis2mdl/
Dlis2mdl.h75 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/sensor/ti/ina23x/
Dina230.h68 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/sensor/honeywell/hmc5883l/
Dhmc5883l.h79 sensor_trigger_handler_t handler);
/Zephyr-latest/include/zephyr/drivers/timer/
Dnrf_grtc_timer.h126 z_nrf_grtc_timer_compare_handler_t handler, void *user_data);
/Zephyr-latest/doc/services/device_mgmt/
Dmcumgr_callbacks.rst35 With the system enabled, a basic handler can be set up and defined in
54 /* Return OK status code to continue with acceptance to underlying handler */
65 This code registers a handler for the :c:enumerator:`MGMT_EVT_OP_CMD_DONE`
74 of the ``MGMT_EVT_OP_*_ALL`` events, alternatively a handler can setup for
135 by a handler will be returned to the MCUmgr client.
152 /* Only run this handler if a previous handler has not failed */
177 /* Return OK status code to continue with acceptance to underlying handler */
188 This code registers a handler for the
208 An example MCUmgr command handler:
251 /* A handler returned a failure code */
/Zephyr-latest/include/zephyr/drivers/
Despi.h432 espi_callback_handler_t handler; member
983 espi_callback_handler_t handler, in espi_init_callback() argument
987 __ASSERT(handler, "Callback handler pointer should not be NULL"); in espi_init_callback()
989 callback->handler = handler; in espi_init_callback()
/Zephyr-latest/drivers/sensor/st/lis2ds12/
Dlis2ds12.h78 sensor_trigger_handler_t handler);
/Zephyr-latest/tests/arch/x86/nmi/
DREADME.txt22 Testing to see interrupt handler executes properly
/Zephyr-latest/tests/ztest/error_hook/
DREADME.txt1 Title: A common fatal error and assert fail handler
6 code writing for fatal and assert handler for error case testing. They can
16 identical code would be written. So we try to move the error handler definition
53 If you use none of them, you can still define your own fatal or assert handler
60 This test verifies if the common fatal error and assert fail handler works.
65 then catch it by the assert handler.
82 - Pass illegal address by syscall, then inside the syscall handler, the
/Zephyr-latest/drivers/comparator/
Dcomparator_shell.c227 entry->handler = NULL; in dsub_set_trigger_lookup_1()
239 entry->handler = NULL; in dsub_set_trigger_lookup_0()
251 entry->handler = NULL; in dsub_device_lookup_0()
/Zephyr-latest/drivers/sensor/ti/tmag5170/
Dtmag5170.h61 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/sensor/st/iis2mdc/
Diis2mdc.h82 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/sensor/st/iis328dq/
Diis328dq.h90 sensor_trigger_handler_t handler);
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_mgmt.rst26 that invokes the registered handler for the corresponding request.
63 register a callback handler at compile time.
73 layer and layer code. A callback handler function **must** check
80 The callback handler function can be shared between different layer events.
172 stack implementation by defining a handler and registering it with an
182 You define your handler modeled with this signature:
/Zephyr-latest/drivers/sensor/st/lps22hh/
Dlps22hh.h85 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/stepper/
Dstepper_shell.c102 entry->handler = NULL; in cmd_stepper_direction()
116 entry->handler = NULL; in cmd_stepper_microstep()
128 entry->handler = NULL; in cmd_pos_stepper_motor_name()
144 entry->handler = NULL; in cmd_pos_stepper_motor_name_dir()
160 entry->handler = NULL; in cmd_pos_stepper_motor_name_microstep()
/Zephyr-latest/drivers/sensor/tdk/mpu6050/
Dmpu6050.h91 sensor_trigger_handler_t handler);
/Zephyr-latest/drivers/mfd/
Dmfd_nxp_lp_flexcomm.c72 LP_FLEXCOMM_PERIPH_T periph, child_isr_t handler) in nxp_lp_flexcomm_setirqhandler() argument
80 child->lp_flexcomm_child_isr = handler; in nxp_lp_flexcomm_setirqhandler()
/Zephyr-latest/drivers/ethernet/
Deth_nxp_s32_netc_priv.h46 .handler = cb, \
102 void (*handler)(uint8_t chan, const uint32 *buf, uint8_t buf_size); member
/Zephyr-latest/drivers/sensor/wsen/wsen_tids_2521020222501/
Dwsen_tids_2521020222501.h76 sensor_trigger_handler_t handler);

12345678910>>...22