Home
last modified time | relevance | path

Searched full:large (Results 1 – 25 of 418) sorted by relevance

12345678910>>...17

/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Dlcd_cli.rst3 Large Composition Data Client
6 The Large Composition Data Client model is a foundation model defined by the Bluetooth mesh
10 The Large Composition Data Client model was introduced in the Bluetooth Mesh Protocol Specification
15 The Large Composition Data Client model communicates with a Large Composition Data Server model
16 using the device key of the node containing the target Large Composition Data Server model instance.
18 If present, the Large Composition Data Client model must only be instantiated on the primary
Dlcd_srv.rst3 Large Composition Data Server
6 The Large Composition Data Server model is a foundation model defined by the Bluetooth mesh
10 The Large Composition Data Server model was introduced in the Bluetooth Mesh Protocol Specification
14 The Large Composition Data Server does not have an API of its own and relies on a
18 If present, the Large Composition Data Server model must only be instantiated on the primary
24 The Large Composition Data Server model allows each model to have a list of model's specific
25 metadata that can be read by the Large Composition Data Client model. The metadata list can be
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/
Dlarge_comp_data_cli.h17 * @defgroup bt_mesh_large_comp_data_cli Large Composition Data Client model
24 /** Large Composition Data response. */
36 /** Large Composition Data Status messages callbacks */
38 /** @brief Optional callback for Large Composition Data Status message.
40 * Handles received Large Composition Data Status messages from a Large Composition Data
46 * @param cli Large Composition Data Client context.
55 * Handles received Models Metadata Status messages from a Large Composition Data
61 * @param cli Large Composition Data Client context.
69 /** Large Composition Data Client model context */
77 /** Optional callback for Large Composition Data Status messages. */
[all …]
Dlarge_comp_data_srv.h17 * @defgroup bt_mesh_large_comp_data_srv Large Composition Data Server model
24 * @brief Large Composition Data Server model composition data entry.
/Zephyr-Core-3.5.0/tests/kernel/mem_protect/mem_map/
Dprj_x86_64_coverage_exec.conf4 # Enable large memory model to avoid relative addressing
7 CONFIG_COMPILER_OPT="-mcmodel=large"
/Zephyr-Core-3.5.0/include/zephyr/shell/
Dshell_string_conv.h27 * -ERANGE if numeric string input is to large to convert.
44 * Set to -ERANGE if numeric string input is to large to convert.
61 * Set to -ERANGE if numeric string input is to large to convert.
78 * Set to -ERANGE if numeric string input is to large to convert.
/Zephyr-Core-3.5.0/lib/libc/armstdc/src/
Derrno.c25 const int __aeabi_EDOM = 33; /**< Argument too large */
26 const int __aeabi_ERANGE = 34; /**< Result too large */
/Zephyr-Core-3.5.0/subsys/console/
DKconfig35 large host-side clipboard pastes. Set to 0 to disable
44 large host-side clipboard pastes. Set to 0 to disable
/Zephyr-Core-3.5.0/samples/bluetooth/mtu_update/
DREADME.rst20 Question: I only want to *send* large packets. I don't need to receive large
30 large notification to be sent.
34 To be able to send a large notification both the server and the client need to
82 should subscribe and then the peripheral will send a large notification. Right
/Zephyr-Core-3.5.0/doc/_static/latex/
Dtitle.tex29 \LARGE \py@release\releaseinfo
36 \large \@author\\\@date
/Zephyr-Core-3.5.0/samples/boards/nrf/system_off/src/
Dretained.c21 * * A 9th block of with 32 KiBy "large" sections
23 * At time of writing the maximum number of large sections is 6, all
24 * within the first large block. Theoretically there could be more
49 /* Inclusive address of the RAM range covered by large sections */
52 /* Size of a controllable RAM section in large blocks */
/Zephyr-Core-3.5.0/arch/arc/core/dsp/
DKconfig68 bool "ARC AGU large size register"
72 Save and restore large AGU registers, including 12 address pointers regs,
/Zephyr-Core-3.5.0/samples/net/sockets/coap_server/
DREADME.rst26 /large
28 /large-update
/Zephyr-Core-3.5.0/arch/arm64/core/
DCMakeLists.txt18 # Use large code model for addresses larger than 32 bits,
27 zephyr_cc_option(-mcmodel=large)
/Zephyr-Core-3.5.0/tests/benchmarks/latency_measure/boards/
Datsame54_xpro.conf2 # for platforms that do not allow frequency dividers large enough to get
Darduino_due.conf2 # for platforms that do not allow frequency dividers large enough to get
Dfrdm_k22f.conf2 # for platforms that do not allow frequency dividers large enough to get
Dfrdm_k64f.conf2 # for platforms that do not allow frequency dividers large enough to get
Dfrdm_k82f.conf2 # for platforms that do not allow frequency dividers large enough to get
Dqemu_cortex_m3.conf2 # for platforms that do not allow frequency dividers large enough to get
Dtwr_ke18f.conf2 # for platforms that do not allow frequency dividers large enough to get
/Zephyr-Core-3.5.0/subsys/bluetooth/mesh/
Dlarge_comp_data_srv.c37 /** Mesh Large Composition Data Server Model Context */
98 LOG_ERR("Unable to send Large Composition Data Status"); in handle_large_comp_data_get()
172 LOG_ERR("Large Composition Data Server only allowed in primary element"); in large_comp_data_srv_init()
176 /* Large Composition Data Server model shall use the device key */ in large_comp_data_srv_init()
/Zephyr-Core-3.5.0/include/zephyr/kernel/internal/
Dsched_priq.h25 * much better O(logN) scaling in the presence of large number of
50 * features like deadline scheduling which need large priority spaces
/Zephyr-Core-3.5.0/tests/bluetooth/shell/boards/
Dnrf5340_audio_dk_nrf5340_cpuapp.conf4 # The LC3 codec uses a large amount of stack. This app runs the codec in the work-queue, hence
Dnrf5340dk_nrf5340_cpuapp.conf4 # The LC3 codec uses a large amount of stack. This app runs the codec in the work-queue, hence

12345678910>>...17