| /linux-4.4.14/drivers/macintosh/ |
| D | via-pmu-backlight.c | 20 static int sleeping, uses_pmu_bl; variable
106 if (!sleeping) in pmu_backlight_update_status()
124 sleeping = sleep; in pmu_backlight_set_sleep()
|
| D | mediabay.c | 69 int sleeping; member
549 if (!media_bays[i].sleeping) in media_bay_task()
591 bay->sleeping = 0; in media_bay_attach()
626 bay->sleeping = 1; in media_bay_suspend()
664 bay->sleeping = 0; in media_bay_resume()
|
| /linux-4.4.14/Documentation/accounting/ |
| D | cgroupstats.txt | 25 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0
27 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
|
| /linux-4.4.14/drivers/media/dvb-frontends/ |
| D | rtl2830_priv.h | 34 bool sleeping; member
|
| D | rtl2830.c | 141 dev->sleeping = false; in rtl2830_init()
154 dev->sleeping = true; in rtl2830_sleep()
290 if (dev->sleeping) in rtl2830_get_frontend()
404 if (dev->sleeping) in rtl2830_read_status()
853 dev->sleeping = true; in rtl2830_probe()
|
| D | rtl2832.c | 409 dev->sleeping = false; in rtl2832_init()
425 dev->sleeping = true; in rtl2832_sleep()
586 if (dev->sleeping) in rtl2832_get_frontend()
701 if (dev->sleeping) in rtl2832_read_status()
1237 dev->sleeping = true; in rtl2832_probe()
|
| D | rtl2832_priv.h | 46 bool sleeping; member
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | kgdb.xml.db | 6 API-sleeping-thread-to-gdb-regs
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-arch.txt | 60 sleeping idle functions.
70 sh64 - Is sleeping racy vs interrupts? (See #4a)
|
| /linux-4.4.14/Documentation/locking/ |
| D | mutex-design.txt | 12 or similar theoretical text books. Mutexes are sleeping locks which
68 for sleeping lock implementation. An important feature of the customized
82 task and busy-waiting for a few cycles instead of immediately sleeping,
|
| D | lglock.txt | 134 does not change the tasks state while sleeping [6].
|
| D | rt-mutex-design.txt | 39 Now there's no way of knowing how long A will be sleeping waiting for C
|
| /linux-4.4.14/Documentation/usb/ |
| D | dwc3.txt | 32 sleeping is handed over to the Thread. The event is saved in an
|
| /linux-4.4.14/drivers/net/ethernet/apple/ |
| D | bmac.c | 82 int sleeping; member
474 bp->sleeping = 1; in bmac_suspend()
980 if (bp->sleeping) in bmac_set_multicast()
1213 bp->sleeping = 0; in bmac_reset_and_enable()
1402 bp->sleeping = 1; in bmac_close()
1449 if (bp->sleeping) in bmac_start()
|
| /linux-4.4.14/drivers/net/ethernet/chelsio/cxgb3/ |
| D | sge.c | 2186 unsigned int sleeping) in check_ring_db() argument
2188 if (sleeping & F_RSPD_TXQ0_GTS) { in check_ring_db()
2199 if (sleeping & F_RSPD_TXQ1_GTS) { in check_ring_db()
2261 unsigned int sleeping = 0; in process_responses() local
2343 sleeping |= flags & RSPD_GTS_MASK; in process_responses()
2385 if (sleeping) in process_responses()
2386 check_ring_db(adap, qs, sleeping); in process_responses()
2466 unsigned int sleeping = 0; in process_pure_responses() local
2480 sleeping |= flags & RSPD_GTS_MASK; in process_pure_responses()
2494 if (sleeping) in process_pure_responses()
[all …]
|
| /linux-4.4.14/arch/arm/mach-pxa/ |
| D | sleep.S | 65 @ Intel PXA270 Specification Update notes problems sleeping
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | hypercalls.txt | 81 same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall,
|
| /linux-4.4.14/Documentation/networking/ |
| D | netdevices.txt | 103 all NAPI instances which will do a sleeping poll on the
|
| D | rxrpc.txt | 296 If recvmsg is called in blocking mode, it will keep sleeping, awaiting the
300 data in the buffer rather than sleeping until it can fill the buffer.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | mca.txt | 172 sleeping. To get a backtrace, just start with thread.ksp for the
173 original task and unwind like any other sleeping task.
|
| /linux-4.4.14/drivers/net/wireless/ath/ath9k/ |
| D | channel.c | 1554 if (an->sleeping == !!avp->noa.absent) in ath9k_p2p_ps_timer()
1557 an->sleeping = avp->noa.absent; in ath9k_p2p_ps_timer()
1558 if (an->sleeping) in ath9k_p2p_ps_timer()
|
| D | xmit.c | 549 if (txok || !an->sleeping) in ath_tx_complete_aggr()
628 if (an->sleeping) in ath_tx_complete_aggr()
632 if (!an->sleeping) { in ath_tx_complete_aggr()
2350 if (!txctl->an->sleeping) in ath_tx_start()
|
| D | ath9k.h | 261 bool sleeping; member
|
| D | main.c | 1600 an->sleeping = true; in ath9k_sta_notify()
1606 an->sleeping = false; in ath9k_sta_notify()
|
| /linux-4.4.14/drivers/scsi/ |
| D | mesh.c | 112 sleeping enumerator
1767 if (ms->phase == sleeping) in mesh_suspend()
1777 ms->phase = sleeping; in mesh_suspend()
1790 if (ms->phase != sleeping) in mesh_resume()
|
| /linux-4.4.14/Documentation/trace/ |
| D | uprobetracer.txt | 140 Lets disable the event after sleeping for some time.
|
| D | mmiotrace.txt | 58 The 'cat' process should stay running (sleeping) in the background.
|
| /linux-4.4.14/drivers/net/wireless/ath/carl9170/ |
| D | carl9170.h | 486 bool sleeping; member
|
| D | main.c | 1735 sta_info->sleeping = true; in carl9170_op_sta_notify()
1741 sta_info->sleeping = false; in carl9170_op_sta_notify()
|
| D | tx.c | 1297 if (unlikely(sta_info->sleeping) && in carl9170_tx_ps_drop()
|
| /linux-4.4.14/Documentation/vm/ |
| D | balance | 71 and all process contexts are sleeping. For 2.3, kswapd does not really
|
| D | page_migration | 123 to sleeping on the locked new page.
|
| /linux-4.4.14/Documentation/ |
| D | flexible-arrays.txt | 62 running in some sort of atomic context; in this situation, sleeping in the
|
| D | IPMI.txt | 465 microseconds, that kipmid will spin before sleeping for a tick. This
|
| D | kernel-parameters.txt | 3016 Param: "sleep" - profile D-state sleeping (millisecs).
|
| /linux-4.4.14/Documentation/laptops/ |
| D | sonypi.txt | 126 Fn-keys which put the laptop in sleeping state, or switch the
|
| /linux-4.4.14/Documentation/gpio/ |
| D | consumer.txt | 191 Also, using these calls for GPIOs that can't safely be accessed without sleeping
200 sleeping, which can't be done from inside IRQ handlers.
|
| D | gpio-legacy.txt | 184 without sleeping (see below) is an error.
200 This requires sleeping, which can't be done from inside IRQ handlers.
585 cost as little as two or three instructions, never sleeping. When such an
|
| D | driver.txt | 141 other GPIO irqchip residing on the other side of a sleeping bus. Of course
|
| /linux-4.4.14/Documentation/arm/pxa/ |
| D | mfp.txt | 65 wakeup from GPIO(s) any more, depending on the sleeping state, ADxER
|
| /linux-4.4.14/drivers/net/wireless/brcm80211/brcmfmac/ |
| D | sdio.c | 518 bool sleeping; member
1023 (bus->sleeping ? "SLEEP" : "WAKE")); in brcmf_sdio_bus_sleep()
1028 if (sleep == bus->sleeping) in brcmf_sdio_bus_sleep()
1062 bus->sleeping = sleep; in brcmf_sdio_bus_sleep()
|
| /linux-4.4.14/Documentation/thermal/ |
| D | intel_powerclamp.txt | 288 Tasks: 197 total, 1 running, 196 sleeping, 0 stopped, 0 zombie
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 140 sleeping on I/O. This means that single-threaded and 1-per-CPU-threaded
|
| /linux-4.4.14/drivers/gpio/ |
| D | Kconfig | 68 before they are used, and that sleeping calls are not made from
69 non-sleeping contexts. They can make bitbanged serial protocols
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 518 be able to reserve the space without sleeping. For a 8MB checkpoint, we need a
639 really needs to be a sleeping lock - if the CIL flush takes the lock, we do not
644 main reason for choosing a sleeping lock even though nothing in either the
|
| D | proc.txt | 214 State state (R is running, S is sleeping, D is sleeping
283 state state (R is running, S is sleeping, D is sleeping in an
|
| D | path-lookup.txt | 284 When we reach a point where sleeping is required, or a filesystem callout
|
| D | ext4.txt | 291 commit time, ext4 will try sleeping for the
|
| D | coda.txt | 301 sleeping.
1640 +o Close will notify any sleeping processes that their upcall cannot
|
| /linux-4.4.14/Documentation/RCU/ |
| D | checklist.txt | 378 is what makes sleeping read-side critical sections tolerable --
|
| /linux-4.4.14/Documentation/power/ |
| D | pci.txt | 204 sleeping, they should cause the system's core logic to trigger wakeup.
222 A GPE may be triggered when the system is sleeping (i.e. when it is in one of
|
| D | devices.txt | 653 refreshed using DMA while most of the system is sleeping lightly ... and
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 1803 wait_usecs - How long to wait without sleeping, usecs
1816 sleep_tries - How many times to try sleeping during a wait
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 90 11.2 Examining sleeping processes
2501 11.2. Examining sleeping processes
2510 What you want is the stack of whatever process is sleeping when it
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ChangeLog.1992-1997 | 1246 the task state before sleeping.
|
| /linux-4.4.14/init/ |
| D | Kconfig | 518 permits arbitrary sleeping or blocking within RCU read-side critical
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 1991 State: S (sleeping)
|