Home
last modified time | relevance | path

Searched refs:seconds (Results 1 – 200 of 297) sorted by relevance

12

/linux-4.4.14/Documentation/watchdog/
Dwatchdog-parameters.txt22 timeout: Watchdog timeout in seconds. 1<= timeout <=63, default=60.
27 timeout: Watchdog timeout in seconds. (0 < timeout < 18000, default=60
32 timeout: Watchdog timeout in seconds. (1<=timeout<=3600, default=30
39 margin: Watchdog margin in seconds (default=60)
44 timeout: Timeout value. Limited to be 1 or 2 seconds. (default=2)
49 wdt_time: Watchdog time in seconds. (default=5)
54 heartbeat: Watchdog heartbeats in seconds. (default = 15)
59 wdt_time: Watchdog time in seconds. (default=30)
64 timeout: Watchdog timeout in seconds. (1<=timeout<=((2^32)/SCLK), default=20)
69 margin: Watchdog margin in seconds (default 60s)
[all …]
Dwatchdog-api.txt90 representing the timeout in seconds. The driver returns the real
96 printf("The timeout was set to %d seconds\n", timeout);
98 This example might actually print "The timeout was set to 60 seconds"
105 printf("The timeout was is %d seconds\n", timeout);
118 Note that the pretimeout is the number of seconds before the time
119 when the timeout will go off. It is not the number of seconds until
120 the pretimeout. So, for instance, if you set the timeout to 60 seconds
121 and the pretimeout to 10 seconds, the pretimeout will go off in 50
122 seconds. Setting a pretimeout to zero disables it.
127 printf("The pretimeout was is %d seconds\n", timeout);
[all …]
Dwdt.txt28 heartbeat Watchdog heartbeat in seconds (default 60)
Dwatchdog-kernel-api.txt75 * timeout: the watchdog timer's timeout value (in seconds).
76 * min_timeout: the watchdog timer's minimum timeout value (in seconds).
77 * max_timeout: the watchdog timer's maximum timeout value (in seconds).
Dhpwdt.txt46 NMIs in a matter of seconds. If a user sees the Linux kernel's "dazed and
/linux-4.4.14/drivers/rtc/
Drtc-tps6586x.c74 unsigned long seconds; in tps6586x_rtc_read_time() local
90 seconds = ticks >> 10; in tps6586x_rtc_read_time()
91 seconds += rtc->epoch_start; in tps6586x_rtc_read_time()
92 rtc_time_to_tm(seconds, tm); in tps6586x_rtc_read_time()
101 unsigned long seconds; in tps6586x_rtc_set_time() local
105 rtc_tm_to_time(tm, &seconds); in tps6586x_rtc_set_time()
106 if (seconds < rtc->epoch_start) { in tps6586x_rtc_set_time()
110 seconds -= rtc->epoch_start; in tps6586x_rtc_set_time()
112 ticks = (unsigned long long)seconds << 10; in tps6586x_rtc_set_time()
160 unsigned long seconds; in tps6586x_rtc_set_alarm() local
[all …]
Drtc-mc13xxx.c65 unsigned int seconds, days1, days2; in mc13xxx_rtc_read_time() local
77 ret = mc13xxx_reg_read(priv->mc13xxx, MC13XXX_RTCTOD, &seconds); in mc13xxx_rtc_read_time()
86 rtc_time64_to_tm((time64_t)days1 * SEC_PER_DAY + seconds, tm); in mc13xxx_rtc_read_time()
94 unsigned int seconds, days; in mc13xxx_rtc_set_mmss() local
98 days = div_s64_rem(secs, SEC_PER_DAY, &seconds); in mc13xxx_rtc_set_mmss()
129 ret = mc13xxx_reg_write(priv->mc13xxx, MC13XXX_RTCTOD, seconds); in mc13xxx_rtc_set_mmss()
160 unsigned seconds, days; in mc13xxx_rtc_read_alarm() local
167 ret = mc13xxx_reg_read(priv->mc13xxx, MC13XXX_RTCTODA, &seconds); in mc13xxx_rtc_read_alarm()
170 if (seconds >= SEC_PER_DAY) { in mc13xxx_rtc_read_alarm()
191 s1970 = (time64_t)days * SEC_PER_DAY + seconds; in mc13xxx_rtc_read_alarm()
[all …]
Drtc-bq32k.c39 uint8_t seconds; member
96 tm->tm_sec = bcd2bin(regs.seconds & BQ32K_SECONDS_MASK); in bq32k_rtc_read_time()
112 regs.seconds = bin2bcd(tm->tm_sec); in bq32k_rtc_set_time()
Drtc-ds1685.c255 u8 seconds, minutes, hours, wday, mday, month, years; in ds1685_rtc_read_time() local
259 seconds = rtc->read(rtc, RTC_SECS); in ds1685_rtc_read_time()
275 tm->tm_sec = ds1685_rtc_bcd2bin(rtc, seconds, RTC_SECS_BCD_MASK, in ds1685_rtc_read_time()
304 u8 ctrlb, seconds, minutes, hours, wday, mday, month, years, century; in ds1685_rtc_set_time() local
307 seconds = ds1685_rtc_bin2bcd(rtc, tm->tm_sec, RTC_SECS_BIN_MASK, in ds1685_rtc_set_time()
351 rtc->write(rtc, RTC_SECS, seconds); in ds1685_rtc_set_time()
381 u8 seconds, minutes, hours, mday, ctrlb, ctrlc; in ds1685_rtc_read_alarm() local
385 seconds = rtc->read(rtc, RTC_SECS_ALARM); in ds1685_rtc_read_alarm()
404 if (unlikely(seconds >= 0xc0)) in ds1685_rtc_read_alarm()
407 alrm->time.tm_sec = ds1685_rtc_bcd2bin(rtc, seconds, in ds1685_rtc_read_alarm()
[all …]
/linux-4.4.14/Documentation/networking/
Dnf_conntrack-sysctl.txt35 nf_conntrack_events_retry_timeout - INTEGER (seconds)
70 nf_conntrack_frag6_timeout - INTEGER (seconds)
75 nf_conntrack_generic_timeout - INTEGER (seconds)
87 nf_conntrack_icmp_timeout - INTEGER (seconds)
92 nf_conntrack_icmpv6_timeout - INTEGER (seconds)
134 nf_conntrack_tcp_timeout_close - INTEGER (seconds)
137 nf_conntrack_tcp_timeout_close_wait - INTEGER (seconds)
140 nf_conntrack_tcp_timeout_established - INTEGER (seconds)
143 nf_conntrack_tcp_timeout_fin_wait - INTEGER (seconds)
146 nf_conntrack_tcp_timeout_last_ack - INTEGER (seconds)
[all …]
Dxfrm_sysctl.txt4 default 30 - hard timeout in seconds for acquire requests
Dgeneric-hdlc.txt73 interval - time in seconds between keepalive packets
74 timeout - time in seconds after last received keepalive packet before
85 t391 - link integrity verification polling timer (in seconds) - user
86 t392 - polling verification timer (in seconds) - network
Dip-sysctl.txt79 purging entries. Entries older than 5 seconds will be cleared
107 Time, in seconds, that cached PMTU information is kept.
128 Time in seconds to keep an IP fragment in memory.
165 Measured in seconds.
171 Measured in seconds.
291 Default: 60 seconds
392 inflations such as transient congestion. The unit is seconds.
479 seconds and is a lower bound for the effective timeout.
483 RFC 1122 recommends at least 100 seconds for the timeout,
530 is 5, which corresponds to 31seconds till the last retransmission
[all …]
Dvortex.txt225 The default value is 5000 (5.0 seconds).
313 the external LAN environment if link is up and 5 seconds if link is down.
316 will be quite dreadful for up to sixty seconds. Be patient.
Ddm9000.txt137 necessary interrupt support in the chip or every two seconds via a
Deql.txt368 bits/sec seconds
391 #lines speed mtu seconds theory actual %of
Dz8530drv.txt515 packets, in seconds. This can be useful on busy CSMA
535 2 mode, in seconds. When no frames have been sent for this
543 This is the maximum time (in seconds) to wait for a free channel
Drxrpc.txt908 The maximum amount of time in seconds that a call may be in progress
913 The amount of time in seconds before we remove a dead call from the call
919 The amount of time in seconds after a connection was last used before we
926 The amount of time in seconds after a transport was last used before we
/linux-4.4.14/drivers/staging/lustre/include/linux/libcfs/linux/
Dlinux-time.h71 static inline long cfs_time_seconds(int seconds) in cfs_time_seconds() argument
73 return ((long)seconds) * HZ; in cfs_time_seconds()
88 static inline __u64 cfs_time_shift_64(int seconds) in cfs_time_shift_64() argument
91 cfs_time_seconds(seconds)); in cfs_time_shift_64()
/linux-4.4.14/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run.sh129 seconds=$(($minutes * 60))
163 boot_args="`per_version_boot_params "$boot_args" $builddir/.config $seconds`"
182 if test $kruntime -ge $seconds
189 if test $kruntime -lt $seconds
191 echo Completed in $kruntime vs. $seconds >> $resdir/Warnings 2>&1
219 echo "!!! PID $qemu_pid hung at $kruntime vs. $seconds seconds" >> $resdir/Warnings 2>&1
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dti,palmas-pwrbutton.txt17 - ti,palmas-long-press-seconds: Duration in seconds which the power
21 - ti,palmas-pwron-debounce-milli-seconds: Duration in milliseconds
33 ti,palmas-long-press-seconds = <12>;
34 ti,palmas-pwron-debounce-milli-seconds = <15>;
/linux-4.4.14/arch/s390/mm/
Dcmm.c237 static void cmm_set_timeout(long nr, long seconds) in cmm_set_timeout() argument
240 cmm_timeout_seconds = seconds; in cmm_set_timeout()
300 long nr, seconds; in cmm_timeout_handler() local
317 seconds = simple_strtoul(p, &p, 0); in cmm_timeout_handler()
318 cmm_set_timeout(nr, seconds); in cmm_timeout_handler()
365 long nr, seconds; in cmm_smsg_target() local
391 seconds = simple_strtoul(msg, &msg, 0); in cmm_smsg_target()
394 cmm_set_timeout(nr, seconds); in cmm_smsg_target()
/linux-4.4.14/Documentation/device-mapper/
Ddm-flakey.txt9 <up interval> seconds, then exhibits unreliable behaviour for <down
10 interval> seconds, and then this cycle repeats.
25 <up interval>: Number of seconds device is available.
26 <down interval>: Number of seconds device returns errors.
/linux-4.4.14/tools/laptop/freefall/
Dfreefall.c81 static void protect(int seconds) in protect() argument
83 const char *str = (seconds == 0) ? "Unparked" : "Parked"; in protect()
85 write_int(unload_heads_path, seconds*1000); in protect()
/linux-4.4.14/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-4.4.14/drivers/staging/lustre/include/linux/libcfs/
Dlibcfs_time.h66 static inline unsigned long cfs_time_shift(int seconds) in cfs_time_shift() argument
68 return cfs_time_add(cfs_time_current(), cfs_time_seconds(seconds)); in cfs_time_shift()
/linux-4.4.14/include/linux/
Ddelay.h50 static inline void ssleep(unsigned int seconds) in ssleep() argument
52 msleep(seconds * 1000); in ssleep()
Dtime.h149 extern unsigned int alarm_setitimer(unsigned int seconds);
Dcpu.h289 bool cpu_wait_death(unsigned int cpu, int seconds);
/linux-4.4.14/include/uapi/linux/netfilter/
Dxt_recent.h27 __u32 seconds; member
36 __u32 seconds; member
/linux-4.4.14/tools/testing/selftests/timers/
Dinconsistency-check.c105 int consistency_test(int clock_type, unsigned long seconds) in consistency_test() argument
120 while (seconds == -1 || now - then < seconds) { in consistency_test()
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Dqcom-wdt.txt15 - timeout-sec : shall contain the default watchdog timeout in seconds,
16 if unset, the default timeout is 30 seconds
Datmel-wdt.txt12 - timeout-sec: contains the watchdog timeout in seconds.
15 seconds. This value should be less or equal to 16. It is used to
18 seconds. This value must be smaller than the max-heartbeat-sec value.
Dbrcm,bcm2835-pm-wdog.txt10 - timeout-sec : Contains the watchdog timeout in seconds
Dpnx4008-wdt.txt9 - timeout-sec: contains the watchdog timeout in seconds.
Domap-wdt.txt8 - timeout-sec : default watchdog timeout in seconds
Dstericsson-coh901327.txt10 - timeout-sec: contains the watchdog timeout in seconds.
Dcadence-wdt.txt13 - timeout-sec : Watchdog timeout value (in seconds).
Ddavinci-wdt.txt8 - timeout-sec : Contains the watchdog timeout in seconds
Ddigicolor-wdt.txt16 - timeout-sec : Contains the watchdog timeout in seconds
Dsamsung-wdt.txt23 - timeout-sec : contains the watchdog timeout in seconds.
Dmarvel.txt35 - timeout-sec : Contains the watchdog timeout in seconds
Dst_lpc_wdt.txt27 - timeout-sec : Watchdog timeout in seconds
Datmel-sama5d4-wdt.txt8 - timeout-sec: watchdog timeout value (in seconds).
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-class-rtc-rtc0-device-rtc_calibration7 Every 60 seconds the AB8500 will correct the RTC's value
10 30.5 micro-seconds (half-parts-per-million of the 32KHz clock)
Dsysfs-ptp101 the form of three integers: channel index, seconds,
111 seconds, start time nanoseconds, period seconds, and
113 all the seconds and nanoseconds values to zero.
Dsysfs-driver-toshiba_haps19 seconds and then restore normal operation. Accepting 1 as the
Dsysfs-platform-dell-laptop52 The timeouts are expressed in seconds, minutes, hours and
58 is assumed to be expressed in seconds.
Dsysfs-class-powercap109 Time window in micro seconds. This is used along with
135 Maximum allowed time window in micro seconds for this
143 Minimum allowed time window in micro seconds for this
Dsysfs-fs-nilfs271 Show last write time of super block in seconds.
84 (in seconds).
154 Show write time of the last segment in seconds.
168 operation in seconds.
Dsysfs-platform-msi-laptop50 and there is a few seconds cooldown between subsequent toggles.
Dsysfs-driver-hid-roccat-kone85 around 6 seconds to complete and activates the TCU.
Dsysfs-power59 seconds, unfreeze tasks and enable nonboot CPUs. If it is in
62 memory, suspend devices, wait for 5 seconds, resume devices,
Dsysfs-block-bcache85 after this delay, expressed as an integer number of seconds.
Dsysfs-devices-edac15 Description: This attribute file displays how many seconds have elapsed
/linux-4.4.14/Documentation/locking/
Dlocktorture.txt68 shutdown_secs The number of seconds to run the test before terminating
73 onoff_interval The number of seconds between each attempt to execute a
80 onoff_holdoff The number of seconds to wait until starting CPU-hotplug
88 stat_interval Number of seconds between statistics-related printk()s.
89 By default, locktorture will report stats every 60 seconds.
100 shuffle_interval The number of seconds to keep the test threads affinitied
101 to a particular subset of the CPUs, defaults to 3 seconds.
/linux-4.4.14/kernel/time/
Ditimer.c253 unsigned int alarm_setitimer(unsigned int seconds) in alarm_setitimer() argument
258 if (seconds > INT_MAX) in alarm_setitimer()
259 seconds = INT_MAX; in alarm_setitimer()
261 it_new.it_value.tv_sec = seconds; in alarm_setitimer()
Dtimekeeping.c532 u64 seconds; in tk_update_ktime_data() local
542 seconds = (u64)(tk->xtime_sec + tk->wall_to_monotonic.tv_sec); in tk_update_ktime_data()
544 tk->tkr_mono.base = ns_to_ktime(seconds * NSEC_PER_SEC + nsec); in tk_update_ktime_data()
556 seconds++; in tk_update_ktime_data()
557 tk->ktime_sec = seconds; in tk_update_ktime_data()
832 time64_t seconds; in ktime_get_real_seconds() local
840 seconds = tk->xtime_sec; in ktime_get_real_seconds()
844 return seconds; in ktime_get_real_seconds()
Dtimer.c1455 SYSCALL_DEFINE1(alarm, unsigned int, seconds) in SYSCALL_DEFINE1() argument
1457 return alarm_setitimer(seconds); in SYSCALL_DEFINE1()
/linux-4.4.14/Documentation/filesystems/
Docfs2.txt55 of seconds has passed since the last update.
68 every 'nrsec' seconds. The default value is 5 seconds.
70 as much as the latest 5 seconds of work (your
75 it at the default (5 seconds).
Dbtrfs.txt75 commit=<seconds>
76 Set the interval of periodic commit, 30 seconds by default. Higher
79 but a warning is printed if it's more than 300 seconds (5 minutes).
Dceph.txt104 Specify the timeout value for mount (in seconds), in the case
106 seconds.
Dnilfs2.txt7 destroyed just a few seconds ago. Since NILFS2 can keep consistency
11 NILFS2 creates a number of checkpoints every few seconds or per
Dext4.txt174 every 'nrsec' seconds. The default value is 5 seconds.
176 as much as the latest 5 seconds of work (your
181 it at the default (5 seconds).
/linux-4.4.14/Documentation/RCU/
Dtorture.txt42 fqs_stutter Wait time (in seconds) between consecutive bursts
85 The number of seconds between each attempt to execute a
92 onoff_holdoff The number of seconds to wait until starting CPU-hotplug
100 The number of seconds to keep the test threads affinitied
101 to a particular subset of the CPUs, defaults to 3 seconds.
104 shutdown_secs The number of seconds to run the test before terminating
109 stall_cpu The number of seconds that a CPU should be stalled while
124 The number of seconds to wait after rcutorture starts
125 before stalling a CPU. Defaults to 10 seconds.
127 stat_interval The number of seconds between output of torture
[all …]
Dstallwarn.txt15 21 seconds.
20 So if you are 10 seconds into a 40-second stall, setting this
33 RCU_STALL_DELAY_DELTA macro allows five extra seconds before
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-transport-srp12 Description: Number of seconds the SCSI layer will wait after a transport
21 Description: Number of seconds the SCSI layer will wait after a transport
37 Description: Number of seconds the SCSI layer will wait after a reconnect
Dsysfs-devices-system-xen_memory17 increased to. The default value is 32 seconds.
35 The time (in seconds) to wait between attempts to
Dsysfs-bus-usb20 power/autosuspend. This file holds the time (in seconds)
/linux-4.4.14/fs/nilfs2/
DKconfig8 destroyed just a few seconds ago. Since this file system can keep
12 NILFS2 creates a number of checkpoints every few seconds or per
/linux-4.4.14/tools/perf/Documentation/
Dexamples.txt42 0.613972165 seconds time elapsed
63 0.643954516 seconds time elapsed ( +- 2.363% )
158 seconds:
171 10.000591410 seconds time elapsed
187 1.058135029 seconds time elapsed ( +- 3.089% )
Dperf-top.txt34 -d <seconds>::
35 --delay=<seconds>::
36 Number of seconds to delay between refreshes.
Dperf-timechart.txt106 Written 10.2 seconds of trace to output.svg.
Dperf-kvm.txt120 Time in seconds between display updates
/linux-4.4.14/Documentation/
Dlockup-watchdogs.txt9 kernel mode for more than 20 seconds (see "Implementation" below for
19 kernel mode for more than 10 seconds (see "Implementation" below for
43 same name) seconds to check for hardlockups. If any CPU in the system
51 for 2*watchdog_thresh seconds (the softlockup threshold) the
Drtc.txt12 The newest non-PC hardware tends to just count seconds, like the time(2)
152 since_epoch: The number of seconds since the epoch according to the RTC
156 after wake if a daily wakeup is required. Format is seconds since
157 the epoch by default, or if there's a leading +, seconds in the
158 future, or if there is a leading +=, seconds ahead of the current
Dbtmrvl.txt23 where Gap is the gap in milli seconds between wakeup signal and
DIPMI.txt296 seconds, it will generate a response automatically saying the command
298 seconds, for instance), that response will be ignored.
595 The timeout is the number of seconds to the action, and the pretimeout
596 is the amount of seconds before the reset that the pre-timeout panic will
599 timeout is 50 seconds and the pretimeout is 10 seconds, then the pretimeout
600 will occur in 40 second (10 seconds before the timeout). The panic_wdt_timeout
714 the system off, then power it on in a few seconds). Setting
Drpmsg.txt73 or a timeout of 15 seconds elapses. When the latter happens,
90 or a timeout of 15 seconds elapses. When the latter happens,
108 or a timeout of 15 seconds elapses. When the latter happens,
Dstatic-keys.txt269 1.601607384 seconds time elapsed ( +- 0.07% )
286 1.579384366 seconds time elapsed
Dkernel-parameters.txt552 Values larger than 10 seconds (10000) are changed to
745 seconds. Defaults to 10*60 = 10mins. A value of 0
1715 optional and is the number seconds in between
1919 specifying five seconds causes the test to run for
1920 five seconds, wait for five seconds, and so on.
2093 memory_corruption_check_period=seconds [X86]
2095 seconds. Use this parameter to check at some
2333 in seconds between layoutstats transmissions.
2365 [NET] Specifies amount of time (in seconds) that
2367 waits 4 seconds.
[all …]
Dsysrq.txt53 You send a BREAK, then within 5 seconds a command key. Sending
194 exit 'showkey' by not typing anything for ten seconds.
Dmd.txt253 period as a number of seconds. The default is 200msec (0.200).
314 The time, in seconds, between looking for bits in the bitmap to
571 sync_action. It is averaged over the last 30 seconds.
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dstmmac.txt17 The 1st cell is reset pre-delay in micro seconds.
18 The 2nd cell is reset pulse in micro seconds.
19 The 3rd cell is reset post-delay in micro seconds.
/linux-4.4.14/include/uapi/scsi/
Dscsi_netlink_fc.h60 uint64_t seconds; member
/linux-4.4.14/sound/drivers/
Dpcm-indirect2.c47 int seconds = (rec->lastbytetime - rec->firstbytetime) / HZ; in snd_pcm_indirect2_stat() local
62 seconds, rec->bytes2hw / seconds, in snd_pcm_indirect2_stat()
63 rec->bytes2hw / 2 / 2 / seconds); in snd_pcm_indirect2_stat()
DKconfig196 seconds of idle time the driver must count before it may
205 In this case, the time-out is set to 10 seconds; setting
208 the device frequently. A value of 10 seconds would be a
218 The default time-out value in seconds for AC97 automatic
Dmts64.c155 u8 seconds, u8 frames,
369 u8 seconds, u8 frames, in mts64_smpte_start() argument
380 mts64_write_command(p, seconds); in mts64_smpte_start()
/linux-4.4.14/Documentation/sound/alsa/
Dpowersave.txt16 the time-out value in seconds. 0 means to disable the automatic
26 automatic power-save mode with 10 seconds, write to
/linux-4.4.14/Documentation/ptp/
Dtestptp.c181 int seconds = 0; in main() local
246 seconds = atoi(optarg); in main()
341 ts.tv_sec = seconds; in main()
/linux-4.4.14/drivers/ptp/
Dptp_clock.c58 s64 seconds; in enqueue_external_timestamp() local
61 seconds = div_u64_rem(src->timestamp, 1000000000, &remainder); in enqueue_external_timestamp()
67 dst->t.sec = seconds; in enqueue_external_timestamp()
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Dinfo.txt16 Default is 5 seconds.
27 Default is 5 seconds.
53 Default is 5 seconds.
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt68 call. The following is an example that reports every 5 seconds what processes
105 10.002577764 seconds time elapsed
132 0.973913387 seconds time elapsed
163 0.982653002 seconds time elapsed ( +- 1.448% )
181 1.002251757 seconds time elapsed ( +- 0.005% )
267 This was interrupted after a few seconds and
Dmmiotrace.txt143 Timestamp is in seconds with decimals. Physical is a PCI bus address, virtual
/linux-4.4.14/drivers/scsi/qla4xxx/
Dql4_nvram.c207 unsigned int seconds = 30; in ql4xxx_sem_spinlock() local
223 } while (--seconds); in ql4xxx_sem_spinlock()
/linux-4.4.14/Documentation/devicetree/bindings/rtc/
Dxlnx-rtc.txt4 Separate IRQ lines for seconds and alarm
Dnvidia,tegra20-rtc.txt3 The Tegra RTC maintains seconds and milliseconds counters, and five alarm
/linux-4.4.14/Documentation/hwmon/
Dlm8059 than 2.0 seconds since the last update). This means that you can easily
62 The LM80 only updates its values each 1.5 seconds; reading it more often
Dgl518sm69 (unless it is less than 1.5 seconds since the last update). This means that
72 The GL518SM only updates its values each 1.5 seconds; reading it more often
Dlm8754 than 1.0 seconds since the last update). This means that you can easily
57 The lm87 driver only updates its values each 1.0 seconds; reading it more
Dlm7864 than 1.5 seconds since the last update). This means that you can easily
67 The LM7* only updates its values each 1.5 seconds; reading it more often
Dvia686a62 than 1.5 seconds since the last update). This means that you can easily
65 The driver only updates its values each 1.5 seconds; reading it more often
Dsis559596 seconds since the last update). This means that you can easily miss
99 The SiS5595 only updates its values each 1.5 seconds; reading it more often
Dpc87360166 data is read (unless it is less than 2 seconds since the last update, in
168 a once-only alarm triggers, it may take 2 seconds for it to show, and 2
169 more seconds for it to disappear.
Dadm102671 seconds since the last update). This means that you can easily miss
76 divisor. It can take as long as 1.5 seconds to measure all fan speeds.
Dlm9387 intervals are (in seconds):
123 four signals are measured within 4 seconds.
224 the spin-up time in seconds. The available spin-up times are constrained by
236 one value each in seconds: pwm_auto_prochot_ramp and pwm_auto_vrdhot_ramp.
Dsmsc47m157 than 1.5 seconds since the last update). This means that you can easily
Dthmc5043 The THMC50 only updates its values each 1.5 seconds; reading it more often
Dadt747037 registers more often than once every 5 seconds. Further, configuration data is
Dg76239 of the programmed value for over 6 seconds 'fan1_alarm' is
Dlm6370 (attributes pwm1_auto_*) have their own independent lifetime of 5 seconds.
Dsmsc47m19248 The temperature and voltage readings are updated once every 1.5 seconds.
Dadm102185 This driver only updates its values each 1.5 seconds; reading it more often
Dit87206 seconds since the last update). This means that you can easily miss
213 The IT87xx only updates its values each 1.5 seconds; reading it more often
Dabituguru-datasheet227 Bit 7: Volt sensor: Shutdown if alarm persist for more than 4 seconds (RW)
296 Bit 7: Shutdown if alarm persist for more than 4 seconds (RW)
Dadm924058 each two seconds. User-space may read sysfs interface faster than the
Dw83791d111 The driver reads the hardware chip values at most once every three seconds.
Dw83792d103 The chips only update values each 3 seconds; reading them more often will
Dw83781d148 than 1.5 seconds since the last update). This means that you can easily
151 The chips only update values each 1.5 seconds; reading them more often
/linux-4.4.14/drivers/scsi/csiostor/
Dcsio_attr.c323 uint64_t seconds; in csio_get_stats() local
352 seconds = jiffies_to_msecs(jiffies) - hw->stats.n_reset_start; in csio_get_stats()
353 do_div(seconds, 1000); in csio_get_stats()
354 fhs->seconds_since_last_reset = seconds; in csio_get_stats()
/linux-4.4.14/Documentation/usb/
Dchipidea.txt41 5) Remove B-device(unplug micro B plug) and insert again in 10 seconds,
44 6) Remove B-device(unplug micro B plug) and insert again after 10 seconds,
Dpower-management.txt140 older file uses seconds. Confusingly, both files are present in 2.6.37
199 The default autosuspend idle-delay time (in seconds) is controlled by
201 is loaded. For example, to set it to 5 seconds instead of 2 you would
263 also change the idle-delay time; 2 seconds is not the best choice for
505 suspends don't take long (a few seconds usually), but it can happen.
/linux-4.4.14/drivers/scsi/aic7xxx/
DKconfig.aic79xx37 int "Initial bus reset delay in milli-seconds"
45 Default: 5000 (5 seconds)
DKconfig.aic7xxx42 int "Initial bus reset delay in milli-seconds"
50 Default: 5000 (5 seconds)
/linux-4.4.14/Documentation/devicetree/bindings/lpddr2/
Dlpddr2-timings.txt12 of type <u32> and the default unit is ps (pico seconds). Parameters with
/linux-4.4.14/Documentation/filesystems/nfs/
Didmapper.txt34 The last parameter, 600, defines how many seconds into the future the key will
36 is not specified, nfs.idmap will default to 600 seconds.
Dnfs.txt95 units of seconds).
/linux-4.4.14/drivers/watchdog/
Dnv_tco.c72 static inline unsigned char seconds_to_ticks(int seconds) in seconds_to_ticks() argument
76 return (seconds * 10) / 6; in seconds_to_ticks()
/linux-4.4.14/Documentation/aoe/
Daoe.txt37 however, because AoE discovery takes a few seconds. It can be
126 seconds that the driver will wait for an AoE device to provide a
127 response to an AoE command. After aoe_deadsecs seconds have
/linux-4.4.14/Documentation/power/powercap/
Dpowercap.txt204 constraint_X_time_window_us (rw): Time window in micro seconds.
212 constraint_X_max_time_window_us(ro): Maximum allowed time window in micro seconds.
214 constraint_X_min_time_window_us(ro): Minimum allowed time window in micro seconds.
/linux-4.4.14/drivers/platform/x86/
Ddell-laptop.c1242 u8 seconds; member
1317 info->seconds = (buffer->output[3] >> 0) & 0xFF; in kbd_get_info()
1533 if (kbd_info.seconds > 63) in kbd_init_info()
1534 kbd_info.seconds = 63; in kbd_init_info()
1641 if (value > kbd_info.seconds) in kbd_led_timeout_store()
1688 if (value <= kbd_info.seconds && kbd_info.seconds) { in kbd_led_timeout_store()
/linux-4.4.14/Documentation/power/
Dinterface.txt30 tasks, wait for 5 seconds, unfreeze tasks and enable nonboot CPUs. If it is
33 for 5 seconds, resume devices, unfreeze tasks and enable nonboot CPUs. Then,
Dpower_supply_class.txt51 µA, µAh, µWh, seconds and tenths of degree Celsius unless otherwise
156 TIME_TO_EMPTY - seconds left for battery to be considered empty (i.e.
158 TIME_TO_FULL - seconds left for battery to be considered full (i.e.
Ds2ram.txt83 quickly after the resume failure. The trace option does not use the seconds
Dbasic-pm-debugging.txt79 seconds (5 by default, but configurable by the suspend.pm_test_delay module
84 configurable number of seconds and invoke the platform (eg. ACPI) global
/linux-4.4.14/include/trace/events/
Dv4l2.h135 __entry->timecode_seconds = buf->timecode.seconds;
212 __entry->timecode_seconds = vbuf->timecode.seconds;
/linux-4.4.14/kernel/
Dsmpboot.c462 bool cpu_wait_death(unsigned int cpu, int seconds) in cpu_wait_death() argument
464 int jf_left = seconds * HZ; in cpu_wait_death()
/linux-4.4.14/net/netfilter/
Dxt_recent.c296 unsigned long time = jiffies - info->seconds * HZ; in recent_mt()
300 if (info->seconds && time_after(time, e->stamps[i])) in recent_mt()
357 (info->seconds || info->hit_count || in recent_mt_check()
360 if ((info->check_set & XT_RECENT_REAP) && !info->seconds) in recent_mt_check()
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2005.txt16 the configured time (in milli seconds), the driver
/linux-4.4.14/Documentation/fmc/
Dfmc-write-eeprom.txt60 after two seconds. Please note, however, that if fmc-write-eeprom is
62 will be reprogrammed and thus will be unloaded after two seconds. The
/linux-4.4.14/drivers/staging/lustre/
Dsysfs-fs-lustre53 Unit: seconds, default: 100
97 Controls minimum adaptive timeout in seconds. If you encounter
108 Controls maximum adaptive timeout in seconds. If at_max timeout
121 in processing in seconds. Normally a server-side parameter, it
135 seconds..
142 Controls for how many seconds to remember slowest events
416 values (in seconds).
569 Number of seconds with no write activity for this target
/linux-4.4.14/Documentation/laptops/
Ddisk-shock-protection.txt49 set to 30 seconds. However, you can always change a timeout to any
52 total timeout can exceed 30 seconds and, more importantly, you can
62 /dev/sda and stop all I/O operations for five seconds:
Dtoshiba_haps.txt38 RSSS - Shuts down the HDD protection interface for a few seconds,
Dlaptop-mode.txt88 is triggered. A sensible value for the knob is 5 seconds. Setting the knob to
123 Maximum time, in seconds, of hard drive spindown time that you are
136 20 seconds (value 4) for BATT_HD and 2 hours (value 244) for AC_HD. The
200 of his regular 3 to 3.5 hours) using a spindown time of 5 seconds (BATT_HD=1).
237 # Maximum time, in seconds, of hard drive spindown time that you are
301 # Default is 2 hours on AC (AC_HD=244) and 20 seconds for battery (BATT_HD=4).
352 # Maximum time, in seconds, of hard drive spindown time that you are
/linux-4.4.14/Documentation/input/
Datarikbd.txt438 RX ; length of time (in tenths of seconds) until
440 RY ; length of time (in tenths of seconds) until
442 TX ; length (in tenths of seconds) of joystick closure
445 TY ; length (in tenths of seconds) of joystick closure
448 VX ; length (in tenths of seconds) of joystick closure
451 VY ; length (in tenths of seconds) of joystick closure
457 tenths of seconds later, keystroke pairs are generated every Tn tenths of
458 seconds. After the Rn breakpoint is reached, keystroke pairs are generated
459 every Vn tenths of seconds. This provides a velocity (auto-repeat) breakpoint
Dyealink.txt190 Example - sound the ringtone for 10 seconds:
Diforce-protocol.txt246 few seconds latency. Personally, I restart it every time I play an effect.
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt138 - delay is retime delay in pico seconds as mentioned in data sheet.
148 as non inverted clock retimed with CLK_B and delay of 0 pico seconds:
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dfsl-upm-nand.txt56 chip-delay = <25>; // in micro-seconds
/linux-4.4.14/Documentation/scsi/
DChangeLog.megaraid_sas370 1. Increased MFI_POLL_TIMEOUT_SECS to 60 seconds from 10. FW may take
371 a max of 60 seconds to respond to the INIT cmd.
404 issue. 2. Increased MFI_POLL_TIMEOUT_SECS to 60 seconds from
405 10. FW may take a max of 60 seconds to respond to the INIT
436 call completion routine every 5 seconds from the reset routine instead of
480 The driver now waits for 10 seconds to elapse instead of 5 (as in
496 resumed if pending cmd count reduces to 16 or 5 seconds has elapsed
Dncr53c8xx.txt381 "ms" means milli-seconds)
409 Example above: 4.94 seconds
413 Example above: 369.94 seconds spent for data transfer
417 Example above: 183.09 seconds spent disconnected
422 Example above: 1.32 seconds spent for post processing
457 10 means 25 nano-seconds synchronous period
458 11 means 30 nano-seconds synchronous period
459 12 means 50 nano-seconds synchronous period
874 settle time 10 seconds settle:10
996 logic state, 100 micro-seconds after having asserted the SCSI RESET line.
[all …]
Dsym53c8xx_2.txt318 9 means 12.5 nano-seconds synchronous period
319 10 means 25 nano-seconds synchronous period
320 11 means 30 nano-seconds synchronous period
321 12 means 50 nano-seconds synchronous period
521 settle=n delay for n seconds
523 After a bus reset, the driver will delay for n seconds before talking
524 to any device on the bus. The default is 3 seconds and safe mode will
563 logic state, 100 micro-seconds after having asserted the SCSI RESET line.
565 Since SCSI devices shall release the BUS at most 800 nano-seconds after SCSI
Dscsi-changer.txt127 timeout_init=<seconds>
131 timeout_move=<seconds>
Ddc395x.txt84 The seconds to not accept commands after a SCSI Reset
Dst.txt107 seconds, open fails with the errno value EIO. With O_NONBLOCK the
486 Set the normal timeout in seconds for this device. The
487 default is 900 seconds (15 minutes). The timeout should be
492 known to take a long time. The default is 14000 seconds
DBusLogic.txt478 BusSettleTime:<seconds>
481 seconds. The Bus Settle Time is the amount of time to wait between a Host
521 second host adapter to 30 seconds.
/linux-4.4.14/drivers/scsi/
D3w-9xxx.c144 static int twa_poll_response(TW_Device_Extension *tw_dev, int request_id, int seconds);
145 static int twa_poll_status_gone(TW_Device_Extension *tw_dev, u32 flag, int seconds);
1417 static int twa_poll_response(TW_Device_Extension *tw_dev, int request_id, int seconds) in twa_poll_response() argument
1423 if (twa_poll_status_gone(tw_dev, TW_STATUS_RESPONSE_QUEUE_EMPTY, seconds) == 0) { in twa_poll_response()
1454 static int twa_poll_status(TW_Device_Extension *tw_dev, u32 flag, int seconds) in twa_poll_status() argument
1472 if (time_after(jiffies, before + HZ * seconds)) in twa_poll_status()
1483 static int twa_poll_status_gone(TW_Device_Extension *tw_dev, u32 flag, int seconds) in twa_poll_status_gone() argument
1500 if (time_after(jiffies, before + HZ * seconds)) in twa_poll_status_gone()
DBusLogic.h1209 static inline void blogic_delay(int seconds) in blogic_delay() argument
1211 mdelay(1000 * seconds); in blogic_delay()
D3w-sas.c525 static int twl_poll_response(TW_Device_Extension *tw_dev, int request_id, int seconds) in twl_poll_response() argument
549 if (time_after(jiffies, before + HZ * seconds)) in twl_poll_response()
1242 …c int twl_poll_register(TW_Device_Extension *tw_dev, void *reg, u32 value, u32 result, int seconds) in twl_poll_register() argument
1253 if (time_after(jiffies, before + HZ * seconds)) in twl_poll_register()
D3w-xxxx.c300 static int tw_poll_status(TW_Device_Extension *tw_dev, u32 flag, int seconds) in tw_poll_status() argument
318 if (time_after(jiffies, before + HZ * seconds)) in tw_poll_status()
329 static int tw_poll_status_gone(TW_Device_Extension *tw_dev, u32 flag, int seconds) in tw_poll_status_gone() argument
347 if (time_after(jiffies, before + HZ * seconds)) in tw_poll_status_gone()
/linux-4.4.14/net/ceph/
Dmon_client.c250 unsigned int seconds; in handle_subscribe_ack() local
255 seconds = le32_to_cpu(h->duration); in handle_subscribe_ack()
264 dout("handle_subscribe_ack after %d seconds\n", seconds); in handle_subscribe_ack()
265 monc->sub_renew_after = monc->sub_sent + (seconds >> 1)*HZ - 1; in handle_subscribe_ack()
/linux-4.4.14/drivers/rapidio/
DKconfig7 int "Discovery timeout duration (seconds)"
/linux-4.4.14/Documentation/blockdev/
DREADME.DAC960287 driver queries each controller for status information every 10 seconds, and
288 checks for additional conditions every 60 seconds. The initial status of each
295 logged to the system console at most every 60 seconds.
452 the driver within 10 seconds of the controller's having detected it, and the
505 Within 10 seconds of this command the driver logs the initiation of the
530 updated every 10 seconds:
624 the driver within 10 seconds of the controller's having detected it, and the
665 updated every 10 seconds:
736 the console by the driver. Within 60 seconds of this command the driver logs:
/linux-4.4.14/Documentation/dvb/
Dfaq.txt3 1. The signal seems to die a few seconds after tuning.
9 allow you to change the timeout (default 5 seconds). Setting the
/linux-4.4.14/drivers/staging/dgnc/
Ddgnc_driver.h127 int (*drain)(struct tty_struct *tty, uint seconds);
Ddgnc_cls.c42 static int cls_drain(struct tty_struct *tty, uint seconds);
898 static int cls_drain(struct tty_struct *tty, uint seconds) in cls_drain() argument
Ddgnc_neo.c44 static int neo_drain(struct tty_struct *tty, uint seconds);
1284 static int neo_drain(struct tty_struct *tty, uint seconds) in neo_drain() argument
/linux-4.4.14/drivers/net/ethernet/qlogic/qlcnic/
Dqlcnic_83xx_init.c160 int seconds; in qlcnic_83xx_idc_update_audit_reg() local
171 seconds = jiffies / HZ - adapter->ahw->idc.sec_counter; in qlcnic_83xx_idc_update_audit_reg()
173 seconds = jiffies / HZ; in qlcnic_83xx_idc_update_audit_reg()
175 val |= seconds << 8; in qlcnic_83xx_idc_update_audit_reg()
309 u64 seconds; in qlcnic_83xx_idc_check_timeout() local
311 seconds = jiffies / HZ - adapter->ahw->idc.sec_counter; in qlcnic_83xx_idc_check_timeout()
312 if (seconds <= time_limit) in qlcnic_83xx_idc_check_timeout()
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-floppy.1996-200213 * Ver 0.8 Dec 7 97 Increase irq timeout from 10 to 50 seconds.
/linux-4.4.14/lib/
DKconfig.debug372 send a BREAK and then within 5 seconds a command keypress. The
698 mode for more than 20 seconds, without giving other tasks a
703 for more than 10 seconds, without letting other interrupts have a
708 generate interrupts and kick the watchdog task every 4 seconds.
709 An NMI is generated every 10 seconds or so to check for hardlockups.
725 mode with interrupts disabled for more than 10 seconds (configurable
743 mode for more than 20 seconds (configurable using the watchdog_thresh
777 int "Default timeout for hung task detection (in seconds)"
781 This option controls the default timeout (in seconds) used
840 Set the timeout value (in seconds) until a reboot occurs when the
[all …]
/linux-4.4.14/Documentation/x86/x86_64/
Dmachinecheck38 How often to poll for corrected machine check errors, in seconds
/linux-4.4.14/Documentation/fb/
Dep93xx-fb.txt24 Note that the pixel clock value is in pico-seconds. You can use the
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt121 S3C2410, this can take approximately 4 seconds to complete.
/linux-4.4.14/Documentation/ia64/
Derr_inject.txt49 #On cpu2, inject only total 0x10 errors, interval 5 seconds
54 #On cpu4, inject and consume total 0x10 errors, interval 5 seconds
59 #On cpu15, inject and consume total 0x10 errors, interval 5 seconds
110 #define MIN_INTERVAL 5 // seconds
Defirtc.txt84 Mon Mar 6 15:32:32 2000 -0.910248 seconds
Dserial.txt106 Long pause (60+ seconds) between "Uncompressing Linux... done" and
/linux-4.4.14/kernel/trace/
DKconfig578 a producer and consumer that will run for 10 seconds and sleep for
579 10 seconds. Each interval it will print out the number of events
600 The test runs for 10 seconds. This will slow your boot time
601 by at least 10 more seconds.
/linux-4.4.14/Documentation/firmware_class/
DREADME90 seconds for the whole load operation.
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt103 seconds). Default:
107 valid for 30 seconds.
548 The value in this file represents the number of seconds the kernel
683 default we allow one every 5 seconds.
692 seconds, we do allow a burst of messages to pass through.
963 is 10 seconds.
Dfs.txt62 int age_limit; /* age in seconds */
72 Age_limit is the age in seconds after which dcache entries
/linux-4.4.14/Documentation/ioctl/
Dcdrom.txt141 MSF stands for minutes-seconds-frames
145 is described as minutes:seconds:frames. A frame is 1/75 of
209 MSF stands for minutes-seconds-frames
Dbotching-up-ioctls.txt138 * Use __s64 seconds plus __u64 nanoseconds to specify time. It's not the most
142 that the kernel native struct ktime has a signed integer for both seconds
/linux-4.4.14/kernel/power/
DKconfig177 make it wake up a few seconds later using an RTC wakeup alarm.
198 int "Watchdog timeout in seconds"
/linux-4.4.14/Documentation/w1/
Dw1.generic94 w1_master_timeout - (ro) the delay in seconds between searches
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dsynopsys-dw-mshc.txt67 * card-detect-delay: Delay in milli-seconds before detecting card after card
/linux-4.4.14/Documentation/isdn/
DREADME169 The DELAY must at least be 1.5 seconds long and delay
170 between the escape characters must not exceed 0.5 seconds.
183 6 3 Delay in seconds before dialing.
466 "isdnctrl cbdelay <InterfaceName> [seconds]"
DREADME.sc200 vi) the hangup timeout can be set to a specified number of seconds
251 vi) the hangup timeout can be set to a specified number of seconds
DREADME.diversion119 specify during a certain amount of time (normally 4 to 10 seconds) what
/linux-4.4.14/drivers/net/wireless/ath/ath9k/
DKconfig141 seconds. Turn off to save power, but enable it if you have
/linux-4.4.14/sound/pci/asihpi/
Dhpi_internal.h956 u16 seconds; member
964 u16 seconds; member
/linux-4.4.14/Documentation/cpu-freq/
Duser-guide.txt156 seconds. If unknown or known to be
/linux-4.4.14/scripts/
Dkernel-doc298 (my $seconds = `date -d"${ENV{'KBUILD_BUILD_TIMESTAMP'}}" +%s`) ne '') {
299 @build_time = gmtime($seconds);
/linux-4.4.14/arch/arm/plat-samsung/
DKconfig266 Note, this can take several seconds depending on memory size
/linux-4.4.14/Documentation/video4linux/bttv/
DInsmod-options144 every few seconds, but only once after
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt94 line high for two seconds), followed by setting up the device
178 for ethernet cards, and so on. This handler then sleeps for 5 seconds,
/linux-4.4.14/arch/powerpc/boot/dts/
Dtqm8548-bigflash.dts425 chip-delay = <25>; // in micro-seconds
Dtqm8548.dts425 chip-delay = <25>; // in micro-seconds
/linux-4.4.14/sound/pci/hda/
DKconfig219 The default time-out value in seconds for HD-audio automatic
/linux-4.4.14/arch/arm/boot/dts/
Darmada-xp-synology-ds414.dts185 * connected a few seconds after pressing the
/linux-4.4.14/Documentation/pps/
Dpps.txt151 Where before the "#" is the timestamp in seconds; after it is the

12