Home
last modified time | relevance | path

Searched full:well (Results 1 – 25 of 666) sorted by relevance

12345678910>>...27

/Zephyr-latest/include/zephyr/net/
Dcoap_link_format.h27 * included in the responses of the .well-known/core resource if is to be used with
31 ((const char * const[]) { ".well-known", "core", NULL })
34 * @brief Build a CoAP response for a .well-known/core CoAP request.
37 * @param request A pointer to the .well-known/core CoAP request
50 * @brief Build a CoAP response for a .well-known/core CoAP request.
54 * @param request A pointer to the .well-known/core CoAP request
69 * 'well-known/core' "virtual" resource, the 'user_data' field should point
Dnet_time.h37 * clock that does not wrap during uptime and is - in a certain, well-defined
46 * well-defined tolerances. Network uptime therefore differs from time
73 * Also net_time_t can be used in the network stack as well as in applications
100 * network nodes comparable within well-defined limits and therefore net_time_t
/Zephyr-latest/tests/drivers/dma/loop_transfer/boards/
Dstm32h750b_dk.conf5 # SRAM4 & the driver excpects it to be uncached as well.
6 # Other DMAs have access to SRAM4 as well.
/Zephyr-latest/tests/bsim/bluetooth/host/att/pipeline/test_scripts/
Drun_test_tolerate_pipeline_variant_rx_tx_prio_invert.sh10 # The DUT GATT server must remain available to a well-behaved
20 # - The well-behaved peer performs a discovery procedure
23 # - The connection with the well-behaved peer shall remain
/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/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/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/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/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/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/tests/subsys/testsuite/fff_fake_contexts/include/zephyr/
Dcalled_API.h24 * as well as providing a return value. This requires the _custom_fake
41 * as well as providing a return value. This is defined to
/Zephyr-latest/include/zephyr/bluetooth/audio/
Dgmap.h98 * Requires BT_GMAP_UGT_FEAT_SOURCE to be set as well
110 * Requires BT_GMAP_UGT_FEAT_SINK to be set as well
116 * Requires BT_GMAP_UGT_FEAT_SINK to be set as well
123 * @kconfig{CONFIG_BT_ASCS_MAX_ACTIVE_ASES} > 1, and BT_GMAP_UGT_FEAT_SINK to be set as well
131 * as well
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst69 the two can be implementation-specific. This configuration is well suited for
93 footprint as well as power consumption. Here's a short list of the different
113 The controller itself needs to be enabled as well, typically by making sure the
139 The controller itself needs to be enabled as well, typically by making sure the
188 event handling as well as connection tracking happens. The implementation of
193 Implements the controller-side of HCI, the Link Layer as well as access to the
/Zephyr-latest/samples/drivers/peci/
Dsample.yaml5 # theoretically EVB can be connected to Intel RVP as well,
/Zephyr-latest/samples/net/tftp_client/
DKconfig19 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/tests/bluetooth/shell/boards/
Dnative_sim.conf5 # For native sim k_sleep is used in the data path as well as for shell input
/Zephyr-latest/samples/drivers/virtualization/ivshmem/doorbell/boards/
Dqemu_cortex_a53.conf19 # The default ivshmem memory size is 4MB (4194304), but libc uses the arena as well
Dqemu_kvm_arm64.conf19 # The default ivshmem memory size is 4MB (4194304), but libc uses the arena as well
/Zephyr-latest/drivers/mipi_dbi/
DKconfig.spi11 a MIPI-DBI mode C compatible controller using a SPI device, 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/samples/sensor/ds18b20/boards/
Dnucleo_g0b1re.overlay11 * a) the UART RX pin as well as the TX pin.
/Zephyr-latest/lib/posix/options/
DKconfig.profile57 PSE51 includes the POSIX Base Definitions (System Interfaces) as well as several Options and
72 PSE52 includes the POSIX Base Definitions (System Interfaces) as well as all features of
88 PSE53 includes the POSIX Base Definitions (System Interfaces) as well as all features of
/Zephyr-latest/dts/bindings/gpio/
Dx-powers,axp192-gpio.yaml7 to be used as an IO as well.
/Zephyr-latest/doc/hardware/peripherals/audio/
Di2s.rst10 as well as common non-standard extensions such as PCM Short/Long Frame Sync

12345678910>>...27