| /Zephyr-Core-3.4.0/lib/hash/ |
| D | hash_map_cxx.cpp | 15 static void sys_hashmap_cxx_iter_next(struct sys_hashmap_iterator *it) in sys_hashmap_cxx_iter_next() argument
17 cxx_map *umap = static_cast<cxx_map *>(it->map->data->buckets); in sys_hashmap_cxx_iter_next()
21 __ASSERT(it->size == it->map->data->size, "Concurrent modification!"); in sys_hashmap_cxx_iter_next()
22 __ASSERT(sys_hashmap_iterator_has_next(it), "Attempt to access beyond current bound!"); in sys_hashmap_cxx_iter_next()
25 for (size_t i = 0; i < it->pos; ++i, it2++) in sys_hashmap_cxx_iter_next()
28 it->key = it2->first; in sys_hashmap_cxx_iter_next()
29 it->value = it2->second; in sys_hashmap_cxx_iter_next()
30 ++it->pos; in sys_hashmap_cxx_iter_next()
37 static void sys_hashmap_cxx_iter(const struct sys_hashmap *map, struct sys_hashmap_iterator *it) in sys_hashmap_cxx_iter() argument
39 it->map = map; in sys_hashmap_cxx_iter()
[all …]
|
| D | hash_map_sc.c | 135 static void sys_hashmap_sc_iter_next(struct sys_hashmap_iterator *it) in sys_hashmap_sc_iter_next() argument
140 const struct sys_hashmap *map = it->map; in sys_hashmap_sc_iter_next()
143 __ASSERT(it->size == map->data->size, "Concurrent modification!"); in sys_hashmap_sc_iter_next()
144 __ASSERT(sys_hashmap_iterator_has_next(it), "Attempt to access beyond current bound!"); in sys_hashmap_sc_iter_next()
146 if (it->pos == 0) { in sys_hashmap_sc_iter_next()
148 it->state = buckets; in sys_hashmap_sc_iter_next()
152 for (bucket = it->state; bucket < &buckets[map->data->n_buckets]; ++bucket) { in sys_hashmap_sc_iter_next()
155 if (entry->key == it->key) { in sys_hashmap_sc_iter_next()
164 it->state = bucket; in sys_hashmap_sc_iter_next()
165 it->key = entry->key; in sys_hashmap_sc_iter_next()
[all …]
|
| D | hash_func32_djb2.c | 9 * behind it (and other DJB software) is quite amazing. Thanks Dan!!
11 * Many distributors have relicensed it under e.g. BSD, MIT, and others.
13 * It is not clear what the original license name is or how to declare it
14 * using SPDX terms, since it explicitly has no license. I think it makes
|
| /Zephyr-Core-3.4.0/tests/bluetooth/host/keys/mocks/ |
| D | keys_help_utils.c | 31 for (size_t it = 0; it < size; it++) { in fill_key_pool_by_id_addr() local
32 params_vector = &src[it]; in fill_key_pool_by_id_addr()
35 refs[it] = bt_keys_get_addr(id, addr); in fill_key_pool_by_id_addr()
36 if (refs[it] == NULL) { in fill_key_pool_by_id_addr()
37 printk("'%s' Failed to add key %d to the keys pool\n", __func__, it); in fill_key_pool_by_id_addr()
57 for (size_t it = 0; it < size; it++) { in fill_key_pool_by_id_addr_type() local
58 params_vector = &src[it]; in fill_key_pool_by_id_addr_type()
62 refs[it] = bt_keys_get_type(type, id, addr); in fill_key_pool_by_id_addr_type()
63 if (refs[it] == NULL) { in fill_key_pool_by_id_addr_type()
64 printk("'%s' Failed to add key %d to the keys pool\n", __func__, it); in fill_key_pool_by_id_addr_type()
|
| /Zephyr-Core-3.4.0/include/zephyr/sys/ |
| D | sys_io.h | 92 * This functions takes the designated bit starting from port and sets it to 1.
102 * This functions takes the designated bit starting from port and sets it to 0.
110 * @brief Test the bit from port if it is set or not
113 * current setting. It will return the current setting.
118 * @return 1 if it is set, 0 otherwise
123 * @brief Test the bit from port and set it
126 * current setting and sets it. It will return the previous setting.
131 * @return 1 if it was set, 0 otherwise
136 * @brief Test the bit from port and clear it
139 * current setting and clears it. It will return the previous setting.
[all …]
|
| /Zephyr-Core-3.4.0/tests/bluetooth/host/keys/bt_keys_find_irk/src/ |
| D | main.c | 127 for (size_t it = 0; it < ARRAY_SIZE(returned_keys_refs); it++) { in rpa_resolving_ts_setup() local
128 returned_keys_refs[it]->irk.val[0] = it; in rpa_resolving_ts_setup()
190 for (size_t it = 0; it < ARRAY_SIZE(testing_id_addr_type_lut); it++) { in ZTEST() local
192 params_vector = &testing_id_addr_type_lut[it]; in ZTEST()
198 params_it = it; in ZTEST()
201 expected_key_ref = returned_keys_refs[it]; in ZTEST()
214 "bt_keys_find_irk() returned a NULL reference %d", it); in ZTEST()
224 "bt_keys_find_irk() returned a non-valid reference %d", it); in ZTEST()
244 for (size_t it = 0; it < ARRAY_SIZE(returned_keys_refs); it++) { in no_resolving_ts_setup() local
245 returned_keys_refs[it]->irk.val[0] = it; in no_resolving_ts_setup()
[all …]
|
| /Zephyr-Core-3.4.0/subsys/mgmt/mcumgr/transport/include/mgmt/mcumgr/transport/ |
| D | smp_reassembly.h | 21 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
22 * to validate the pointer before passing it to this function.
29 * The function adds data to the end of current re-assembly buffer; it will allocate new buffer
39 * Note: For efficiency there are ot NULL checks on @p smpt and @p buf pointers and it is caller's
46 * CONFIG_MCUMGR_TRANSPORT_NETBUF_SIZE, which means there is no way to fit it in
61 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
62 * to validate the pointer before passing it to this function.
72 * Checks if the packet has enough data to be re-assembled and passes it for further processing.
76 * in which case it is users responsibility to use the user data, passed with the packet, to notify
82 * Note: for efficiency there is no NULL check on @p smpt pointer and it is caller's responsibility
[all …]
|
| /Zephyr-Core-3.4.0/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 15 a means to hold the packet, write and read it, as well as necessary
19 The data structure and the whole API around it are defined in
44 Note, however, one will rarely have to use it, as the core provides
54 needs various metadata information to become relevant as well. It
55 requires at least to get the network interface it is meant to be sent
56 through or through which it was received. As this is a very common
78 :ref:`net_buf_interface` for more information). However, it mostly
94 once via :c:func:`net_pkt_alloc_with_buffer`. It is actually the most
140 :c:func:`net_pkt_alloc_buffer`, as it will take into account the
141 existing buffer. It will also account for the header space if
[all …]
|
| /Zephyr-Core-3.4.0/doc/connectivity/networking/ |
| D | net_pkt_processing_stats.rst | 33 The TX time tells how long it took for network packet from its creation to
34 when it was sent to the network. The RX time tells the time from its creation
35 to when it was passed to the application. The values are in microseconds. The
53 The numbers inside the brackets contain information how many microseconds it
60 * Packet is about to be placed to transmit queue. The time it took from network
63 queue. It took **15** microseconds from previous state.
65 network packet. It took **23** microseconds from previous state.
66 * In total it took on average **60** microseconds to get the network packet
74 * Packet is about to be placed to receive queue. The time it took from network
77 queue. It took **6** microseconds from previous state.
[all …]
|
| /Zephyr-Core-3.4.0/drivers/ieee802154/ |
| D | Kconfig.cc2520 | 18 The default value should be sufficient, but in case it proves to be
19 a too little one, this option makes it easy to play with the size.
25 Set the initialization priority number. Do not mess with it unless
28 might need it too). And of course it has to start before the net stack.
82 Set the initialization priority number. Do not mess with it unless
83 you know what you are doing. It should be initialized after CC2520
84 as it shares the same runtime context.
|
| D | Kconfig.rf2xx | 21 The default value should be sufficient, but in case it proves to be
22 a too little one, this option makes it easy to play with the size.
28 Set the initialization priority number. Do not mess with it unless
31 might need it too). And of course it has to start before the net stack.
|
| /Zephyr-Core-3.4.0/scripts/kconfig/ |
| D | kconfigfunctions.py | 57 to an EDT node. If it finds an EDT node, it will look to see if that node
229 is out of range it will return 0.
252 to an EDT node. If it finds an EDT node, it will look to see if that
276 to an EDT node. If it finds an EDT node, it will look to see if that node
314 This function takes a 'path' and looks for an EDT node at that path. If it
315 finds an EDT node, it will look to see if that node has a register at the
340 This function takes a 'path' and looks for an EDT node at that path. If it
341 finds an EDT node, it will look to see if that node has a register at the
380 This function takes the 'node_search_function' and uses it to search for
382 inside the node and is a boolean, if it is true, returns "y".
[all …]
|
| /Zephyr-Core-3.4.0/drivers/timer/ |
| D | Kconfig.riscv_machine | 20 timer driver. It provides the standard "system clock driver" interfaces.
32 When N=2, it is divided by 4, and when N=5, it is divided by 32.
34 It is normal configuration for RISC-V machine clock.
38 and it is desirable usage that references it with using a function such as
|
| /Zephyr-Core-3.4.0/samples/subsys/nvs/src/ |
| D | main.c | 7 * and writing data it also shows how data can be deleted from flash.
20 * Every reboot increases the values of the reboot_counter and updates it in
27 * basic nvs_read() function as it has been deleted. It is possible to read the
102 * read it from flash, since we don't know the size read the in main()
106 if (rc > 0) { /* item was found, show it */ in main()
108 } else {/* item was not found, add it */ in main()
114 /* KEY_ID is used to store a key, lets see if we can read it from flash in main()
117 if (rc > 0) { /* item was found, show it */ in main()
123 } else {/* item was not found, add it */ in main()
124 printk("No key found, adding it at id %d\n", KEY_ID); in main()
[all …]
|
| /Zephyr-Core-3.4.0/drivers/espi/ |
| D | Kconfig.espi_emul | 11 it does not talk to real hardware. Instead it talks to emulation
12 drivers that pretend to be devices on the emulated eSPI bus. It is
16 number of required pins. It includes the functionality of LPC, SMB, SPI
18 specification for more details (it is good for the introduction as well)
|
| /Zephyr-Core-3.4.0/doc/develop/api/ |
| D | terminology.rst | 25 if the function may return before the operation it initializes is
47 is invoked by a thread it is possible for that thread to be suspended as
78 unless that thread has explicitly invoked an operation that caused it to
83 suspend, wait, or invoke :c:func:`k_yield` before it can complete
108 long as it can be completed immediately, and to return an error code
109 rather than sleep if it cannot.
111 It is use of the no-wait feature that allows functions like
112 :c:func:`k_sem_take` to be invoked from ISRs, since it is not
126 The isr-ok attribute is used on a function to indicate that it works
127 whether it is being invoked from interrupt or thread context.
[all …]
|
| /Zephyr-Core-3.4.0/arch/xtensa/core/ |
| D | README-WINDOWS.rst | 33 There is an ENTRY instruction that does the rotation. It adds CALLINC
36 immediate offset from it to make space for the new frame.
38 There is a RETW instruction that undoes the rotation. It reads the
44 return value format and is used immediately, so it makes more sense
45 for it to use processor state instead.
51 WINDOWSTART stores a bitmask with one bit per hardware quad (so it's 8
56 each call frame that is live in hardware registers, and it will be
62 indicating it's valid. If it does not, the registers must have been
69 registers, but it's possible to hit registers 12 out from WINDOWBASE,
70 so it's actually possible to trap again when the instruction restarts
[all …]
|
| /Zephyr-Core-3.4.0/samples/sensor/grow_r502a/ |
| D | README.rst | 12 #. When SENSOR_ATTR_RECORD_FREE_IDX is set then it search for free index in sensor library.
13 #. When SENSOR_ATTR_RECORD_ADD is set then it adds a new fingerprint to the sensor.
14 …hen SENSOR_ATTR_RECORD_FIND is set then it tries to find a match for the input fingerprint. On fin…
15 #. When SENSOR_ATTR_RECORD_DEL is set then it deletes a fingerprint from the sensor.
20 #. On successful addition or deletion of fingerprint it will flash in blue three times.
21 #. On finding a match for the input fingerprint it will flash in purple.
22 #. In all other cases it will flash in red.
|
| /Zephyr-Core-3.4.0/doc/services/pm/ |
| D | device_runtime.rst | 11 devices which are idle or not used independently of the system state. It can be
13 driver is responsible to indicate when it needs the device and when it does not.
18 initially set to a :c:enumerator:`PM_DEVICE_STATE_SUSPENDED` indicating it is
19 not used. On the first device request, it will be resumed and so put into the
21 state until it is no longer used. At this point, the device will be suspended
24 :c:enumerator:`PM_DEVICE_STATE_SUSPENDED` state, whereas if it is performed
25 asynchronously, it will be put into the
60 When runtime PM is enabled on a device it will no longer be resumed or suspended
62 indicate when it needs a device and when it does not. The device runtime PM API
68 until the last sensor has finished using it.
[all …]
|
| /Zephyr-Core-3.4.0/tests/bluetooth/controller/mock_ctrl/src/ |
| D | util.c | 55 * - It shall have no more than six consecutive zeros or ones.
56 * - It shall not be the advertising channel packets' Access Address.
57 * - It shall not be a sequence that differs from the advertising channel
59 * - It shall not have all four octets equal.
60 * - It shall have no more than 24 transitions.
61 * - It shall have a minimum of two transitions in the most significant six
65 * - It shall have at least three ones in the least significant 8 bits.
66 * - It shall have no more than eleven transitions in the least significant 16
130 /* It shall have no more than six consecutive zeros or ones. */ in util_aa_le32()
131 /* It shall have a minimum of two transitions in the most in util_aa_le32()
[all …]
|
| /Zephyr-Core-3.4.0/samples/drivers/ipm/ipm_imx/ |
| D | README.rst | 9 Messaging Unit peripheral. It reads the received data from the Messaging Unit
10 using the IPM and transmits it back unchanged. The information about
12 it blocks until the data are read by the remote side.
28 The sample requires that data are being sent by the remote core so it can echo
29 it back. The other core is usually not running Zephyr but Linux on i.MX
33 It can be built as follows:
42 for how to load the Zephyr binary to the desired core and execute it.
47 The remote code is in the form of a loadable Linux kernel module. It creates
51 The remote code and the instructions how to build and run it are located at:
|
| /Zephyr-Core-3.4.0/tests/bluetooth/host/keys/bt_keys_update_usage/src/ |
| D | test_suite_save_aging_counter.c | 18 * It is defined in main.c.
23 * It is defined in main.c.
60 for (size_t it = 0; it < ARRAY_SIZE(testing_id_addr_pair_lut); it++) { in ZTEST() local
61 params_vector = &testing_id_addr_pair_lut[it]; in ZTEST()
64 expected_updated_keys = returned_keys_refs[it]; in ZTEST()
|
| /Zephyr-Core-3.4.0/subsys/logging/ |
| D | Kconfig.misc | 12 Deprecated. It is not used in the code.
32 Using VLA slightly decreases stack usage in some cases it may not be
47 for dead code. It is also required in immediate mode since it requires
54 When enabled, logs are kept in dedicated memory section. It allows
72 mode is tracked. It can be used to trim LOG_BUFFER_SIZE.
90 of dropped messages. It may contain additional information depending
|
| /Zephyr-Core-3.4.0/doc/develop/test/ |
| D | pytest.rst | 8 an improvement, please, let us know about it and open a GitHub issue/enhancement.*
13 Pytest is a python framework that *“makes it easy to write small, readable tests, and can scale to
15 Python is known for its free libraries and ease of using it for scripting. In addition, pytest
26 ``PYTHONPATH`` with path to this plugin, and then during pytest call, it appends the command with
41 If ``harness: pytest`` is used, twister delegates the test execution to pytest, by calling it as
51 By default, it points to ``pytest`` directory, located next to a directory with binary sources.
67 The first enables pytest-twister-harness plugin indirectly, as it is added with pytest.
68 It also gives access to ``dut`` fixture. The second is important for type checking and enabling
70 argument of a test function it gives access to a DeviceAbstract type object. The fixture yields a
80 cases, it is not the most convenient way, and it will be considered how to improve this
[all …]
|
| /Zephyr-Core-3.4.0/tests/bsim/bluetooth/mesh/tests_scripts/blob_mdls/ |
| D | blob_cli_caps.sh | 7 # The test instance sequence must stay as it is due to addressing scheme
12 # The test instance sequence must stay as it is due to addressing scheme
17 # The test instance sequence must stay as it is due to addressing scheme
22 # The test instance seqence must stay as it is due to addressing scheme
|
