Home
last modified time | relevance | path

Searched full:seconds (Results 1 – 25 of 1681) sorted by relevance

12345678910>>...68

/linux-5.10/Documentation/networking/
Dnf_conntrack-sysctl.rst60 nf_conntrack_frag6_timeout - INTEGER (seconds)
65 nf_conntrack_generic_timeout - INTEGER (seconds)
80 nf_conntrack_icmp_timeout - INTEGER (seconds)
85 nf_conntrack_icmpv6_timeout - INTEGER (seconds)
127 nf_conntrack_tcp_timeout_close - INTEGER (seconds)
130 nf_conntrack_tcp_timeout_close_wait - INTEGER (seconds)
133 nf_conntrack_tcp_timeout_established - INTEGER (seconds)
136 nf_conntrack_tcp_timeout_fin_wait - INTEGER (seconds)
139 nf_conntrack_tcp_timeout_last_ack - INTEGER (seconds)
142 nf_conntrack_tcp_timeout_max_retrans - INTEGER (seconds)
[all …]
/linux-5.10/Documentation/watchdog/
Dwatchdog-parameters.rst18 Maximum time, in seconds, for which the watchdog framework will take
44 Watchdog timeout in seconds. 1<= timeout <=63, default=60.
53 Watchdog timeout in seconds. (0 < timeout < 18000, default=60
62 Watchdog timeout in seconds. (1<=timeout<=3600, default=30
74 Watchdog margin in seconds (default=60)
83 Watchdog timeout in seconds. (default=120)
92 Watchdog time in seconds. (default=5)
101 Watchdog heartbeats in seconds. (default = 15)
110 Watchdog time in seconds. (default=30)
119 Watchdog margin in seconds (default 60s)
[all …]
Dwatchdog-api.rst98 representing the timeout in seconds. The driver returns the real
104 printf("The timeout was set to %d seconds\n", timeout);
106 This example might actually print "The timeout was set to 60 seconds"
113 printf("The timeout was is %d seconds\n", timeout);
127 Note that the pretimeout is the number of seconds before the time
128 when the timeout will go off. It is not the number of seconds until
129 the pretimeout. So, for instance, if you set the timeout to 60 seconds
130 and the pretimeout to 10 seconds, the pretimeout will go off in 50
131 seconds. Setting a pretimeout to zero disables it.
136 printf("The pretimeout was is %d seconds\n", timeout);
[all …]
Dhpwdt.rst30 Default value is 30 seconds.
33 This is the number of seconds before timeout when an
36 Default value is 9 seconds.
42 kdumptimeout Minimum timeout in seconds to apply upon receipt of an NMI
54 can only be set to 9 seconds. Attempts to set pretimeout to other
/linux-5.10/include/linux/
Dtimekeeper_internal.h21 * @xtime_nsec: Shifted (fractional) nano seconds offset for readout
49 * @xtime_sec: Current CLOCK_REALTIME time in seconds
50 * @ktime_sec: Current CLOCK_MONOTONIC time in seconds
55 * @tai_offset: The current UTC to TAI offset in seconds
59 * @raw_sec: CLOCK_MONOTONIC_RAW time in seconds
62 * @xtime_interval: Number of clock shifted nano seconds in one NTP
64 * @xtime_remainder: Shifted nano seconds left over when rounding
66 * @raw_interval: Shifted raw nano seconds accumulated per NTP interval.
68 * shifted nano seconds.
69 * @ntp_error_shift: Shift conversion between clock shifted nano seconds and
[all …]
Dwatchdog.h32 * @set_timeout:The routine for setting the watchdog devices timeout value (in seconds).
34 * @get_timeleft:The routine that gets the time left before a reset (in seconds).
68 * @timeout: The watchdog devices timeout value (in seconds).
70 * @min_timeout:The watchdog devices minimum timeout value (in seconds).
71 * @max_timeout:The watchdog devices maximum timeout value (in seconds)
76 * in milli-seconds.
78 * Hardware limit for maximum timeout, in milli-seconds.
165 * (since internal calculations are done in milli-seconds), in watchdog_timeout_invalid()
/linux-5.10/drivers/rtc/
Drtc-mc13xxx.c63 unsigned int seconds, days1, days2; in mc13xxx_rtc_read_time() local
75 ret = mc13xxx_reg_read(priv->mc13xxx, MC13XXX_RTCTOD, &seconds); in mc13xxx_rtc_read_time()
84 rtc_time64_to_tm((time64_t)days1 * SEC_PER_DAY + seconds, tm); in mc13xxx_rtc_read_time()
92 unsigned int seconds, days; in mc13xxx_rtc_set_time() local
96 days = div_s64_rem(rtc_tm_to_time64(tm), SEC_PER_DAY, &seconds); in mc13xxx_rtc_set_time()
116 * write seconds=0 to prevent a day switch between writing days in mc13xxx_rtc_set_time()
117 * and seconds below in mc13xxx_rtc_set_time()
127 ret = mc13xxx_reg_write(priv->mc13xxx, MC13XXX_RTCTOD, seconds); in mc13xxx_rtc_set_time()
158 unsigned int seconds, days; in mc13xxx_rtc_read_alarm() local
165 ret = mc13xxx_reg_read(priv->mc13xxx, MC13XXX_RTCTODA, &seconds); in mc13xxx_rtc_read_alarm()
[all …]
Drtc-tps6586x.c73 time64_t seconds; in tps6586x_rtc_read_time() local
89 seconds = ticks >> 10; in tps6586x_rtc_read_time()
90 rtc_time64_to_tm(seconds, tm); in tps6586x_rtc_read_time()
99 time64_t seconds; in tps6586x_rtc_set_time() local
103 seconds = rtc_tm_to_time64(tm); in tps6586x_rtc_set_time()
105 ticks = (unsigned long long)seconds << 10; in tps6586x_rtc_set_time()
152 time64_t seconds; in tps6586x_rtc_set_alarm() local
161 seconds = rtc_tm_to_time64(&alrm->time); in tps6586x_rtc_set_alarm()
182 if ((seconds - rtc_current_time) > ALM1_VALID_RANGE_IN_SEC) in tps6586x_rtc_set_alarm()
183 seconds = rtc_current_time - 1; in tps6586x_rtc_set_alarm()
[all …]
Dclass.c38 /* IMPORTANT: the RTC only stores whole seconds. It is arbitrary
40 * seconds truncated. However, it is important that we use it to store
283 * If the start_secs is larger than the maximum seconds (rtc->range_max) in rtc_device_get_offset()
284 * supported by RTC hardware or the maximum seconds of new expanded in rtc_device_get_offset()
286 * rtc->range_min, which means the minimum seconds (rtc->range_min) of in rtc_device_get_offset()
288 * the offset seconds calculation formula should be: in rtc_device_get_offset()
291 * If the start_secs is larger than the minimum seconds (rtc->range_min) in rtc_device_get_offset()
296 * seconds of RTC hardware (rtc->range_min) should be mapped to in rtc_device_get_offset()
297 * rtc->range_max + 1, then the offset seconds formula should be: in rtc_device_get_offset()
300 * If the start_secs is less than the minimum seconds (rtc->range_min), in rtc_device_get_offset()
[all …]
/linux-5.10/drivers/char/
Dhangcheck-timer.c17 * duration in seconds. The hangcheck_margin parameter defines the
18 * margin of error, in seconds. The defaults are 60 seconds for the
19 * timer and 180 seconds for the margin of error. IOW, a timer is set
20 * for 60 seconds. When the timer fires, the callback checks the
22 * allotted time and margin (here 60 + 180, or 240 seconds), the machine
43 #define DEFAULT_IOFENCE_MARGIN 60 /* Default fudge factor, in seconds */
44 #define DEFAULT_IOFENCE_TICK 180 /* Default timer timeout, in seconds */
55 …gin, "If the hangcheck timer has been delayed more than hangcheck_margin seconds, the driver will …
155 printk("Hangcheck: starting hangcheck timer %s (tick is %d seconds, margin is %d seconds).\n", in hangcheck_init()
/linux-5.10/tools/testing/selftests/firmware/
Dsettings2 # 2 seconds). There are 3 test configs, each done with and without firmware
4 # normal execution should be 2 * 3 * 2 * 2 * 5 = 120 seconds for those alone.
5 # Additionally, fw_fallback may take 5 seconds for internal timeouts in each
6 # of the 3 configs, so at least another 15 seconds are needed. Add another
7 # 10 seconds for each testing config: 120 + 15 + 30
/linux-5.10/Documentation/devicetree/bindings/input/
Dti,palmas-pwrbutton.txt16 - ti,palmas-long-press-seconds: Duration in seconds which the power
20 - ti,palmas-pwron-debounce-milli-seconds: Duration in milliseconds
32 ti,palmas-long-press-seconds = <12>;
33 ti,palmas-pwron-debounce-milli-seconds = <15>;
/linux-5.10/drivers/net/ethernet/microchip/
Dlan743x_ptp.c25 u32 seconds, u32 nano_seconds,
66 u32 seconds, u32 nano_seconds, in lan743x_ptp_tx_ts_enqueue_ts() argument
73 ptp->tx_ts_seconds_queue[ptp->tx_ts_queue_size] = seconds; in lan743x_ptp_tx_ts_enqueue_ts()
88 u32 header, nseconds, seconds; in lan743x_ptp_tx_ts_complete() local
106 seconds = ptp->tx_ts_seconds_queue[i]; in lan743x_ptp_tx_ts_complete()
110 tstamps.hwtstamp = ktime_set(seconds, nseconds); in lan743x_ptp_tx_ts_complete()
180 u32 *seconds, u32 *nano_seconds,
408 u32 seconds = 0; in lan743x_ptpci_gettime64() local
410 lan743x_ptp_clock_get(adapter, &seconds, &nano_seconds, NULL); in lan743x_ptpci_gettime64()
411 ts->tv_sec = seconds; in lan743x_ptpci_gettime64()
[all …]
/linux-5.10/tools/testing/selftests/watchdog/
Dwatchdog-test.c81 printf(" -p, --pingrate=P\tSet ping rate to P seconds (default %d)\n", in usage()
83 printf(" -t, --timeout=T\tSet timeout to T seconds\n"); in usage()
85 printf(" -n, --pretimeout=T\tSet the pretimeout to T seconds\n"); in usage()
172 printf("Watchdog ping rate set to %u seconds.\n", ping_rate); in main()
178 printf("Watchdog timeout set to %u seconds.\n", flags); in main()
188 printf("WDIOC_GETTIMEOUT returns %u seconds.\n", flags); in main()
196 printf("Watchdog pretimeout set to %u seconds.\n", flags); in main()
206 printf("WDIOC_GETPRETIMEOUT returns %u seconds.\n", flags); in main()
214 printf("WDIOC_GETTIMELEFT returns %u seconds.\n", flags); in main()
/linux-5.10/drivers/watchdog/
Dbd70528_wdt.c15 * Max time we can set is 1 hour, 59 minutes and 59 seconds
168 unsigned int seconds; in bd70528_wdt_set_timeout() local
172 seconds = timeout; in bd70528_wdt_set_timeout()
176 seconds -= (60 * 60); in bd70528_wdt_set_timeout()
177 minutes = seconds / 60; in bd70528_wdt_set_timeout()
178 seconds = seconds % 60; in bd70528_wdt_set_timeout()
199 BD70528_MASK_WDT_SEC, bin2bcd(seconds)); in bd70528_wdt_set_timeout()
201 dev_err(w->dev, "Failed to set WDT seconds\n"); in bd70528_wdt_set_timeout()
Debc-c384_wdt.c22 * watchdog timer; the maximum timeout possible is 15300 (255 * 60) seconds.
37 MODULE_PARM_DESC(timeout, "Watchdog timeout in seconds (default="
44 /* resolution is in minutes for timeouts greater than 255 seconds */ in ebc_c384_wdt_start()
62 /* resolution is in minutes for timeouts greater than 255 seconds */ in ebc_c384_wdt_set_timeout()
72 /* set watchdog timer for seconds */ in ebc_c384_wdt_set_timeout()
/linux-5.10/Documentation/devicetree/bindings/memory-controllers/
Darm,pl172.txt68 enable (WE signal) in nano seconds.
71 enable (OE signal) in nano seconds.
74 access in nano seconds.
77 access in nano seconds.
80 accesses in nano seconds.
83 seconds.
/linux-5.10/kernel/time/
Ditimer.c266 * alarm_setitimer - set alarm in seconds
268 * @seconds: number of seconds until alarm
271 * Returns the remaining time in seconds of a pending timer or 0 when
274 * On 32 bit machines the seconds value is limited to (INT_MAX/2) to avoid
277 static unsigned int alarm_setitimer(unsigned int seconds) in alarm_setitimer() argument
282 if (seconds > INT_MAX) in alarm_setitimer()
283 seconds = INT_MAX; in alarm_setitimer()
285 it_new.it_value.tv_sec = seconds; in alarm_setitimer()
306 SYSCALL_DEFINE1(alarm, unsigned int, seconds) in SYSCALL_DEFINE1() argument
308 return alarm_setitimer(seconds); in SYSCALL_DEFINE1()
/linux-5.10/Documentation/locking/
Dlocktorture.rst80 The number of seconds to run the test before terminating
86 The number of seconds between each attempt to execute a
94 The number of seconds to wait until starting CPU-hotplug
103 Number of seconds between statistics-related printk()s.
104 By default, locktorture will report stats every 60 seconds.
116 The number of seconds to keep the test threads affinitied
117 to a particular subset of the CPUs, defaults to 3 seconds.
/linux-5.10/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh10 # Usage: kvm-test-1-run.sh config builddir resdir seconds qemu-args boot_args
124 seconds=$4
155 boot_args="`per_version_boot_params "$boot_args" $resdir/.config $seconds`"
209 if test $kruntime -ge $seconds -o -f "$TORTURE_STOPFILE"
216 if test $kruntime -lt $seconds
218 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
269 if test "$newline" != "$oldline" -a "$last_ts" -lt $((seconds + $TORTURE_SHUTDOWN_GRACE))
273 if test $must_continue = no -a $kruntime -ge $((seconds + $TORTURE_SHUTDOWN_GRACE))
275 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-rtc51 Valid time range for the RTC, as seconds from epoch, formatted
59 (RO) RTC-provided time as the number of seconds since the epoch
88 wake if a daily wakeup is required. Format is seconds since the
89 epoch by default, or if there's a leading +, seconds in the
90 future, or if there is a leading +=, seconds ahead of the
Dsysfs-bus-iio-sps307 to its maximum speed and keeps spinning for about 10 seconds in
17 the current one is returned. Units are seconds.
26 The range of available values in seconds represented as the
/linux-5.10/fs/udf/
Dudftime.c32 * We don't take into account leap seconds. This may be correct or incorrect.
33 * For more NIST information (especially dealing with leap seconds), see:
75 time64_t seconds; in udf_time_to_disk_stamp() local
83 seconds = ts.tv_sec + offset * 60; in udf_time_to_disk_stamp()
84 time64_to_tm(seconds, 0, &tm); in udf_time_to_disk_stamp()
/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-flakey.rst10 <up interval> seconds, then exhibits unreliable behaviour for <down
11 interval> seconds, and then this cycle repeats.
33 Number of seconds device is available.
35 Number of seconds device returns errors.
/linux-5.10/include/net/netns/
Dsctp.h45 * RTO.Initial - 3 seconds
47 * RTO.Max - 60 seconds
70 /* Valid.Cookie.Life - 60 seconds */
76 /* HB.interval - 30 seconds */
162 /* Threshold for autoclose timeout, in seconds. */

12345678910>>...68