| /Zephyr-latest/tests/boards/nrf/coresight_stm/pytest/ |
| D | test_stm.py | 68 def _check_benchmark_results(output: str, core: str, constraints: STMLimits) -> None:
78 "expected": constraints.log_0_arg,
82 "expected": constraints.log_1_arg,
86 "expected": constraints.log_2_arg,
90 "expected": constraints.log_3_arg,
94 "expected": constraints.log_str,
98 "expected": constraints.tracepoint,
102 "expected": constraints.tracepoint_d32,
111 threshold = cfg[check]["expected"] * (1 + constraints.tolerance)
240 _check_benchmark_results(output=output, core='app', constraints=app_constraints)
[all …]
|
| /Zephyr-latest/subsys/pm/policy/ |
| D | policy_device_lock.c | 16 struct pm_state_constraint *constraints; member
76 .constraints = PM_CONSTRAINTS_NAME(node_id), \
97 _devices_constraints[i].constraints[j].state, in pm_policy_device_power_lock_get()
98 _devices_constraints[i].constraints[j].substate_id); in pm_policy_device_power_lock_get()
113 _devices_constraints[i].constraints[j].state, in pm_policy_device_power_lock_put()
114 _devices_constraints[i].constraints[j].substate_id); in pm_policy_device_power_lock_put()
|
| D | Kconfig | 15 on CPU residency times and other constraints imposed by the drivers or
27 bool "Power state constraints per device"
31 This used to set and release power state constraints when
|
| /Zephyr-latest/soc/ti/simplelink/cc13x2_cc26x2/ |
| D | power.c | 65 uint32_t constraints; in pm_state_set() local
80 constraints = Power_getConstraintMask(); in pm_state_set()
93 if ((constraints & (1 << PowerCC26XX_NEED_FLASH_IN_IDLE)) || in pm_state_set()
|
| /Zephyr-latest/soc/ti/simplelink/cc13x2x7_cc26x2x7/ |
| D | power.c | 66 uint32_t constraints; in pm_state_set() local
81 constraints = Power_getConstraintMask(); in pm_state_set()
94 if ((constraints & (1 << PowerCC26XX_NEED_FLASH_IN_IDLE)) || in pm_state_set()
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | mpu_stack_objects.rst | 36 During stack creation, a set of constraints are enforced on the allocation of
37 memory. These constraints include determining the alignment of the stack and
39 constraints are used to place the stacks properly.
41 The main source of the memory constraints is the MPU design for the SoC. The
42 MPU design may require specific constraints on the region definition. These
51 v7m MPU will have these constraints.
61 Size and alignment constraints may result in stack allocations being larger
|
| D | memory_domain.rst | 186 to the following constraints:
190 underlying hardware constraints. For example, many MPU-based systems require
|
| D | overview.rst | 178 There are some constraints if additional application binary data is loaded
|
| /Zephyr-latest/samples/subsys/nvs/boards/ |
| D | nucleo_wb55rg.overlay | 11 /* Set 12KB of storage at the end of 1st half of flash (dual core constraints) */
|
| /Zephyr-latest/drivers/disk/ |
| D | Kconfig.flash | 19 Enable runtime zephyr,flash-disk partition page layout constraints
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 14 local constraints, such as low battery power or changes in topology. For these
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 25 related constraints.
34 related constraints. Dynamic threads are a subset of all other CMSIS
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 12 During the development of west, a set of :ref:`west-design-constraints` were
85 .. _west-design-constraints:
|
| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 32 feature as it is being designed, and incorporate important constraints into the
|
| /Zephyr-latest/doc/kernel/services/ |
| D | index.rst | 71 do not have alignment constraints, but use temporary memory from the
|
| /Zephyr-latest/samples/ |
| D | sample_definition_and_criteria.rst | 80 resource constraints. Ideally, one platform should be enough to verify the
|
| /Zephyr-latest/doc/services/pm/ |
| D | system.rst | 92 Other constraints placed upon the decision may include locks disallowing certain power states,
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 74 order given the linker constraints described above (i386 doesn't have
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | smp_transport.rst | 40 are no real protocol constraints that require that limit.
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 148 Adding more constraints, the Zephyr project has demanding policies
152 Put together, all these constraints can make writing header files very
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | shields.rst | 56 timing constraints, etc), in order to enable it for proper operation with the
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | index.rst | 173 Depending on configuration, there are several constraints that must be
187 The alignment constraints can be quite restrictive, for example some MPUs
478 still used, but there are additional constraints which must be met or the
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 140 specification requires the application to obey certain constraints.
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 34 2. The underlying architecture may impose constraints on the bounds of
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | fatal.rst | 249 this function for additional details and constraints.
|
