Searched refs:elapse (Results 1 – 17 of 17) sorted by relevance
/linux-6.12.1/drivers/usb/chipidea/ |
D | otg.c | 156 unsigned long elapse = jiffies + msecs_to_jiffies(5000); in hw_wait_vbus_lower_bsv() local 160 if (time_after(jiffies, elapse)) { in hw_wait_vbus_lower_bsv()
|
/linux-6.12.1/Documentation/RCU/ |
D | rcu.rst | 9 A "grace period" must elapse between the two parts, and this grace period 13 a grace period to elapse, then free the element. See listRCU.rst for more
|
D | rcubarrier.rst | 9 a grace period to elapse. This primitive takes a pointer to an rcu_head 41 grace period to elapse, it does not wait for the callbacks to complete. 55 than waiting for a grace period to elapse, rcu_barrier() waits for all
|
D | UP.rst | 45 RCU usage, since call_rcu() must wait for a grace period to elapse.
|
D | listRCU.rst | 65 grace periods elapse, with the help of call_rcu(), which is invoked via
|
D | checklist.rst | 297 those waiting for a grace period to elapse. Enforce a
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-class-chromeos-driver-cros-ec-lightbar | 21 that must elapse between accessing any of the lightbar
|
/linux-6.12.1/sound/soc/sof/ |
D | Kconfig | 195 elapse to inform ALSA about that, on platforms (e.g. Intel SKL+) that 196 with other approach (e.g. HDAC DPIB/posbuf) to elapse PCM.
|
/linux-6.12.1/Documentation/hwmon/ |
D | w83627ehf.rst | 188 how many milliseconds [ms] must elapse to switch
|
D | nct6775.rst | 227 how many milliseconds must elapse to switch
|
/linux-6.12.1/Documentation/RCU/Design/Requirements/ |
D | Requirements.rst | 1282 without forcing the updater to wait for a grace period to elapse. The 1359 | elapse? | 1909 | elapse. So even if there are quite a few callbacks posted, | 2221 waiting for a grace period to elapse. It is also the reason why 2497 period to elapse. For example, this results in a self-deadlock:
|
/linux-6.12.1/Documentation/scsi/ |
D | ChangeLog.megaraid_sas | 480 The driver now waits for 10 seconds to elapse instead of 5 (as in
|
/linux-6.12.1/tools/memory-model/Documentation/ |
D | litmus-tests.txt | 870 waits for an RCU grace period to elapse, and finally line 32 emulates
|
/linux-6.12.1/Documentation/RCU/Design/Data-Structures/ |
D | Data-Structures.rst | 125 while they are waiting for a grace period to elapse, as shown in the
|
/linux-6.12.1/Documentation/networking/ |
D | ip-sysctl.rst | 3072 is the largest time interval that can elapse between retransmissions. 3078 is the smallest time interval the can elapse between retransmissions.
|
/linux-6.12.1/Documentation/admin-guide/ |
D | cgroup-v2.rst | 2163 duration of time between evaluation events. Windows only elapse
|
D | kernel-parameters.txt | 6460 Specifies how many nanoseconds must elapse
|