| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig.ucifi | 49 device that can be stored in this object.
57 device that can be stored in this object.
65 to a device that can be stored in this object.
74 stored in this object.
82 that can be stored in this object.
91 that can be stored in this object.
100 be stored in this object.
|
| /Zephyr-latest/drivers/flash/ |
| D | flash_util.c | 31 size_t stored = 0; in z_impl_flash_fill() local
57 while (stored < size) { in z_impl_flash_fill()
58 size_t chunk = MIN(sizeof(filler), size - stored); in z_impl_flash_fill()
60 rc = api->write(dev, offset + stored, filler, chunk); in z_impl_flash_fill()
63 dev, (size_t)offset + stored); in z_impl_flash_fill()
66 stored += chunk; in z_impl_flash_fill()
|
| /Zephyr-latest/include/zephyr/xen/ |
| D | generic.h | 30 ({ __typeof__(*ptr) stored = old; \
31 __atomic_compare_exchange_n(ptr, &stored, new, 0, __ATOMIC_SEQ_CST, \
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | spsc_pbuf.rst | 7 buffer, whose contents are stored in first-in-first-out order. Variable size
8 packets are stored in the buffer. Packet buffer works under assumption that there
|
| /Zephyr-latest/samples/tfm_integration/psa_protected_storage/ |
| D | README.rst | 17 be stored to and read from UIDs, and how overwrite protection can be enabled using flags.
59 Info on data stored in UID1:
63 Read and compare data stored in UID1
64 Data stored in UID1: The quick brown fox jumps over the lazy dog
65 Overwriting data stored in UID1 with: Lorem ipsum dolor sit amet
|
| /Zephyr-latest/subsys/secure_storage/src/its/ |
| D | CMakeLists.txt | 17 This means that the data and keys stored via the PSA APIs may not be secure at rest.")
22 This means that the data and keys stored via the PSA APIs will not be secure at rest.
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 23 may secure the data stored via the PSA Secure Storage API at rest.
49 * The data stored in the ITS is by default encrypted and authenticated (Against ``1.`` in
58 | This is not the case on all MCUs. Thus, additional protection is provided to the stored data.
60 However, this does not guarantee that the data stored will be secure at rest in all cases,
65 In addition, the data stored in the ITS is not protected against replay attacks,
68 * The data stored via the PSA Secure Storage API is not protected from direct
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 233 The :ref:`tls_credentials <sockets_tls_credentials_subsys>` module treats stored credentials as arb…
243 …"``BIN``", "Credential is handled by shell as base64 and stored without NULL termination.", "Data …
244 …stored with NULL termination.", "Data entered into shell will be decoded from base64 into raw bina…
245 …"``STR``", "Credential is handled by shell as literal string and stored without NULL termination."…
246 …stored with NULL-termination.", "Text data entered into shell will be passed into storage as-writt…
254 This ensures it is stored without a NULL terminator.
256 …-END X----`` markers), and then use the ``BINT`` format to make sure the stored string is NULL-ter…
|
| /Zephyr-latest/drivers/i2s/ |
| D | Kconfig.litex | 28 bool "Received data will be stored as big endian"
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | core.rst | 51 which RPL entries are to be stored in this case.
77 the change needs to be stored persistently, the stack schedules a work item.
83 When IV index, Sequence Number or CDB configuration have to be stored, the work
89 stored, the delay is set to :kconfig:option:`CONFIG_BT_MESH_RPL_STORE_TIMEOUT`.
90 If other stack configuration has to be stored, the delay defined by
106 workqueue, while the stack configuration is being stored.
|
| D | cfg.rst | 18 Runtime configuration changes before the node is provisioned will not be stored
|
| D | srpl_srv.rst | 13 of the message are stored in the node's SRPL.
|
| /Zephyr-latest/samples/sensor/grow_r502a/ |
| D | README.rst | 13 #. Shows the number of fingerprints stored in the sensor.
61 Fingerprint successfully stored at #3
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.device | 10 When enabled, device dependencies will be stored so that they can be
32 If enabled, additional data from the devicetree will be stored for
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.nrf5 | 42 bool "Support usage of EUI64 value stored in UICR registers"
47 stored in User information configuration registers (UICR).
61 section in which custom EUI64 is stored.
|
| /Zephyr-latest/samples/subsys/fs/zms/ |
| D | README.rst | 14 #. A string representing an IP address: stored at id=1, data="192.168.1.1"
15 #. A binary blob representing a key/value pair: stored at id=0xbeefdead,
17 #. A variable (32bit): stored at id=2, data=cnt
|
| /Zephyr-latest/modules/hal_nordic/nrf_802154/ |
| D | CMakeLists.txt | 37 # pending data is stored.
41 # pending data is stored.
|
| /Zephyr-latest/subsys/net/lib/wifi_credentials/ |
| D | Kconfig | 63 bool "Add command to connect to stored networks directly."
72 Wait period before falling back to the next entry in the list of stored SSIDs.
|
| /Zephyr-latest/doc/services/storage/nvs/ |
| D | nvs.rst | 6 Elements, represented as id-data pairs, are stored in flash using a
14 at least one id-data pair stored in flash at all time.
19 Each element is stored in flash as metadata (8 byte) and data. The metadata is
29 The data CRC is not checked for a partial read, as it is stored at the end of the
39 During initialization NVS will verify the data stored in flash, if it
|
| /Zephyr-latest/drivers/misc/coresight/ |
| D | Kconfig | 13 Module handles data stored in the ETR circular buffer (e.g. STM logging
29 In this mode, log messages stored by Coresight STM logging frontends are
|
| /Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/ |
| D | README.rst | 43 word (name) of the stored text will be sent to all other boards in
46 To reset a board to its initial state (disable mesh, erase the stored
|
| /Zephyr-latest/drivers/input/ |
| D | Kconfig.kbd_matrix | 34 If enabled, the actual-key-mask devicetree property data is stored in
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | fuel_gauge.rst | 34 or sleep mode due to its utility in reducing battery drain while devices are stored or shipped.
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 17 - The key part is written in an ATE (Allocation Table Entry) called "ID-ATE" which is stored
19 - The value part is defined as "DATA" and is stored raw starting from the top of the sector
91 ``ID-ATE:`` are entries that contain a 32 bits Key and describe where the data is stored, its
147 By default it looks for the last data with the same ID by browsing through all stored ATEs from
166 The lead cycle counter is stored in the empty ATE.
167 To become valid, an ATE must have the same cycle counter as the one stored in the empty ATE.
244 Values smaller than 8 bytes will be stored within the entry (ATE) itself, without writing data
268 Large data values ( > 8 bytes) are stored separately at the top of the sector.
279 Total data that could be stored in this partition for this case is :math:`11 \times 3 \times 64 = 2…
368 - Small sized data ( <= 8 bytes) are stored in the ATE itself
[all …]
|
| /Zephyr-latest/doc/services/settings/ |
| D | index.rst | 14 Settings items are stored as key-value pair strings. By convention,
105 data is stored when you call :c:func:`settings_save()`, or :c:func:`settings_save_one()`.
137 This means that the newest data entity is stored after any
149 A key need to be covered by a ``h_export`` only if it is supposed to be stored
153 changes most actual key's value are stored, therefore there is no need to check
|
