Searched full:comparing (Results 1 – 25 of 53) sorted by relevance
123
16 RDP1 is enabled by comparing it to some hardcoded value. The byte has to
25 * @brief Function comparing two datasets.
44 calibration by comparing the RTC_SLOW_CLK frequency with main XTAL
52 enabled, we find the target redistributor by comparing the aff0 only.
47 /* Test RTR flag conversion after comparing data payload */ in ZTEST()87 /* Test RTR flag conversion after comparing data payload */ in ZTEST()
94 * @param[out] epsilon Tolerance to use comparing expected and actual values to account for rounding151 * well as the increment (value per LSB) which can be used as an epsilon when comparing results.
160 to the result. The offset can be obtained by comparing
12 // Comparing result of strcmp with 0
80 /* Lazy run, comparing pointers only assuming that compiler will be able to store in zcbor_map_decode_bulk_key_found()
24 The following combinations are suggested for comparing ROM sizes in different
87 /* Skip comparing Timestamp */ in validate_log_type()
66 At its heart, the external testing is actually comparing two clocks: one on
85 * and comparing it with cpuid. in sqn_hwspinlock_lock()
40 Comparing the :zephyr_file:`boards/arm/mps2/mps2_an521_cpu0.dts` and
17 Diffconfig is a simple utility for comparing two .config files.
63 * The head and tail of the list can be detected by comparing the
27 * connection failure is intentional. It's useful for comparing against
20 `CONFIG_LOG_BLOCK_IN_THREAD`, and they can all be characterized by comparing
143 # adjust origin includes before comparing
40 * after they occur, which requires comparing "deadline" to "now" with enough
131 * to fire. The user can detect a spurious event by comparing absolute time
169 * to fire. The user can detect a spurious event by comparing absolute time
125 * Check if next window is invalid by comparing
149 * of rbtree are in logarithmic time by comparing a node's operation
125 bool "Use build number while comparing image version"
