Searched refs:millisecond (Results 1 – 4 of 4) sorted by relevance
| /tests/drivers/watchdog/wdt_basic_reset_none/ |
| A D | Kconfig | 13 due to the max window reaching the millisecond feed window.
22 due to the max window reaching the millisecond feed window.
|
| /tests/drivers/gnss/gnss_dump/ |
| A D | testcase.yaml | 19 - "gnss_dev: gnss_time: {hour: 0, minute: 0, millisecond 0, month_day 0, month: 0, \
25 - "gnss_dev: gnss_time: {hour: 1, minute: 2, millisecond 3, month_day 4, month: 5, \
|
| /tests/drivers/gnss/gnss_nmea0183/src/ |
| A D | main.c | 98 uint16_t millisecond; member
102 {.str = "000102", .hour = 0, .minute = 1, .millisecond = 2000},
103 {.str = "235959.999", .hour = 23, .minute = 59, .millisecond = 59999},
104 {.str = "000000.0", .hour = 0, .minute = 0, .millisecond = 0}
118 zassert_equal(hhmmss_samples[i].millisecond, utc.millisecond, in ZTEST()
288 zassert_equal(data.utc.millisecond, 49000, "Incorrectly parsed millisecond"); in ZTEST()
|
| /tests/drivers/gnss/gnss_dump/src/ |
| A D | main.c | 36 test_data.utc.millisecond = 3; in test_gnss_data()
|
Completed in 16 milliseconds