Home
last modified time | relevance | path

Searched full:via (Results 1 – 25 of 894) sorted by relevance

12345678910>>...36

/Zephyr-Core-3.5.0/include/zephyr/drivers/dma/
Ddma_mcux_smartdma.h10 /* Write RGB565 data to MIPI DSI via DMA. */
12 /* Write RGB888 data to MIPI DSI via DMA */
14 /* Write RGB565 data to MIPI DSI via DMA. Rotate output data by 180 degrees */
16 /* Write RGB888 data to MIPI DSI via DMA. Rotate output data by 180 degrees */
19 /* Write RGB565 data to MIPI DSI via DMA. Swap data endianness, so that
23 /* Write RGB888 data to MIPI DSI via DMA. Swap data endianness, so that
27 /* Write RGB565 data to MIPI DSI via DMA. Rotate output data by 180 degrees,
31 /* Write RGB888 data to MIPI DSI via DMA. Rotate output data by 180 degrees,
/Zephyr-Core-3.5.0/tests/kernel/lifo/lifo_api/src/
Dtest_lifo_contexts.c11 /**TESTPOINT: init via K_LIFO_DEFINE*/
61 /**TESTPOINT: thread-thread data passing via lifo*/ in tlifo_thread_thread()
73 /**TESTPOINT: thread-isr data passing via lifo*/ in tlifo_thread_isr()
81 /**TESTPOINT: isr-thread data passing via lifo*/ in tlifo_isr_thread()
92 * @brief test thread to thread data passing via lifo
97 /**TESTPOINT: init via k_lifo_init*/ in ZTEST()
106 * @brief test isr to thread data passing via lifo
111 /**TESTPOINT: init via k_lifo_init*/ in ZTEST()
120 * @brief test thread to isr data passing via lifo
/Zephyr-Core-3.5.0/drivers/espi/
DKconfig.xec110 Enable a 32 byte mailbox interface accessible via Host I/O over the
116 Enable ACPI EC2 interface accessible via Host I/O over the
122 Enable ACPI EC3 interface accessible via Host I/O over the
128 Enable ACPI EC4 interface accessible via Host I/O over the
134 Enable ACPI PM1 interface accessible via Host I/O over the
140 Enable EMI 0 interface accessible via Host I/O over the
146 Enable EMI 1 interface accessible via Host I/O over the
152 Enable EMI 2 interface accessible via Host I/O over the
/Zephyr-Core-3.5.0/doc/services/tfm/
Dtestsuites.rst9 These test suites can be run from Zephyr via an appropriate sample application
15 The regression test suite can be run via the :ref:`tfm_regression_test` sample.
18 NS/S boundary via the PSA APIs. They provide a useful sanity check for proper
25 The PSA Arch Test suite, available via :ref:`tfm_psa_test`, contains a number of
31 described via ``CONFIG_TFM_PSA_TEST_*`` KConfig flags:
Drequirements.rst52 You can install them via:
65 This can be installed on Linux via:
71 And on OS X via:
/Zephyr-Core-3.5.0/soc/arm/microchip_mec/mec172x/
DKconfig.soc45 bool "Debug support via Serial wire debug"
50 bool "Debug support via Serial wire debug with tracing enabled"
64 bool "Debug support via Serial wire debug"
70 bool "debug support via Serial Wire Debug and Viewer"
/Zephyr-Core-3.5.0/tests/kernel/fifo/fifo_api/src/
Dtest_fifo_contexts.c11 /**TESTPOINT: init via K_FIFO_DEFINE*/
90 /**TESTPOINT: thread-thread data passing via fifo*/ in tfifo_thread_thread()
102 /**TESTPOINT: isr-thread data passing via fifo*/ in tfifo_thread_isr()
110 /**TESTPOINT: thread-isr data passing via fifo*/ in tfifo_isr_thread()
134 * @brief Test thread to thread data passing via fifo
139 /**TESTPOINT: init via k_fifo_init*/ in ZTEST()
148 * @brief Test isr to thread data passing via fifo
153 /**TESTPOINT: init via k_fifo_init*/ in ZTEST()
162 * @brief Test thread to isr data passing via fifo
/Zephyr-Core-3.5.0/soc/arm/microchip_mec/mec1501/
DKconfig.soc57 bool "Debug support via Serial wire debug"
62 bool "Debug support via Serial wire debug with tracing enabled"
77 bool "Debug support via Serial wire debug"
83 bool "debug support via Serial Wire Debug and Viewer"
/Zephyr-Core-3.5.0/samples/boards/nrf/nrfx_prs/
Dprj.conf1 # This is needed for using SPIM2 and UARTE2 via nrfx drivers and for switching
8 # This is needed for using another SPIM instance via the Zephyr SPI driver.
/Zephyr-Core-3.5.0/doc/services/storage/disk/
Daccess.rst15 SD cards via SPI. These drivers use disk driver interface and a file system
16 can access the SD cards via disk access API.
29 Zephyr supports SD memory cards via the disk driver API, or via the SDMMC
30 subsystem. This subsystem can be used transparently via the disk driver API,
36 SD Card support via SPI
/Zephyr-Core-3.5.0/drivers/sensor/lis2dw12/
DKconfig66 bool "Wakeup threshold trigger (via interrupt)"
77 bool "Free Fall detection (via interrupt)"
79 Enable freefall detection via interrupt.
/Zephyr-Core-3.5.0/subsys/debug/coredump/
DKconfig20 Core dump is done via logging subsystem.
34 Core dump is done via memory window slot[1].
41 Core dump is done via custom mechanism defined out of tree
/Zephyr-Core-3.5.0/doc/connectivity/usb/device_next/
Dusb_device.rst29 ``-DCONF_FILE=usbd_next_prj.conf`` either directly or via ``west``.
38 ``-DCONF_FILE=usbd_next_prj.conf`` either directly or via ``west``.
45 ``-DCONF_FILE=usbd_next_prj.conf`` either directly or via ``west``.
57 ``-DDTC_OVERLAY_FILE="usbd_next_ecm.overlay`` either directly or via ``west``.
/Zephyr-Core-3.5.0/lib/posix/
DKconfig.barrier17 e.g. via twister, explicit serialization may be required between
22 via pthread_barrier_wait().
/Zephyr-Core-3.5.0/drivers/disk/
DKconfig.mmc26 bool "MMC access via SD subsystem"
31 Enable MMC access via SD subsystem.
/Zephyr-Core-3.5.0/boards/arm/pandora_stm32l475/support/
Dopenocd.cfg3 # but perfectly functional for any other STM32L4 board connected via
5 # This is for STM32L4 boards that are connected via stlink-v2-1.
/Zephyr-Core-3.5.0/soc/arm/aspeed/ast10x0/
DKconfig.soc19 changing it via menuconfig or in configuration files.
26 generally avoid changing it via menuconfig or in configuration files.
/Zephyr-Core-3.5.0/dts/bindings/usb/
Dusb-controller.yaml16 via DT, USB controllers should use their maximum
26 description: Control VBUS via GPIO pin.
/Zephyr-Core-3.5.0/scripts/coccinelle/
Dconst_config_info.cocci68 // asg via macro: struct T * D = DEV_CFG()
80 // asg via macro to const local: struct T * const D = DEV_CFG()
92 // asg via macro: struct T * D; ... ; D = (const struct T*)CI;
106 // delayed asg via macro: struct T * D; ... ; D = DEV_CFG();
/Zephyr-Core-3.5.0/tests/kernel/msgq/msgq_api/src/
Dtest_msgq_contexts.c9 /**TESTPOINT: init via K_MSGQ_DEFINE*/
95 /**TESTPOINT: thread-thread data passing via message queue*/ in msgq_thread()
133 /**TESTPOINT: thread-thread data passing via message queue*/ in msgq_thread_overflow()
152 /**TESTPOINT: thread-isr data passing via message queue*/ in msgq_isr()
250 * @brief Test thread to thread data passing via message queue
257 /**TESTPOINT: init via k_msgq_init*/ in ZTEST()
267 * @brief Test thread to thread data passing via message queue
274 /**TESTPOINT: init via k_msgq_init*/ in ZTEST()
292 * @brief Test user thread to kernel thread data passing via message queue
310 * @brief Test thread to thread data passing via message queue
[all …]
/Zephyr-Core-3.5.0/dts/bindings/bluetooth/
Dzephyr,bt-hci-spi-slave.yaml8 A node defined via devicetree overlay should look like this:
21 The host interrupt GPIO is set to gpio1 pin 2 via irq-gpios. The
/Zephyr-Core-3.5.0/tests/kernel/stack/stack/src/
Dtest_stack_contexts.c15 /**TESTPOINT: init via K_STACK_DEFINE*/
70 /**TESTPOINT: thread-thread data passing via stack*/ in tstack_thread_thread()
88 /**TESTPOINT: thread-isr data passing via stack*/ in tstack_thread_isr()
102 * @brief Test to verify data passing between threads via stack
109 * Verify data passing between threads via stack
128 * @brief Verifies data passing between user threads via stack
144 * @brief Verifies data passing between thread and ISR via stack
168 /**TESTPOINT: thread-thread data passing via stack*/ in ZTEST()
/Zephyr-Core-3.5.0/doc/hardware/peripherals/
Dbbram.rst7 common types of BBRAM properties are easily accessed via this API:
14 Along with these, the API provides a means for reading and writing to the memory region via
/Zephyr-Core-3.5.0/samples/sensor/wsen_hids/
DREADME.rst19 This sample requires a WSEN-HIDS sensor connected via the I2C or SPI interface.
29 This sample can be configured to support WSEN-HIDS sensors connected via
30 either I2C or SPI. Configuration is done via the :ref:`devicetree <dt-guide>`.
/Zephyr-Core-3.5.0/include/zephyr/arch/xtensa/
Dgdbstub.h32 * 0x02xx : Special Registers (access via RSR/WSR)
33 * 0x03xx : User Registers (access via RUR/WUR)
136 * accessed via RSR/WSR.
152 * accessed via RUR/WUR.

12345678910>>...36