Home
last modified time | relevance | path

Searched refs:mandatory (Results 1 – 25 of 54) sorted by relevance

123

/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/
Dcfg_srv.rst11 The Configuration Server model is mandatory on all Bluetooth Mesh nodes, and
Daccess.rst183 is mandatory for all mesh devices. It contains the element and model composition,
190 and is mandatory for all mesh devices. A model may extend and/or correspond to one
205 Composition Data Page 2 is only mandatory for devices that claim support for one or more
/Zephyr-Core-3.7.0/include/zephyr/shell/
Dshell.h112 uint8_t mandatory; /*!< Number of mandatory arguments. */ member
231 mandatory, optional) \ argument
233 SHELL_CMD_ARG(syntax, subcmd, help, handler, mandatory, optional); \
262 mandatory, optional) \ argument
267 mandatory, optional) \
494 .args = { .mandatory = _mand, .optional = _opt} \
/Zephyr-Core-3.7.0/subsys/logging/
DKconfig.template.log_config_inherit7 # The following arguments are mandatory:
/Zephyr-Core-3.7.0/subsys/llext/
Dshell.c85 entry->args.mandatory = 0; in llext_name_get()
94 entry->args.mandatory = 1; in llext_name_arg_get()
/Zephyr-Core-3.7.0/soc/openisa/rv32m1/
Dvector_table.ld9 * Respect for CONFIG_ROM_START_OFFSET is mandatory
/Zephyr-Core-3.7.0/cmake/
Dpristine.cmake10 mandatory arguments:
/Zephyr-Core-3.7.0/boards/intel/socfpga_std/cyclonev_socdk/
Dcyclonev_socdk.dts82 /* Configuring Zephyr mandatory devices */
/Zephyr-Core-3.7.0/doc/contribute/
Dindex.rst25 This page is a mandatory read for first-time contributors as it contains important information on
30 This document is another mandatory read that describes the expected behavior of `all`
/Zephyr-Core-3.7.0/subsys/mgmt/osdp/
DKconfig.cp52 master Key. This is a mandatory key when secure channel is enabled.
/Zephyr-Core-3.7.0/doc/develop/manifest/
Dindex.rst53 recommended ways to do this while still inheriting the mandatory modules from
/Zephyr-Core-3.7.0/doc/hardware/peripherals/
Drtc.rst81 By default, only the mandatory setting and getting of time is enabled
92 only the mandatory features, the following command can be used for
/Zephyr-Core-3.7.0/samples/subsys/testsuite/pytest/shell/
DREADME.rst58 DEBUG: #: Write memory at address with mandatory width and value:
/Zephyr-Core-3.7.0/samples/bluetooth/encrypted_advertising/
DREADME.rst20 While this sample uses extended advertising, it is **not** mandatory when using
/Zephyr-Core-3.7.0/doc/hardware/porting/
Dsoc_porting.rst46 A ``<VENDOR>`` subdirectory is mandatory if contributing your SoC
74 The mandatory files are:
211 There is one mandatory Kconfig file in the SoC directory, and two optional
/Zephyr-Core-3.7.0/samples/subsys/video/capture/
DREADME.rst16 This sample needs a video capture device (e.g. a camera) but it is not mandatory.
/Zephyr-Core-3.7.0/lib/posix/options/
DKconfig.timer78 Enable mandatory timeouts for some blocking operations.
DKconfig.profile58 Option Groups to facilitate device I/O, signals, mandatory configuration utilities, and
/Zephyr-Core-3.7.0/modules/hostap/
DKconfig30 # 30K is mandatory, but might need more for long duration use cases
84 # Hidden as these are mandatory for WFA certification
/Zephyr-Core-3.7.0/cmake/modules/
DFindTargetTools.cmake38 # CMAKE_SYSTEM_NAME : this one is mandatory, it is the name of the target
/Zephyr-Core-3.7.0/dts/arm/ti/
Dcc13xx_cc26xx.dtsi204 status = "okay"; /* the system clock timer is mandatory */
/Zephyr-Core-3.7.0/doc/services/portability/posix/conformance/
Dindex.rst23 .. TODO: POSIX_ASYNCHRONOUS_IO, and other interfaces below, are mandatory. That means that a
/Zephyr-Core-3.7.0/subsys/shell/
Dshell.c539 if (sh->ctx->active_cmd.args.mandatory) { in exec_cmd()
540 uint32_t mand = sh->ctx->active_cmd.args.mandatory; in exec_cmd()
585 *args_left = entry->args.mandatory - 1; in active_cmd_prepare()
Dshell_cmds.c452 return (entry->args.mandatory == 1) && (entry->args.optional == 0); in no_args()
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/
Dbluetooth-ctlr-arch.rst224 * 7 capture/compare registers (3 mandatory, 1 optional for ISR profiling,

123