| /Zephyr-latest/drivers/sensor/adi/adxl372/ |
| D | adxl372.h | 329 struct k_work work; member
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 13 These directions have been validated to work with version 1.16.0 of the IDE
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | index.rst | 85 * MAY implement :c:type:`sensor_submit_t` using a work queue if
|
| /Zephyr-latest/samples/sensor/fxos8700/ |
| D | README.rst | 21 :zephyr:board:`bbc_microbit`, and :ref:`reel_board` boards. It does not work on
|
| /Zephyr-latest/samples/subsys/fs/littlefs/ |
| D | README.rst | 71 This example should work on any board that provides a "storage"
|
| /Zephyr-latest/cmake/linker/ld/ |
| D | target.cmake | 56 # TODO: How would the linker script dependencies work for non-linker
|
| /Zephyr-latest/cmake/linker/xt-ld/ |
| D | target.cmake | 54 # TODO: How would the linker script dependencies work for non-linker
|
| /Zephyr-latest/samples/modules/tflite-micro/hello_world/ |
| D | README.rst | 34 The sample should work on most boards since it does not rely
|
| /Zephyr-latest/samples/bluetooth/tmap_central/src/ |
| D | cap_initiator.c | 375 static void audio_timer_timeout(struct k_work *work) in audio_timer_timeout() argument
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/src/mesh/ |
| D | publisher.c | 20 void publish(struct k_work *work) in publish() argument
|
| /Zephyr-latest/tests/kernel/context/ |
| D | README.txt | 48 - Used when triggering an ISR to perform ISR context work.
|
| /Zephyr-latest/kernel/ |
| D | CMakeLists.txt | 81 work.c
|
| /Zephyr-latest/samples/bluetooth/hap_ha/src/ |
| D | bap_unicast_sr.c | 136 static void audio_timer_timeout(struct k_work *work) in audio_timer_timeout() argument
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.1.rst | 488 * :github:`20933` - x\_nucleo\_iks01a3 shield: STM LSM6DSO sensor does not work after h/w or s/w re…
595 * :github:`20325` - samples/drivers/i2c\_scanner does not work on STM32 NUCLEO and DISCOVERY boards
651 * :github:`19885` - SMP doesn't work on ARC any longer
673 * :github:`19734` - "make gdbserver" doesn't work properly for qemu\_x86\_long
755 * :github:`19181` - sock\_set\_flag implementation in sock\_internal.h does not work for 64 bit poi…
769 * :github:`19078` - search for board specific shield overlays doesn't always work
780 * :github:`19013` - [Zephyr 1.14]: NetUsb and Ethernet work together
797 * :github:`18816` - ssd1306 driver can't work with lvgl
828 * :github:`18143` - stm32f SPI Slave TX does not work correctly, but occurs OVERRUN err
884 * :github:`15323` - blink\_led sample does not work on most of the nRF boards
|
| D | release-notes-1.8.rst | 233 * ``ZEP-1530`` - Hotkeys for the menu at the bottom of menuconfig sometimes doesn't work
245 * ``ZEP-1719`` - TCP does not work with 6lo
299 * ``ZEP-2029`` - xtensa: irq_offload() doesn't work on XRC_D2PM
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 66 some architectures require a bit more work to be performed.
95 When a device wants to signal the processor that there is some work to be done
100 interrupts. The handler performs the work required by the exception or the
101 interrupt. For interrupts, that work is device-specific. For exceptions, it
105 The kernel has to perform some work in addition to the work the handler itself
121 This work is conceptually the same across architectures, but the details are
125 * The processor instructions to perform the work.
299 on the architecture. There is a generic implementation, but it might not work
435 for doing real work after initialization, i.e. it is sitting in a loop doing
|
| /Zephyr-latest/drivers/gpio/ |
| D | gpio_pca95xx.c | 623 static void gpio_pca95xx_interrupt_worker(struct k_work *work) in gpio_pca95xx_interrupt_worker() argument
626 work, struct gpio_pca95xx_drv_data, interrupt_worker); in gpio_pca95xx_interrupt_worker()
|
| /Zephyr-latest/boards/wiznet/w5500_evb_pico/doc/ |
| D | index.rst | 194 work with the OpenOCD that was installed with the default configuration. This
204 adapter maybe also work with this configuration.
|
| /Zephyr-latest/doc/services/pm/ |
| D | device_runtime.rst | 59 devices power consumption with minimal application work. Device drivers are
111 then be carried out when the system work queue gets the chance to run. The
|
| /Zephyr-latest/boards/st/nucleo_h755zi_q/doc/ |
| D | index.rst | 233 Sometimes, flashing via OpenOCD does not work. It is necessary to erase the flash
234 (with STM32CubeProgrammer for example) to make it work again.
|
| /Zephyr-latest/boards/st/stm32h745i_disco/doc/ |
| D | index.rst | 219 Sometimes, flashing does not work properly. It is necessary to erase the flash
220 (with STM32CubeProgrammer for example) to make it work again.
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | http_server_core.c | 375 static void client_timeout(struct k_work *work) in client_timeout() argument
377 struct k_work_delayable *dwork = k_work_delayable_from_work(work); in client_timeout()
|
| /Zephyr-latest/subsys/usb/device_next/class/ |
| D | usbd_hid.c | 538 static void hid_dev_output_handler(struct k_work *work) in hid_dev_output_handler() argument
540 struct hid_device_data *ddata = CONTAINER_OF(work, in hid_dev_output_handler()
|
| /Zephyr-latest/drivers/wifi/esp32/ |
| D | Kconfig.esp32 | 295 int "Maximum work queue thread priority"
298 Maximum priority of thread used for processing driver work queue items.
306 …it will work for at least ESP_WIFI_SLP_DEFAULT_MIN_ACTIVE_TIME. If a data packet is received or se…
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 46 contributor, such as when the contributor is doing work on behalf of a
114 (b) The contribution is based upon previous work that, to the
117 submit that work with modifications, whether created in whole
800 #. Create a topic branch (off of ``main``) for your work (if you're addressing
806 Some Zephyr subsystems do development work on a separate branch from
865 can create another branch to work on another issue. (Be sure to make your
871 and use the same process described above to work on this new topic branch.
963 proposal (RFC) for your work first, to be sure that we can use it. Please
968 prevent duplication of work, and help you to craft the change so that it is
|
