Home
last modified time | relevance | path

Searched full:timing (Results 1 – 25 of 442) sorted by relevance

12345678910>>...18

/Zephyr-latest/tests/drivers/can/timing/src/
Dmain.c25 * @brief Defines a set of CAN timing test values
35 * @brief List of CAN timing values to test.
52 * @brief List of CAN FD data phase timing values to test.
66 * @brief Assert that a CAN timing struct matches the specified bitrate
68 * Assert that the values of a CAN timing struct matches the specified bitrate
72 * @param timing pointer to the CAN timing struct
75 static void assert_bitrate_correct(const struct device *dev, struct can_timing *timing, in assert_bitrate_correct() argument
78 const uint32_t ts = 1 + timing->prop_seg + timing->phase_seg1 + timing->phase_seg2; in assert_bitrate_correct()
83 zassert_not_equal(timing->prescaler, 0, "prescaler is zero"); in assert_bitrate_correct()
88 bitrate_calc = core_clock / timing->prescaler / ts; in assert_bitrate_correct()
[all …]
/Zephyr-latest/samples/boards/nordic/coresight_stm/
DREADME.rst10 Also, it prints timing for different log messages.
73 rad: Timing for log message with 0 arguments: 5.10us
74 rad: Timing for log message with 1 argument: 6.10us
75 rad: Timing for log message with 2 arguments: 6.0us
76 rad: Timing for log message with 3 arguments: 6.40us
77 rad: Timing for log_message with string: 7.10us
78 rad: Timing for tracepoint: 0.5us
79 rad: Timing for tracepoint_d32: 0.5us
80 flpr: Timing for log message with 0 arguments: 1.20us
81 flpr: Timing for log message with 1 argument: 1.20us
[all …]
Dsample.yaml43 - "Timing for log message with 0 arguments:"
44 - "Timing for log message with 1 argument:"
45 - "Timing for log message with 2 arguments:"
46 - "Timing for log message with 3 arguments:"
47 - "Timing for log_message with string:"
/Zephyr-latest/include/zephyr/timing/
Dtiming.h11 #include <zephyr/timing/types.h>
18 * @brief Timing Measurement APIs
19 * @defgroup timing_api Timing Measurement APIs
22 * The timing measurement APIs can be used to obtain execution
25 * Please note that the timing functions may use a different timer
31 * @brief SoC specific Timing Measurement APIs
32 * @defgroup timing_api_soc SoC specific Timing Measurement APIs
35 * Implements the necessary bits to support timing measurement
36 * using SoC specific timing measurement mechanism.
42 * @brief Initialize the timing subsystem on SoC.
[all …]
/Zephyr-latest/tests/boards/nrf/coresight_stm/
Dtestcase.yaml60 - "Timing for log message with 0 arguments:"
61 - "Timing for log message with 1 argument:"
62 - "Timing for log message with 2 arguments:"
63 - "Timing for log message with 3 arguments:"
64 - "Timing for log_message with string:"
79 - "Timing for log message with 0 arguments:"
80 - "Timing for log message with 1 argument:"
81 - "Timing for log message with 2 arguments:"
82 - "Timing for log message with 3 arguments:"
83 - "Timing for log_message with string:"
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dusbc_tc.h45 * See Table 4-29 VBUS and VCONN Timing Parameters
52 * See Table 4-29 VBUS and VCONN Timing Parameters
58 * See Table 4-29 VBUS and VCONN Timing Parameters
65 * See Table 4-29 VBUS and VCONN Timing Parameters
72 * See Table 4-29 VBUS and VCONN Timing Parameters
79 * See Table 4-29 VBUS and VCONN Timing Parameters
85 * See Table 4-30 DRP Timing Parameters
91 * See Table 4-30 DRP Timing Parameters
98 * See Table 4-30 DRP Timing Parameters
105 * See Table 4-30 DRP Timing Parameters
[all …]
/Zephyr-latest/doc/kernel/timing_functions/
Dindex.rst6 The timing functions can be used to obtain execution time of
9 Please note that the timing functions may use a different timer
16 To allow using the timing functions, :kconfig:option:`CONFIG_TIMING_FUNCTIONS`
22 To gather timing information:
27 timing information. This usually starts the timer.
41 7. Repeat from step 3 to gather timing information for other
45 timing information. This usually stops the timer.
50 This shows an example on how to use the timing functions:
54 #include <zephyr/timing/timing.h>
/Zephyr-latest/subsys/timing/
DKconfig6 bool "Timing Functions"
8 When enabled, timing related functions are compiled. This is
9 useful for gathering timing on code execution.
15 Hidden option to indicate that timing functions need to be
19 to use timing functions.
/Zephyr-latest/drivers/w1/
Dw1_zephyr_gpio.c14 * follows the timing specifications for 1-Wire communication.
35 * The time critical sections are used to ensure that the timing
49 * Standard timing between communication operations:
63 * Overdrive timing between communication operations:
103 /** timing parameters for 1-Wire communication */
104 const struct w1_gpio_timing *timing; member
141 const struct w1_gpio_timing *timing = data->timing; in w1_gpio_reset_bus() local
146 W1_GPIO_WAIT_US(timing->g); in w1_gpio_reset_bus()
152 W1_GPIO_WAIT_US(timing->h); in w1_gpio_reset_bus()
158 W1_GPIO_WAIT_US(timing->i); in w1_gpio_reset_bus()
[all …]
/Zephyr-latest/drivers/stepper/step_dir/
Dstep_dir_stepper_timing_source.h12 * @brief Initialize the stepper timing source.
20 * @brief Update the stepper timing source.
29 * @brief Start the stepper timing source.
37 * @brief Whether the stepper timing source requires rescheduling (keeps running
41 * @return true if the timing source requires rescheduling, false otherwise.
46 * @brief Stop the stepper timing source.
54 * @brief Check if the stepper timing source is running.
57 * @return true if the timing source is running, false otherwise.
62 * @brief Stepper timing source API.
/Zephyr-latest/dts/bindings/memory-controllers/
Datmel,sam-smc.yaml27 atmel,smc-setup-timing = <1 1 1 1>;
28 atmel,smc-pulse-timing = <6 6 6 6>;
29 atmel,smc-cycle-timing = <7 7>;
37 55ns, as per specification, it requires atmel,smc-cycle-timing of at least
38 7 pulses (56ns). The atmel,smc-cycle-timing is composed of three parts:
43 Note: Since no hold parameter is available at SMC the atmel,smc-cycle-timing
47 cycle-timing (7) = setup (1) + pulse (6) + hold (0)
50 cycle-timing (10) = setup (1) + pulse (6) + hold (3)
117 atmel,smc-setup-timing:
129 atmel,smc-pulse-timing:
[all …]
Dst,stm32-fmc-nor-psram.yaml63 st,timing = <4 2 3 0 16 17 STM32_FMC_ACCESS_MODE_A>;
108 * WAITCFG - Wait timing configuration.
112 If set, then 'st,timing-ext' shall be provided.
120 st,timing:
124 SRAM/NOR-Flash (read) timing register (FMC_BTRx).
129 'st,timing-ext' to configure write accesses.
172 st,timing-ext:
176 SRAM/NOR-Flash (write) timing register (FMC_BWTRx).
191 Refer to 'st,timing' for detailed field descriptions.
/Zephyr-latest/samples/boards/st/i2c_timing/
DREADME.rst18 a TIMING register to write in order to generate the correct I2C clock signal.
20 The calculation of that TIMING value can be given by the `STM32CubeMX`_ application
23 Because the code sequence to calculate the I2C V2 TIMING value is heavy,
26 retrieve timing register configuration for the defined ``clock-frequency``.
27 User can then configure timing in his application by adapting the following dts
71 The sample gives the corresponding TIMING value to report to the Device Tree:
75 I2C timing value, report to the DTS :
/Zephyr-latest/samples/boards/nordic/coresight_stm/pytest/
Dtest_stm.py60 rf"{core}: Timing for log message with 0 arguments: (.+)us", output
62 assert latency_msg_0_str is not None, "Timing for log message with 0 arguments NOT found"
65 rf"{core}: Timing for log message with 1 argument: (.+)us", output
67 assert latency_msg_1_str is not None, "Timing for log message with 1 argument NOT found"
70 rf"{core}: Timing for log message with 2 arguments: (.+)us", output
72 assert latency_msg_2_str is not None, "Timing for log message with 2 arguments NOT found"
75 rf"{core}: Timing for log message with 3 arguments: (.+)us", output
77 assert latency_msg_3_str is not None, "Timing for log message with 3 arguments NOT found"
80 rf"{core}: Timing for log_message with string: (.+)us", output
82 assert latency_msg_string_str is not None, "Timing for log_message with string NOT found"
[all …]
/Zephyr-latest/drivers/can/
Dcan_shell.c396 shell_print(sh, "timing: sjw %u..%u, prop_seg %u..%u, " in cmd_can_show()
408 shell_print(sh, "timing data: sjw %u..%u, prop_seg %u..%u, " in cmd_can_show()
438 struct can_timing timing = { 0 }; in cmd_can_bitrate_set() local
462 err = can_calc_timing(dev, &timing, bitrate, sample_pnt); in cmd_can_bitrate_set()
464 shell_error(sh, "failed to calculate timing for " in cmd_can_bitrate_set()
472 timing.sjw = (uint16_t)strtoul(argv[4], &endptr, 10); in cmd_can_bitrate_set()
482 timing.sjw); in cmd_can_bitrate_set()
485 timing.sjw, timing.prop_seg, timing.phase_seg1, timing.phase_seg2, in cmd_can_bitrate_set()
486 timing.prescaler); in cmd_can_bitrate_set()
488 err = can_set_timing(dev, &timing); in cmd_can_bitrate_set()
[all …]
Dcan_common.c130 * @brief Update the timing given a total number of time quanta and a sample point.
150 * @param min Pointer to the minimum supported timing parameter values.
151 * @param max Pointer to the maximum supported timing parameter values.
237 * @brief Internal function for calculating CAN timing parameters.
241 * @param min Pointer to the minimum supported timing parameter values.
242 * @param max Pointer to the maximum supported timing parameter values.
346 static int check_timing_in_range(const struct can_timing *timing, in check_timing_in_range() argument
350 if (!IN_RANGE(timing->sjw, min->sjw, max->sjw) || in check_timing_in_range()
351 !IN_RANGE(timing->prop_seg, min->prop_seg, max->prop_seg) || in check_timing_in_range()
352 !IN_RANGE(timing->phase_seg1, min->phase_seg1, max->phase_seg1) || in check_timing_in_range()
[all …]
Dcan_mcux_flexcan.c116 struct can_timing timing; member
137 const struct can_timing *timing) in mcux_flexcan_set_timing() argument
141 if (!timing) { in mcux_flexcan_set_timing()
149 data->timing = *timing; in mcux_flexcan_set_timing()
249 flexcan_timing_config_t timing; in mcux_flexcan_start() local
292 /* Delay this until start since setting the timing automatically exits freeze mode */ in mcux_flexcan_start()
293 timing.preDivider = data->timing.prescaler - 1U; in mcux_flexcan_start()
294 timing.rJumpwidth = data->timing.sjw - 1U; in mcux_flexcan_start()
295 timing.phaseSeg1 = data->timing.phase_seg1 - 1U; in mcux_flexcan_start()
296 timing.phaseSeg2 = data->timing.phase_seg2 - 1U; in mcux_flexcan_start()
[all …]
/Zephyr-latest/drivers/i2c/
Di2c_xilinx_axi.h30 REG_TSUSTA = 0x128, /* Timing Parameter */
31 REG_TSUSTO = 0x12C, /* Timing Parameter */
32 REG_THDSTA = 0x130, /* Timing Parameter */
33 REG_TSUDAT = 0x134, /* Timing Parameter */
34 REG_TBUF = 0x138, /* Timing Parameter */
35 REG_THIGH = 0x13C, /* Timing Parameter */
36 REG_TLOW = 0x140, /* Timing Parameter */
37 REG_THDDAT = 0x144, /* Timing Parameter */
/Zephyr-latest/dts/bindings/i2c/
Dst,stm32-i2c-v2.yaml26 An optional table of pre-computed i2c timing values with the
33 Because timing value is valid for a given I2C peripheral clock
34 frequency and target I2C bus clock, each timing value must be
38 clock-frequency timing>
/Zephyr-latest/drivers/mspi/
Dmspi_ambiq.h55 mspi_timing_cfg *timing = (mspi_timing_cfg *)cfg; \
56 timing->ui8TurnAround; \
61 mspi_timing_cfg *timing = (mspi_timing_cfg *)cfg; \
62 timing->ui8TurnAround = num; \
/Zephyr-latest/tests/arch/common/timing/
Dtestcase.yaml7 arch.common.timing:
9 - timing
/Zephyr-latest/tests/subsys/sd/sdio/src/
Dmain.c71 TC_PRINT("Card timing: SDR12\n"); in ZTEST()
74 TC_PRINT("Card timing: SDR25\n"); in ZTEST()
77 TC_PRINT("Card timing: SDR50\n"); in ZTEST()
80 TC_PRINT("Card timing: SDR104\n"); in ZTEST()
83 TC_PRINT("Card timing: DDR50\n"); in ZTEST()
86 zassert_unreachable("Card timing is not known value"); in ZTEST()
/Zephyr-latest/tests/kernel/sleep/
Dtestcase.yaml2 kernel.common.timing:
6 kernel.common.timing.minimallibc:
/Zephyr-latest/tests/subsys/sd/sdmmc/src/
Dmain.c204 TC_PRINT("Card timing: SDR12\n"); in ZTEST()
206 /* Card uses non UHS mode timing */ in ZTEST()
207 TC_PRINT("Card timing: Legacy\n"); in ZTEST()
212 TC_PRINT("Card timing: SDR25\n"); in ZTEST()
214 /* Card uses non UHS mode timing */ in ZTEST()
215 TC_PRINT("Card timing: High Speed\n"); in ZTEST()
219 TC_PRINT("Card timing: SDR50\n"); in ZTEST()
221 "Card must support UHS mode for this timing"); in ZTEST()
224 TC_PRINT("Card timing: SDR104\n"); in ZTEST()
226 "Card must support UHS mode for this timing"); in ZTEST()
[all …]
/Zephyr-latest/drivers/spi/
DKconfig.ambiq61 bool "Ambiq SPI-BLEIF timing trace"
65 configurable BLEIF timing observation functions on other exposed
66 pins. The user can enable it to configure the pins for timing

12345678910>>...18