Searched full:functional (Results 1 – 25 of 144) sorted by relevance
123456
2 settings.functional.nvs:10 settings.functional.nvs.chosen:18 settings.functional.nvs.dk:
16 /* Functional / External Reset Status Register */20 /* Functional Event Reset Disable Register */22 /* Functional Bidirectional Reset Enable Register */24 /* Functional Reset Escalation Counter Register */28 /* Functional Reset Escalation Threshold Register */46 /* Functional Reset Entry Timeout Control Register */94 /* All functional reset sources generate a reset event */ in mc_rgm_init()
86 /** Functional Reset Mode */135 * SYS_REBOOT_WARM (Functional Reset):139 * preserved across functional reset.142 * - No BISTs are executed after functional reset.
2 settings.functional.fcb:14 settings.functional.fcb.chosen:
19 Functional Reset Escalation threshold.20 If the value of this property is 0, the Functional reset escalation21 function is disabled. Any other value is the number of Functional
47 * Class Functional Descriptors168 /** Header Functional Descriptor */176 /** Union Interface Functional Descriptor */185 /** Call Management Functional Descriptor */194 /** Abstract Control Management Functional Descriptor */220 /** Ethernet Networking Functional Descriptor */
69 /** DFU FUNCTIONAL descriptor type */72 /** DFU attributes DFU Functional Descriptor */81 /** Run-Time Functional Descriptor */
32 * OPERATION_MODE = 0x0 sets functional mode to protect requests based on35 * OPERATION_MODE = 0x1 sets functional mode to all requests not be protected and38 * OPERATION_MODE = 0x2 sets functional mode to protect all requests and ignore
11 SBS driver are functional.
24 * content during functional reset through a hardware mechanism, therefore accesses do not30 /* If we come from a destructive reset, then ignore functional reset flags */
7 peripherals. Child nodes are used to represent each functional block.
3 # but perfectly functional for any other STM32L4 board connected via
72 * Functional73 * Non-Functional95 * Verifiable (e.g. testable for functional requirements)
12 This overview is provided for people who are interested in the functional safety development part56 The IEC 61508 standard is a widely recognized international standard for functional safety of90 The IEC 61508 standard was selected because it serves as a foundational functional safety standard112 additional requirement caused by functional safety standards. Functional safety considers quality114 project regardless of the functional safety goals. The following list describes the quality goals
11 * locking interface is functional and the internal newlib locks function as191 * functions to verify that sinit lock is functional and its implementation261 * to verify that sfp lock is functional and its implementation is provided by331 * verify that malloc lock is functional and its implementation is provided by401 * that env lock is functional and its implementation is provided by the433 * tz lock is functional and its implementation is provided by the retargetable
17 functional support for the API.21 | In addition to providing functional support for the API, depending on34 | Its foremost goal is functional support for the API on all board targets.
12 * in this file are simple stubs without functional behavior.
24 * in this file are simple stubs without functional behavior.
23 be a functional wakeup source:73 - Functional Mode: High
167 still to be functional but approaching limit where it gets damaged.193 still to be functional but approaching limit where it gets damaged.221 assumed still to be functional but approaching limit where it gets247 assumed still to be functional but approaching limit where it gets
57 # The 15.4 driver Tx encryption is currently not functional with this
21 It's only intended for functional support.
7 #include <functional>
24 * to the next power of two; this restriction guarantees a functional VTOR
