Searched refs:thread (Results 501 – 525 of 920) sorted by relevance
1...<<21222324252627282930>>...37
| /Zephyr-latest/drivers/sensor/ams/tsl2540/ |
| D | tsl2540_trigger.c | 196 k_thread_create(&data->thread, data->thread_stack, CONFIG_TSL2540_THREAD_STACK_SIZE, in tsl2540_trigger_init()
199 k_thread_name_set(&data->thread, "TSL2540 trigger"); in tsl2540_trigger_init()
|
| /Zephyr-latest/subsys/mgmt/ec_host_cmd/ |
| D | Kconfig | 21 int "Stack size for the EC host command handler thread"
98 The ec_host_cmd_init function creates a new thread dedicated for Host Command.
99 Otherwise the ec_host_cmd_task function has to be called within another thread.
|
| /Zephyr-latest/drivers/modem/ |
| D | Kconfig.ublox-sara-r4 | 42 int "Stack size for the u-blox SARA-R4 modem driver RX thread"
45 This stack is used by the u-blox SARA-R4 RX thread.
52 to the rest of the network stack, letting the rx thread continue
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.stm32_hal | 45 int "RX thread stack size"
48 RX thread stack size
56 With pre-emptive threads, the thread can be pre-empted.
62 This option allows to configure the priority of the RX thread that
|
| D | eth_w5500_priv.h | 94 struct k_thread thread; member
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | Kconfig | 27 int "PTP thread stack size"
30 Set the PTP thread stack size in bytes. The PTP thread handles the
31 PTP state machine. There is one PTP thread in the system.
38 int "Priority of the PTP service thread"
|
| /Zephyr-latest/drivers/sensor/wsen/wsen_pads_2511020213301/ |
| D | wsen_pads_2511020213301.h | 55 struct k_thread thread; member
|
| /Zephyr-latest/boards/shields/rk055hdmipi4ma0/ |
| D | Kconfig.defconfig | 44 # Use offloaded render thread
|
| /Zephyr-latest/drivers/sensor/sensirion/sht3xd/ |
| D | sht3xd.h | 74 struct k_thread thread; member
|
| /Zephyr-latest/arch/x86/core/ |
| D | ia32.cmake | 18 ia32/thread.c
|
| /Zephyr-latest/soc/nxp/mcx/mcxw/ |
| D | Kconfig.defconfig | 43 # need to be queued and processed by a dedicated thread
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 231 or sending network data. Each traffic class queue is implemented as a thread
234 faster or slower. Because of thread scheduling latencies, in practice the
236 using a dedicated traffic class thread. This is why by default the
256 used to enable or disable a feature. Each thread stack size is optimized
259 The network management API is using a dedicated thread by default. The thread
264 that the net_mgmt thread is calling for each network management event.
265 By default the net_mgmt event thread stack size is rather small.
268 The net_mgmt event thread stack size is controlled by
272 The network thread stack utilization can be monitored from kernel shell by
|
| /Zephyr-latest/samples/userspace/hello_world_user/ |
| D | README.rst | 15 * single thread
|
| /Zephyr-latest/subsys/shell/modules/kernel_service/ |
| D | Kconfig | 30 rsource "thread/Kconfig"
|
| /Zephyr-latest/subsys/rtio/ |
| D | rtio_workq.c | 55 req->work.thread = NULL; in rtio_work_req_alloc()
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig.nxp_fs26 | 66 Size of the stack used for internal thread which is ran for
73 Priority level for internal cooperative thread which is ran for
|
| /Zephyr-latest/drivers/sensor/honeywell/sm351lt/ |
| D | sm351lt.c | 213 k_thread_create(&data->thread, data->thread_stack, in sm351lt_init()
221 k_thread_name_set(&data->thread, dev->name); in sm351lt_init()
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | coredump.c | 195 void arch_coredump_priv_stack_dump(struct k_thread *thread) in arch_coredump_priv_stack_dump() argument
200 hdr_stack_obj = (struct xtensa_thread_stack_header *)thread->stack_obj; in arch_coredump_priv_stack_dump()
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.cc2520 | 14 int "Driver's internal RX thread stack size"
17 This option sets the driver's stack size for its internal RX thread.
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig.nxp | 27 bool "Process RX buffers in a dedicated thread"
31 in a dedicated thread.
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.nrf5 | 40 hardware to make them ready for thread mode consumers.
48 thread mode consumers. As soon as the number of available bytes in the
|
| D | Kconfig.stm32 | 26 hardware to make them ready for thread mode consumers.
34 thread mode consumers. As soon as the number of available bytes in the
|
| /Zephyr-latest/samples/subsys/ipc/openamp/ |
| D | README.rst | 83 Starting application thread!
97 Starting application thread!
|
| /Zephyr-latest/subsys/net/lib/coap/ |
| D | Kconfig | 113 int "Coap client thread priority"
116 Priority of receive thread of the CoAP client.
140 int "Stack size of the CoAP client thread"
176 int "CoAP server thread stack size"
179 CoAP server thread stack size for processing RX/TX events.
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | socket_service.rst | 14 is data received on a socket. The API helps to avoid creating a dedicated thread
15 for each TCP or UDP service that the application provides. Instead one thread
17 as only one thread needs to be created in the system in this case.
95 service after which the socket service thread will start to call the callback
|
1...<<21222324252627282930>>...37
