Home
last modified time | relevance | path

Searched refs:waits (Results 1 – 50 of 50) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dti,tas5086.txt17 waits for this period of time before starting the
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dbrcm,iproc-touchscreen.txt15 the tsc waits to allow the voltage to settle after
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-driver-hid-picolcd21 Description: Delay PicoLCD waits before restarting in new mode when
/linux-4.4.14/Documentation/RCU/
Drcubarrier.txt74 a grace period to elapse, rcu_barrier() waits for all outstanding RCU
174 RCU callbacks will be posted. The rcu_barrier() call on line 53 waits
201 callback queues, and then waits until they have all started executing, at
224 before on_each_cpu() returns. Line 9 then waits for the completion.
Dchecklist.txt375 A given synchronize_srcu() waits only for SRCU read-side critical
DRTFP.txt258 node was to be deleted, and waits until all such processes have
291 node was to be deleted, and waits until all such processes have
321 Describes lazy TLB flush, where one waits for each CPU to pass
DwhatisRCU.txt175 To reiterate, synchronize_rcu() waits only for ongoing RCU
/linux-4.4.14/Documentation/accounting/
Dtaskstats-struct.txt120 * from the kernel in involuntary waits due to virtualization.
128 * for kernel's involuntary waits due to virtualization.
/linux-4.4.14/drivers/rapidio/
DKconfig11 Amount of time a discovery node waits for a host to complete
/linux-4.4.14/Documentation/usb/
Danchors.txt63 This function waits for all URBs associated with an anchor to finish
DURB.txt164 It does everything usb_unlink_urb does, and in addition it waits
Dusbmon.txt306 Second, it waits for an event to be present in the buffer, unless the pseudo-
/linux-4.4.14/Documentation/networking/
Dcxacru.txt90 "restart" (stops, waits 1.5s, then starts)
/linux-4.4.14/Documentation/ide/
Dide-tape.txt8 to the request-list of the block device, and waits for their completion.
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/
Dgate.txt19 "ti,wait-gate-clock" - gate clock which waits until clock is active before
/linux-4.4.14/Documentation/virtual/kvm/devices/
Ds390_flic.txt48 Disables async page faults for the guest and waits until already pending
/linux-4.4.14/Documentation/dmaengine/
Ddmatest.txt48 /sys/module/dmatest/parameters/wait waits for any running test to complete
/linux-4.4.14/Documentation/mmc/
Dmmc-async-req.txt39 truly non-blocking. If there is an ongoing async request it waits
/linux-4.4.14/Documentation/devicetree/bindings/arm/msm/
Dqcom,idle-state.txt16 trigger to execute the SPM state machine. The SPM state machine waits for the
/linux-4.4.14/drivers/staging/rdma/hfi1/
Dsdma.c1416 struct iowait *waits[SDMA_WAIT_BATCH_SIZE]; in sdma_desc_avail() local
1442 if (n == ARRAY_SIZE(waits)) in sdma_desc_avail()
1455 waits[n++] = wait; in sdma_desc_avail()
1463 waits[i]->wakeup(waits[i], SDMA_AVAIL_REASON); in sdma_desc_avail()
/linux-4.4.14/Documentation/filesystems/caching/
Dobject.txt159 preparation states in which the object sets itself up and waits for its parent
248 can destroy themselves. This object waits for all its children to go away
Dnetfs-api.txt759 invalidates any backing objects and waits for cessation of activity on any
/linux-4.4.14/Documentation/
Dbcache.txt35 in the cache it first disables writeback caching and waits for all dirty data
262 any, waits some number of seconds before initiating writeback. Defaults to
361 Write to this file to shut down the cache set - waits until all attached
Dntb.txt44 Ping Pong enables the link when started, waits for the NTB link to come up, and
Dcpu-hotplug.txt381 architecture. __cpu_die() typically waits for some
DIPMI.txt525 message as a block write to the I2C bus and waits for a response.
Dmemory-barriers.txt2267 get the lock again; it instead just waits for its task pointer to be cleared
Dkernel-parameters.txt2367 waits 4 seconds.
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt158 already-completed events, successful waits and timed-out waits are all sane
/linux-4.4.14/sound/pci/
Dfm801.c1067 unsigned short reg, unsigned long waits) in wait_for_codec() argument
1069 unsigned long timeout = jiffies + waits; in wait_for_codec()
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt131 endpoint waits for enumeration to be completed. If the specified timeout
294 each agent waits for enumeration completion by the host for the configured wait
/linux-4.4.14/Documentation/filesystems/
Dautofs4-mount-control.txt303 and any remaining waits in the queue released.
351 request back to the daemon and waits for completion.
/linux-4.4.14/Documentation/scsi/
DChangeLog.megaraid_sas434 1. When MegaSAS driver receives reset call from OS, driver waits in reset
480 The driver now waits for 10 seconds to elapse instead of 5 (as in
Dtmscsim.txt325 * DelayReset is the time in seconds (minus 0.5s), the adapter waits, after a
Dst.txt105 drive is not ready. If O_NONBLOCK is not used, the driver waits for
/linux-4.4.14/Documentation/ia64/
Dmca.txt28 then it cannot service the MCA interrupt. SAL waits ~20 seconds then
/linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dgpc.fuc377 // Disables various things, waits a bit, and re-enables them..
Dhub.fuc423 // Disables various things, waits a bit, and re-enables them..
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt175 RTT for its presence. If the postmap free block is in the RTT, it waits till the
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt36 The older tasks waits until it can acquire the contended lock. The younger tasks
/linux-4.4.14/drivers/scsi/
Dst.c967 int attentions, waits, max_wait, scode; in test_ready() local
975 for (attentions=waits=0; ; ) { in test_ready()
1003 if (waits < max_wait) { in test_ready()
1008 waits++; in test_ready()
Dpmcraid.c3110 int waits = jiffies_to_msecs(PMCRAID_RESET_HOST_TIMEOUT) / interval; in pmcraid_eh_host_reset_handler() local
3119 while (waits--) { in pmcraid_eh_host_reset_handler()
/linux-4.4.14/Documentation/power/
Dfreezing-of-tasks.txt168 on another. For example, if kernel thread A waits for a completion (in the
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt435 The simple example assumes that the subsystem merely waits until all the
/linux-4.4.14/tools/perf/Documentation/
Dintel-pt.txt471 In full-trace mode, the driver waits for data to be copied out before allowing
/linux-4.4.14/Documentation/input/
Dsentelic.txt12 @4. Issuing the "Get device ID" command (0xF2) and waits for the response;
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt549 waits before rebooting on a panic. When you use the software watchdog,
/linux-4.4.14/Documentation/filesystems/cifs/
DREADME517 all dirty (cached) file data to the server and waits for the
/linux-4.4.14/Documentation/video4linux/
Dv4l2-framework.txt735 your driver also waits in the code, then you should do the same to allow other
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt1813 waits, only about 250 result in a sleep.