Home
last modified time | relevance | path

Searched refs:well (Results 1 – 25 of 401) sorted by relevance

12345678910>>...17

/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/philosophers/
DREADME.rst12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
18 are shown as well, such as STARVING when the philosopher is hungry but the
56 priorities, as well as semaphores and thread sleeping.
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/philosophers/
DREADME.rst12 threads of differing priorities, as well as mutex/semaphore and thread sleeping
18 are shown as well, such as STARVING when the philosopher is hungry but the
56 priorities, as well as semaphores and thread sleeping.
/Zephyr-latest/doc/hardware/arch/
Drisc-v.rst8 Currently, there's support for some boards, as well as Qemu support
13 ISA extensions as well as :ref:`semihosting<semihost_guide>`.
/Zephyr-latest/doc/hardware/peripherals/audio/
Di2s.rst10 as well as common non-standard extensions such as PCM Short/Long Frame Sync
/Zephyr-latest/samples/net/lwm2m_client/
DKconfig12 This is used as client endpoint name as well as PSK ID.
40 When DNS resolver is enabled, DNS domain names could be used as well.
/Zephyr-latest/boards/qemu/cortex_a53/
Dqemu_cortex_a53_qemu_cortex_a53_smp_defconfig16 # icount does not work well with SMP
/Zephyr-latest/samples/net/tftp_client/
DKconfig19 When DNS resolver is enabled, DNS domain names could be used as well.
/Zephyr-latest/samples/sensor/ds18b20/boards/
Dnucleo_g0b1re.overlay11 * a) the UART RX pin as well as the TX pin.
Dnrf52840dk_nrf52840.overlay11 * line to the UART RX pin as well as the TX pin
/Zephyr-latest/samples/bluetooth/peripheral/
DREADME.rst10 Application demonstrating the Bluetooth LE Peripheral role. It has several well-known and
/Zephyr-latest/tests/drivers/disk/disk_access/
DREADME.txt6 disk devices as well. The test has the following phases:
8 * Setup test: Verifies that disk initialization works, as well as testing
/Zephyr-latest/drivers/w1/
DCMakeLists.txt23 # network functions should be callable from user as well as supervisor mode:
/Zephyr-latest/doc/connectivity/bluetooth/
Dindex.rst11 hardware, as well as portions of a Classical Bluetooth (BR/EDR) Host layer.
/Zephyr-latest/samples/drivers/stepper/tmc50xx/boards/
Dnucleo_g071rb.overlay35 /* ADI TMC ramp generator as well as current settings */
/Zephyr-latest/drivers/mipi_dbi/
DKconfig.spi11 a MIPI-DBI mode C compatible controller using a SPI device, as well
/Zephyr-latest/doc/services/llext/
Dindex.rst11 and introspected to some degree, as well as unloaded when no longer needed.
/Zephyr-latest/samples/bluetooth/bthome_sensor_template/
DREADME.rst27 went well.
/Zephyr-latest/scripts/
Drequirements-base.txt39 # "win32" is used for 64-bit Windows as well
/Zephyr-latest/subsys/net/lib/coap/
DKconfig21 bool "CoAP ./well-known/core services block wise support"
24 to ./well-known/core request. Without this option all resource's
30 int "CoAP ./well-known/core services block wise support"
202 bool "CoAP server support ./well-known/core service"
205 Enable responding to the ./well-known/core service resource.
/Zephyr-latest/subsys/bluetooth/services/nus/
DKconfig.nus17 instance as well.
/Zephyr-latest/tests/drivers/disk/disk_performance/
DREADME.txt5 was tested with SD cards, but can be used for other disk devices as well.
/Zephyr-latest/samples/drivers/w1/scanner/
DREADME.rst11 scan routine once and prints the family id as well as serial number of the
/Zephyr-latest/drivers/espi/
DKconfig.espi_emul18 specification for more details (it is good for the introduction as well)
/Zephyr-latest/doc/connectivity/networking/api/
Dmqtt_sn.rst13 MQTT-SN is a variant of the well-known MQTT protocol - see :ref:`mqtt_socket_interface`.
17 but others like Bluetooth, UDP or even a UART can be used just as well.
49 independently. Additionally, a structure for the transport is needed as well.
141 the socket), call :c:func:`mqtt_sn_client_deinit`, which will deinit the transport as well.
/Zephyr-latest/doc/services/debugging/
Dcpu_load.rst8 it is more accurate since it takes into account time spent in the interrupt context as well.

12345678910>>...17