Searched refs:work (Results 926 – 950 of 991) sorted by relevance
1...<<31323334353637383940
90 static void rx_work_handler(struct k_work *work);97 static void init_work(struct k_work *work);4227 static void init_work(struct k_work *work) in init_work() argument4237 static void rx_work_handler(struct k_work *work) in rx_work_handler() argument
27 of the thread's processing. Special macros exist to create and work with297 not the per-CPU interrupt stack. Design work to enable the use of the
369 There are three implementations that work in a similar way, providing a virtual506 is generic in nature and should work with different hardware variants, then it
201 description: Configures USB controllers to work up to a specific speed.430 implicit specifier space naming convention doesn't work. One appropriate
205 work in DTS files, before moving on to a concrete example and providing
155 This **does not always work** since not all drivers use ``DT_DRV_COMPAT``.
2041 static void dhcpv6_timeout(struct k_work *work) in dhcpv6_timeout() argument2047 ARG_UNUSED(work); in dhcpv6_timeout()
228 work with Zephyr applications in most cases. The reason is that there is
36 # files in scripts/dts to make all this work. We also optionally will
143 sample to connect to it, it does require some work on the user's part to
1491 static void signal_interval_timeout(struct k_work *work) in signal_interval_timeout() argument1493 struct k_work_delayable *dwork = k_work_delayable_from_work(work); in signal_interval_timeout()
197 Drivers and applications that are supposed to work in multilevel-interrupt configurations should574 The APIs were marked as callable from usermode but in practice this does not work as the device
321 * :github:`3682` - incremental builds do not work properly in Windows384 * :github:`4182` - NET_APP_SETTINGS for 15.4 doesn't seem to work (if to trust 15.4 shell)
171 ``Tab`` completion do not work.768 backend and the Log RTT backend does not work by default, because both default
73 Also various system services like DHCP and DNS need connection endpoints to work.
154 The *gen_syscall.py* and *parse_syscalls.py* scripts work
85 in the monitored socket, a user supplied work is called.
400 Many of the Bluetooth examples will work on the BL5340 DVK.
573 Many of the Bluetooth examples will work on the BT610.
333 How does it work?
300 CFLAGS and not Kconfig. Added solely to be able to work
96 :c:func:`ring_buf_item_put` and :c:func:`ring_buf_item_get`, and work
385 The newer implementations should be able to work with older ones in backward compatible mode.
31 However, the instructions are generic and will work on other boards unless
229 Required kernel modules must be loaded for RPMSG to work:
