Home
last modified time | relevance | path

Searched refs:millisecond (Results 1 – 19 of 19) sorted by relevance

/Zephyr-latest/doc/connectivity/networking/api/
Dnet_timeout.rst13 Zephyr's network infrastructure mostly uses the millisecond-resolution uptime
27 seconds, which corresponds to a 42-bit millisecond count.
55 in some applications, as it does allow a millisecond-resolution calculation of
/Zephyr-latest/tests/drivers/gnss/gnss_nmea0183/src/
Dmain.c98 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()
/Zephyr-latest/scripts/coccinelle/
Dms_timeout.cocci18 // ** Handle millisecond timeout as the last parameter
81 // ** Handle millisecond timeout as second from last parameter
139 // ** Handle millisecond timeout as third from last parameter
Dint_ms_to_timeout.cocci231 // and replace with the corresponding millisecond duration.
278 msg = "WARNING: replace timeout-valued delay with millisecond duration".format()
/Zephyr-latest/samples/drivers/gnss/
DREADME.rst25 …gnss: gnss_time: {hour: 16, minute: 17, millisecond 36000, month_day 3, month: 10, century_year: 2…
/Zephyr-latest/drivers/gnss/
Dgnss_emul.c371 uint16_t millisecond; in gnss_emul_set_utc() local
376 millisecond = (uint16_t)(data->fix_timestamp_ms % 1000) in gnss_emul_set_utc()
380 data->data.utc.millisecond = millisecond; in gnss_emul_set_utc()
Dgnss_dump.c124 ret = snprintk(str, strsize, fmt, utc->hour, utc->minute, utc->millisecond, in gnss_dump_time()
Dgnss_nmea0183.c342 utc->millisecond = (uint16_t)i64; in gnss_nmea0183_parse_hhmmss()
/Zephyr-latest/tests/drivers/gnss/gnss_dump/src/
Dmain.c36 test_data.utc.millisecond = 3; in test_gnss_data()
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig365 Timeout for waiting HDR Signure. Unit is millisecond.
372 Waiting time after firmware is uploaded. Unit is millisecond.
379 Waiting time after controller baudrate is updated. Unit is millisecond.
/Zephyr-latest/include/zephyr/drivers/
Dgnss.h158 uint16_t millisecond; member
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst57 millisecond input value to the next higher number of ticks, returning
268 Subsystems that keep millisecond APIs
283 been able to accept this value to their millisecond API in the past no
/Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt/
DKconfig148 bool "Support millisecond field in datetime commands"
/Zephyr-latest/doc/kernel/
Dtimeutil.rst13 ``CLOCK_MONOTONIC_RAW``. :c:func:`k_uptime_get()` provides a millisecond
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst193 force :kconfig:option:`CONFIG_CDC_ACM_TX_DELAY_MS` millisecond delay before real
/Zephyr-latest/kernel/
DKconfig815 of cycles per tick should be chosen so that 1 millisecond is exactly
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split477 the Periodic Advertising Interval shall be 10 millisecond more than
/Zephyr-latest/doc/releases/
Drelease-notes-2.3.rst192 type instead of a 32 bit millisecond count. These can be
Drelease-notes-2.5.rst68 legacy/deprecated millisecond counts.