Home
last modified time | relevance | path

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

/Zephyr-latest/subsys/shell/modules/kernel_service/
Duptime.c20 int64_t hours; in cmd_kernel_uptime() local
37 hours = milliseconds / HOURS_FACTOR; in cmd_kernel_uptime()
46 days, hours, minutes, seconds, milliseconds); in cmd_kernel_uptime()
/Zephyr-latest/include/zephyr/bluetooth/services/
Dcts.h48 uint8_t hours; member
Dots.h510 uint8_t hours; member
/Zephyr-latest/subsys/bluetooth/services/
Dcts.c45 date_time.tm_hour = ct_time->hours; /* hours of day */ in bt_cts_time_to_unix_ms()
94 ct_time->hours = date_time.tm_hour; /* hours */ in bt_cts_time_from_unix_ms()
/Zephyr-latest/tests/drivers/build_all/fuel_gauge/
Dapp.overlay62 charge-full-design-microamp-hours = <1350000>;
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_timeout.rst15 32-bit unsigned values. The 32-bit value rolls over at 49 days 17 hours 2 minutes
22 number (``INT32_MAX``), which overflows at 24 days 20 hours 31 minutes 23.648
/Zephyr-latest/subsys/logging/
Dlog_output.c254 uint32_t hours; in timestamp_print() local
258 hours = seconds / 3600U; in timestamp_print()
259 seconds -= hours * 3600U; in timestamp_print()
264 hours, mins, seconds, ms, us); in timestamp_print()
/Zephyr-latest/drivers/rtc/
DKconfig.pcf852326 Offset correction is made once per two hours and then correction pulses are applied once
/Zephyr-latest/tests/kernel/timer/starve/
DREADME.txt12 minutes, hours, or days to fail, depending on the hardware clock rate
/Zephyr-latest/tests/drivers/build_all/sensor/
Dadc.dtsi46 charge-full-design-microamp-hours = <1000000>;
/Zephyr-latest/boards/nordic/thingy53/
Dthingy53_nrf5340_common.dtsi101 charge-full-design-microamp-hours = <1350000>;
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst83 set in 10-second increments, up to 182 hours, in addition to the base time of 20 seconds. The wait
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig1564 in Progress, we need to keep track of how many hours has passed
1566 the state at least for 96 hours (Update in Progress has an
1567 additional upper limit of 144 hours).
1571 how many hours the node has been in the state. This doesn't
1582 state is saved every 24 hours (96 / 4).
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv6275 value. The value is in minutes. Default value is 23 hours (23*60).
/Zephyr-latest/doc/project/
Dproject_roles.rst382 * A minimum review period of 2 business days, 4 hours for trivial changes (see
/Zephyr-latest/subsys/bluetooth/services/ots/
Dots_client.c260 p_date_time->hours = net_buf_simple_pull_u8(buf); in date_time_decode()
/Zephyr-latest/doc/contribute/
Dguidelines.rst949 #. Revisit PR after 1-2 hours to see the status of all CI checks, make sure all
/Zephyr-latest/doc/releases/
Drelease-notes-2.4.rst1671 * :github:`23319` - hci interface stopped working after few hours/days
Drelease-notes-3.3.rst3188 * :github:`52632` - MQTT over WebSockets: After hours of running time receiving published messages …