Home
last modified time | relevance | path

Searched full:minutes (Results 1 – 25 of 73) sorted by relevance

123

/Zephyr-latest/subsys/shell/modules/kernel_service/
Duptime.c21 int64_t minutes; in cmd_kernel_uptime() local
39 minutes = milliseconds / MINUTES_FACTOR; in cmd_kernel_uptime()
45 "uptime: %llu days, %llu hours, %llu minutes, %llu seconds, %llu milliseconds", in cmd_kernel_uptime()
46 days, hours, minutes, seconds, milliseconds); in cmd_kernel_uptime()
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst90 first sector will be full after 1024/12 = 85.33 minutes. After another 85.33
91 minutes, the second sector is full. When this happens, because we're using
93 after 171 minutes of system time. With the expected device life of 20,000
94 writes, with two sectors writing every 171 minutes, the device should last
95 about 171 * 20,000 minutes, or about 6.5 years.
104 the expected device life (in minutes) can be calculated as::
106 SECTOR_COUNT * SECTOR_SIZE * PAGE_ERASES / (NS * (DS+8)) minutes
/Zephyr-latest/samples/fuel_gauge/max17048/src/
Dmain.c55 printk("Time to empty %d minutes\n", vals[0].runtime_to_empty); in main()
57 printk("Time to full %d minutes\n", vals[1].runtime_to_full); in main()
/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/drivers/fuel_gauge/bq27z746/
Dbq27z746.h16 #define BQ27Z746_ATRATETIMETOEMPTY 0x04 /* R/O, Unit: minutes, Range: 0..65535 */
24 #define BQ27Z746_AVERAGETIMETOEMPTY 0x16 /* R/O, Unit: minutes, Range: 0..65535 */
25 #define BQ27Z746_AVERAGETIMETOFULL 0x18 /* R/O, Unit: minutes, Range: 0..65535 */
27 #define BQ27Z746_MAXLOADTIMETOEMPTY 0x20 /* R/O, Unit: minutes, Range: 0..65535 */
/Zephyr-latest/tests/lib/heap/
Dtestcase.yaml3 # minutes (vs. ~20 seconds for qemu) to complete in CI. There's
/Zephyr-latest/tests/kernel/fpu_sharing/generic/
DCMakeLists.txt8 # output being in the range of every few seconds to every few minutes. To
/Zephyr-latest/samples/boards/enjoydigital/litex/i2s/
DREADME.rst36 It seems that after a few minutes some music delay occurs, this is because the sound driver is not …
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/
Dpriv_proxy_net_id.sh14 # 3. RX device waits for 10 minutes.
/Zephyr-latest/subsys/mgmt/hawkbit/
DKconfig30 int "Time to poll interval (in minutes)"
35 This time interval is zero and 43200 minutes(30 days). This will be overridden
/Zephyr-latest/subsys/mgmt/updatehub/
DKconfig31 int "Time to poll interval (in minutes)"
36 This time interval is zero and 43200 minutes(30 days).
/Zephyr-latest/tests/kernel/timer/starve/
DREADME.txt12 minutes, hours, or days to fail, depending on the hardware clock rate
/Zephyr-latest/include/zephyr/drivers/
Dfuel_gauge.h59 /** Remaining battery life time in minutes */
61 /** Remaining time in minutes until battery reaches full charge */
87 /** AtRateTimeToFull (minutes) */
89 /** AtRateTimeToEmpty (minutes) */
95 /** Remaining Time Alarm (minutes) */
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv6264 int "Max lifetime for temporary address (in minutes)"
268 value. The value is in minutes. Default value is 1 day (24*60).
271 int "Max preferred lifetime for temporary address (in minutes)"
275 value. The value is in minutes. Default value is 23 hours (23*60).
DKconfig.tcp58 suggests to use MSL of 2 minutes, but notes "This is an
100 retransmit for up to 1:42 minutes. This is as close as possible
101 to the minimum value recommended by RFC1122 (1:40 minutes).
/Zephyr-latest/include/zephyr/drivers/rtc/
Dmcp7940n.h177 /* TRIGGER_ALL matches seconds, minutes, hours, weekday, date and month */
185 * minutes, hours, day of the week, day of the month, month and year.
Dmaxim_ds3231.h147 /** @brief Control alarm behavior on match in minutes field.
149 * If clear the alarm fires only when the RTC minutes matches the
150 * alarm minutes. The bit for IGNSE must be clear.
152 * If set the alarm minutes field is ignored and alarms will be
267 * component hours, minutes, seconds, day-of-week, and
306 * match on minutes and seconds must also be enabled. Failure
/Zephyr-latest/tests/bluetooth/adv/src/
Dmain.c16 #define TIMEOUT_MS 300000 /* 5 minutes */
/Zephyr-latest/include/zephyr/drivers/misc/ft8xx/
Dft8xx_copro.h54 /** Co-processor clock widget is drawn without hour and minutes hands,
62 /** Co-processor clock widget is drawn without hour, minutes and seconds hands */
/Zephyr-latest/.github/workflows/
Dtwister-publish.yaml42 run_date=`date --iso-8601=minutes`
/Zephyr-latest/subsys/bluetooth/services/
Dcts.c89 * year, month, day, hours, minutes and seconds. in bt_cts_time_from_unix_ms()
95 ct_time->min = date_time.tm_min; /* minutes */ in bt_cts_time_from_unix_ms()
/Zephyr-latest/include/zephyr/logging/
Dlog_output_custom.h48 * printer(log_instance, "%02u:%02u", hours, minutes);
/Zephyr-latest/include/zephyr/drivers/sensor/
Dscd4x.h43 * Operate the SCD4x in the operation mode for at least 3 minutes in an environment with a
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/
Dtrain_magic_wand_model.ipynb60 …Change runtime type** and selecting **GPU**. Training will take around 5 minutes on a GPU runtime."
193 …lowing cell will begin the training process. Training will take around 5 minutes on a GPU runtime.…
/Zephyr-latest/doc/connectivity/networking/
Dnet_config_guide.rst162 suggests to use MSL of 2 minutes, but notes
185 retransmit for up to 1:42 minutes. This is as close as possible
187 `RFC 1122 <https://www.rfc-editor.org/rfc/rfc1122>`_ (1:40 minutes).

123