Home
last modified time | relevance | path

Searched refs:timing (Results 1 – 17 of 17) sorted by relevance

/tests/drivers/can/timing/src/
A Dmain.c73 const uint32_t ts = 1 + timing->prop_seg + timing->phase_seg1 + timing->phase_seg2; in assert_bitrate_correct()
83 bitrate_calc = core_clock / timing->prescaler / ts; in assert_bitrate_correct()
125 const uint32_t ts = 1 + timing->prop_seg + timing->phase_seg1 + timing->phase_seg2; in assert_sp_within_margin()
126 const uint16_t sp_calc = ((1 + timing->prop_seg + timing->phase_seg1) * 1000) / ts; in assert_sp_within_margin()
148 struct can_timing timing = { 0 }; in test_timing_values() local
178 timing.sjw, timing.prop_seg, timing.phase_seg1, timing.phase_seg2, in test_timing_values()
179 timing.prescaler); in test_timing_values()
181 assert_bitrate_correct(dev, &timing, test->bitrate); in test_timing_values()
182 assert_timing_within_bounds(&timing, min, max); in test_timing_values()
186 err = can_set_timing_data(dev, &timing); in test_timing_values()
[all …]
/tests/arch/common/timing/
A Dtestcase.yaml7 arch.common.timing:
9 - timing
/tests/kernel/sleep/
A Dtestcase.yaml2 kernel.common.timing:
10 kernel.common.timing.minimallibc:
/tests/drivers/stepper/stepper_api/
A DKconfig9 int "Stepper timing tolerance percentage"
12 Additional margin (%) added to step timing during test timeouts.
/tests/drivers/can/timing/
A Dtestcase.yaml2 drivers.can.timing:
A DKconfig4 mainmenu "CAN timing test"
/tests/drivers/mspi/flash/boards/
A Dapollo3p_evb.overlay47 ambiq,timing-config-mask = <3>;
48 ambiq,timing-config = <0 8 0 0 0 0 0 0>;
/tests/kernel/usage/thread_runtime_stats/
A Dtestcase.yaml5 # exhibit precision timing anomalies related to emulation.
/tests/kernel/timer/timer_behavior/dts/bindings/
A Dtimer-behavior-external.yaml19 that will collect timing information.
/tests/drivers/can/api/src/
A Dcanfd.c483 struct can_timing timing; in ZTEST_USER() local
486 err = can_calc_timing_data(can_dev, &timing, TEST_BITRATE_3, 1000); in ZTEST_USER()
527 struct can_timing timing = { 0 }; in ZTEST_USER() local
530 err = can_calc_timing_data(can_dev, &timing, TEST_BITRATE_3, TEST_SAMPLE_POINT); in ZTEST_USER()
533 err = can_set_timing_data(can_dev, &timing); in ZTEST_USER()
A Dclassic.c537 struct can_timing timing; in ZTEST_USER() local
540 err = can_calc_timing(can_dev, &timing, TEST_BITRATE_1, 1000); in ZTEST_USER()
1396 struct can_timing timing = { 0 }; in ZTEST_USER() local
1399 err = can_calc_timing(can_dev, &timing, TEST_BITRATE_1, TEST_SAMPLE_POINT); in ZTEST_USER()
1402 err = can_set_timing(can_dev, &timing); in ZTEST_USER()
/tests/drivers/sdhc/src/
A Dmain.c32 io.timing = SDHC_TIMING_LEGACY; in sdhc_power_on()
88 io.timing = SDHC_TIMING_LEGACY; in ZTEST()
/tests/drivers/pwm/pwm_gpio_loopback/
A DKconfig23 int "Allowed deviation (%) for PWM timing checks"
/tests/kernel/timer/timer_behavior/
A DKconfig51 tool (such as a logic analyzer) to gather timing data. A pytest harness
/tests/drivers/can/shell/src/
A Dmain.c56 static int can_shell_test_capture_timing(const struct device *dev, const struct can_timing *timing) in can_shell_test_capture_timing() argument
60 memcpy(&timing_capture, timing, sizeof(timing_capture)); in can_shell_test_capture_timing()
/tests/bsim/bluetooth/mesh/
A DREADME.rst117 subsystems, so timing requirements should generally be kept fairly liberal to
/tests/drivers/build_all/display/
A Dapp.overlay379 compatible = "zephyr,panel-timing";

Completed in 33 milliseconds