Searched full:within (Results 1 – 25 of 653) sorted by relevance
12345678910>>...27
| /Zephyr-Core-3.6.0/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.crypto_modules | 14 Enables the random number generator module within the crypto partition.
21 Enables the KEY crypto module within the crypto partition.
29 Enables the AEAD crypto module within the crypto partition.
37 Enables the MAC crypto module within the crypto partition.
45 Enables the HASH crypto module within the crypto partition.
53 Enables the CIPHER crypto module within the crypto partition.
61 Enables the ASYM ENCRYPT crypto module within the crypto partition.
69 Enables the ASYM SIGN crypto module within the crypto partition.
77 Enables the KEY_DERIVATION crypto module within the crypto partition.
|
| /Zephyr-Core-3.6.0/include/zephyr/sys/ |
| D | mem_manage.h | 22 * @brief Check if a physical address is within range of physical memory.
24 * This checks if the physical address (@p virt) is within
36 * @return True if physical address is within range, false if not.
41 * @brief Check if a virtual address is within range of virtual memory.
43 * This checks if the virtual address (@p virt) is within
55 * @return True if virtual address is within range, false if not.
|
| D | device_mmio.h | 152 * Declare storage for MMIO information within a device's dev_data struct.
201 * @brief Declare storage for MMIO data within a device's config struct
247 * Initialize MMIO-related information within a specific instance of
334 * @brief Declare storage for MMIO data within a device's dev_data struct
363 * @param name Member name to use to store within dev_data.
379 * @param name Member name within dev_data
387 * @brief Declare storage for MMIO data within a device's config struct.
419 * @param name Member name to store within config
432 * @param name Member name within config
440 * Initialize MMIO-related information within a specific instance of
[all …]
|
| /Zephyr-Core-3.6.0/include/zephyr/drivers/mm/ |
| D | mm_drv_bank.h | 12 * driver to track page usage within memory banks.
30 * track page usage within memory banks.
70 * This function is used to update the number of mapped pages within the
75 * @return The number of pages mapped within the memory bank
82 * This function is used to update the number of unmapped pages within the
87 * @return The number of unmapped pages within the memory bank
|
| /Zephyr-Core-3.6.0/doc/kernel/data_structures/ |
| D | rbtree.rst | 19 within an rbtree must be provided as a predicate function by the user.
25 not allowed, nodes within a tree must have a single fixed order for
28 As with the slist and dlist containers, nodes within an rbtree are
30 user-managed memory, typically embedded within the data structure
31 being tracked in the tree. Unlike the list code, the data within an
37 with :c:func:`rb_remove`. Access to the "first" and "last" nodes within a
41 provided node pointer exists as an element within the tree. As
104 within the binary tree. Traversal of a tree for rebalancing following
|
| D | index.rst | 7 used within the kernel, but useful by application code in general.
16 expectation is that the node will be itself embedded within a
|
| /Zephyr-Core-3.6.0/doc/security/ |
| D | reporting.rst | 11 acknowledged and analyzed by the security response team within 1 week.
21 Issues within this bug tracking system will transition through a
71 appropriate branch within Zephyr.
106 within the Zephyr project to fix the issues, and 60 days for external
119 CVEs to these PRs (this information is within the Github security
151 status within the project. This information is intended to allow them
170 - Backport plans within the Zephyr project.
175 Each security issue fixed within zephyr shall be backported to the
202 - Maintainers will have access to all information within their domain
|
| /Zephyr-Core-3.6.0/drivers/mm/ |
| D | mm_drv_bank.c | 9 * @brief Module for tracking page use within memory banks
11 * The memory management drivers may use the routines within this module
12 * to track page use within their memory banks. This information in turn
|
| /Zephyr-Core-3.6.0/samples/drivers/led_is31fl3733/ |
| D | Kconfig | 12 to drive LEDs within this range.
20 LEDs within this range.
|
| /Zephyr-Core-3.6.0/subsys/fs/ |
| D | fs_impl.h | 23 * @param mp a pointer to the mount point within which @p path is found
25 * @return the absolute path within the mount point. Behavior is
|
| /Zephyr-Core-3.6.0/doc/hardware/peripherals/ |
| D | regulators.rst | 12 that a devicetree node directly depends on. Within the driver for the node the
20 controlled within the driver for the corresponding node, e.g. a sensor.
|
| /Zephyr-Core-3.6.0/subsys/fs/nvs/ |
| D | nvs_priv.h | 36 uint16_t offset; /* data offset within sector */
37 uint16_t len; /* data len within sector */
|
| /Zephyr-Core-3.6.0/ |
| D | LICENSE | 64 subsequently incorporated within the Work.
84 or a Contribution incorporated within the Work constitutes direct
109 within such NOTICE file, excluding those notices that do not
111 of the following places: within a NOTICE text file distributed
112 as part of the Derivative Works; within the Source form or
114 within a display generated by the Derivative Works, if and
118 notices within Derivative Works that You distribute, alongside
187 identification within third-party archives.
|
| /Zephyr-Core-3.6.0/drivers/ipm/ |
| D | Kconfig.intel_adsp | 26 Location of the host-writable inbox window within the
37 within the pre-existing window 0 (this is not the same as
|
| /Zephyr-Core-3.6.0/subsys/net/lib/tftp/ |
| D | Kconfig | 36 However, if it doesn't arrive within the given time we will re-transmit
37 the request to the server in hopes that the server will respond within
|
| /Zephyr-Core-3.6.0/arch/x86/include/ |
| D | kernel_arch_func.h | 65 * @brief Check if a memory address range falls within the stack
67 * Given a memory address range, ensure that it falls within the bounds
74 * @return true if addr/size region is not within the thread stack
|
| /Zephyr-Core-3.6.0/doc/services/storage/fcb/ |
| D | fcb.rst | 19 Entries in the flash contain the length of the entry, the data within
54 - Within callback function copy in data from the entry using
55 :c:func:`flash_area_read`. You can tell when all data from within a sector
|
| /Zephyr-Core-3.6.0/samples/bluetooth/extended_adv/ |
| D | README.rst | 23 scanner from within the `recycled` callback exposes the application to deadlocking.
55 Initiating disconnect within 5 seconds...
62 Initiating disconnect within 5 seconds...
|
| /Zephyr-Core-3.6.0/soc/arm/nxp_kinetis/kv5x/ |
| D | wdog.S | 48 * This sequence must execute within 20 clock cycles, so disable
63 * Writes to control/configuration registers must execute within
|
| /Zephyr-Core-3.6.0/boards/arm/udoo_neo_full_m4/ |
| D | udoo_neo_full_m4.dts | 14 * usually within DDR.
22 * usually within DDR.
|
| /Zephyr-Core-3.6.0/subsys/mgmt/mcumgr/grp/fs_mgmt/ |
| D | Kconfig | 45 size/offset within CBOR frame with file chunk.
51 size/offset within CBOR frame with file chunk.
60 Maximal byte length of encoded offset/size, within transferred
63 as it selects sizes of fields within headers.
|
| /Zephyr-Core-3.6.0/subsys/mgmt/mcumgr/smp/ |
| D | Kconfig | 19 the one that encapsulates everything within response.
74 be expected to be decoded within different command groups.
130 be encoded within different comm&& groups.
|
| /Zephyr-Core-3.6.0/doc/safety/ |
| D | index.rst | 7 for ensuring safety is addressed within the Zephyr project.
|
| /Zephyr-Core-3.6.0/samples/boards/nrf/dynamic_pinctrl/ |
| D | Kconfig | 10 Initialization priority of the remap routine within the PRE_KERNEL1 level.
|
| /Zephyr-Core-3.6.0/dts/bindings/sd/ |
| D | zephyr,sdmmc-disk.yaml | 2 Zephyr MMC disk node. A binding with this compatible present within an SD
|
12345678910>>...27
