Searched refs:elapse (Results 1 – 17 of 17) sorted by relevance
| /openbmc/linux/drivers/usb/chipidea/ |
| H A 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()
|
| /openbmc/linux/Documentation/RCU/ |
| H A 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
|
| H A 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
|
| H A D | UP.rst | 45 RCU usage, since call_rcu() must wait for a grace period to elapse.
|
| H A D | listRCU.rst | 56 grace periods elapse, with the help of call_rcu(), which is invoked via
|
| H A D | checklist.rst | 290 those waiting for a grace period to elapse. Enforce a
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-chromeos-driver-cros-ec-lightbar | 21 that must elapse between accessing any of the lightbar
|
| /openbmc/linux/sound/soc/sof/ |
| H A D | Kconfig | 184 elapse to inform ALSA about that, on platforms (e.g. Intel SKL+) that
185 with other approach (e.g. HDAC DPIB/posbuf) to elapse PCM.
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | w83627ehf.rst | 188 how many milliseconds [ms] must elapse to switch
|
| H A D | nct6775.rst | 227 how many milliseconds must elapse to switch
|
| /openbmc/linux/Documentation/scsi/ |
| H A D | ChangeLog.megaraid_sas | 480 The driver now waits for 10 seconds to elapse instead of 5 (as in
|
| /openbmc/linux/Documentation/RCU/Design/Requirements/ |
| H A 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
2496 period to elapse. For example, this results in a self-deadlock:
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | litmus-tests.txt | 870 waits for an RCU grace period to elapse, and finally line 32 emulates
|
| /openbmc/linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 125 while they are waiting for a grace period to elapse, as shown in the
|
| /openbmc/linux/Documentation/networking/ |
| H A D | ip-sysctl.rst | 2984 is the largest time interval that can elapse between retransmissions.
2990 is the smallest time interval the can elapse between retransmissions.
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 2019 duration of time between evaluation events. Windows only elapse
|
| H A D | kernel-parameters.txt | 6182 Specifies how many nanoseconds must elapse
|