Home
last modified time | relevance | path

Searched refs:needed (Results 126 – 150 of 450) sorted by relevance

12345678910>>...18

/Zephyr-latest/doc/develop/manifest/external/
Dcannectivity.rst39 path: custom/cannectivity # adjust the path as needed
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst640 - No actions needed
642 - No actions needed
644 - No actions needed.
647 - No actions needed.
650 - No actions needed.
653 - No actions needed
656 - No actions needed, client proceeds to idle state automatically. Cannot send or receive data.
661 - No actions needed.
668 - No actions needed, client will re-register once the disable period is over.
/Zephyr-latest/doc/kernel/
Dcode-relocation.rst48 needed to force the required functions and data variables to the correct
53 The ``code_relocation.c`` file has code that is needed for
55 Also this contains code needed for bss zeroing and
/Zephyr-latest/boards/khadas/edge2/doc/
Dindex.rst61 0x1000 is the size (in number of sectors) or your image. Increase it if needed.
/Zephyr-latest/subsys/net/l2/
DKconfig10 Add a dummy L2 layer driver. This is usually only needed when
/Zephyr-latest/doc/services/virtualization/
Divshmem.rst36 vectors that will be needed.
/Zephyr-latest/samples/net/sockets/coap_server/
DREADME.rst18 some adjustments to the configuration may be needed.
/Zephyr-latest/samples/net/sockets/http_server/
DKconfig62 memory. Only increase the value here if really needed.
/Zephyr-latest/samples/drivers/adc/adc_sequence/
DREADME.rst25 oversampling setting (if used). It is also needed to provide an alias ``adc0`` for the
/Zephyr-latest/lib/posix/options/getopt/
DREADME17 commands as well. A library is needed that allows the developer to parse
/Zephyr-latest/doc/kernel/memory_management/
Dslabs.rst51 Unlike a heap, more than one memory slab can be defined, if needed. This
125 then releases it once it is no longer needed.
/Zephyr-latest/doc/connectivity/networking/
Dnetworking_with_multiple_instances.rst40 if needed, see :ref:`networking_with_eth_qemu` for details. You can also use
128 too as needed.
/Zephyr-latest/doc/services/crypto/
Dpsa_crypto.rst35 methods as needed. This flexibility is crucial for maintaining
50 libraries or hardware accelerators as needed.
61 The API provides all of the cryptographic primitives needed to establish TLS connections.
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig30 Enable structures and functions needed for packet reassembly by SMP backend.
/Zephyr-latest/subsys/mgmt/mcumgr/grp/shell_mgmt/
DKconfig39 # nothing extra is needed here, nor a default value.
/Zephyr-latest/cmake/
Dtarget_toolchain_flags.cmake32 # Loading of templates are strictly not needed as they do not set any
/Zephyr-latest/boards/shields/adafruit_data_logger/doc/
Dindex.rst54 internal GPIO pull-up and thus no external pull-up resistor is needed.
/Zephyr-latest/kernel/
DKconfig.mem_domain21 architecture-specific data is needed on a per memory domain basis.
/Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/
DKconfig76 Note: Usually no margin is needed for CIS as Null PDUs can be used if a payload
/Zephyr-latest/samples/sensor/lps22hh_i3c/
DREADME.rst36 bus. Therefore, when flashing a new image, a power cycle is needed
/Zephyr-latest/modules/hal_nordic/nrf_802154/
DCMakeLists.txt116 # This link is needed to resolve circular dependency between SL and platform
/Zephyr-latest/tests/drivers/i2s/i2s_speed/
DKconfig39 value of this option may be needed when GPIO loopback is used.
/Zephyr-latest/include/zephyr/arch/arm64/scripts/
Dlinker.ld230 * When _app_smem region is empty, alignment is also needed. If there
339 /* Output section descriptions are needed for these sections to suppress
/Zephyr-latest/cmake/modules/
Ddts.cmake107 # This generates DT information needed by the C macro APIs,
114 # The generated C header needed by <zephyr/devicetree.h>
120 # This generates DT information needed by the Kconfig APIs.
125 # This generates DT information needed by the CMake APIs.
/Zephyr-latest/doc/services/llext/
Dbuild.rst151 directory. It's a tarball that contains the headers and compile flags needed
159 contain the compile flags needed by the project, as well as other build-related
179 The full list of flags needed to build an extension is provided by

12345678910>>...18