Searched full:busy (Results 1 – 25 of 105) sorted by relevance
12345
| /Documentation/devicetree/bindings/display/ |
| D | repaper.txt | 12 - busy-gpios: BUSY pin
49 busy-gpios = <&gpio 25 0>;
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 76 of idleness (idle, busy, and newly idle):
95 cpu was busy
97 load did not require balancing when busy
99 more tasks and failed, when the cpu was busy
101 load_balance() in this domain when the cpu was busy
102 13) # of times in this domain pull_task() was called when busy
104 target task was cache-hot when busy
106 find a busier queue while the cpu was busy
108 was busy but no busier group was found
|
| /Documentation/driver-api/nvdimm/ |
| D | firmware-activate.rst | 22 'armed', 'overflow', and 'busy'.
30 - busy:
31 In the busy state armed devices are in the process of transitioning
63 attribute indicates 'idle', 'armed', or 'busy'. The state transitions
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e17.rst | 52 DS28E17 devices. It is a multiplier used on the calculation of the busy
56 driver checks the DS28E17's busy flag in a loop after the precalculated
60 19-00000002dbd8: busy timeout" in the kernel log.
|
| /Documentation/locking/ |
| D | hwspinlock.rst | 93 msecs). If the hwspinlock is already taken, the function will busy loop
101 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
109 msecs). If the hwspinlock is already taken, the function will busy loop
116 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
125 msecs). If the hwspinlock is already taken, the function will busy loop
133 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
142 msecs). If the hwspinlock is already taken, the function will busy loop
150 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
159 msecs). If the hwspinlock is already taken, the function will busy loop
166 notably -ETIMEDOUT if the hwspinlock is still busy after timeout msecs).
|
| /Documentation/process/ |
| D | volatile-considered-harmful.rst | 62 when the processor is busy-waiting on the value of a variable. The right
63 way to perform a busy wait is::
70 barrier, so, once again, volatile is unnecessary. Of course, busy-
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-w1_ds28e17 | 19 the busy timeout for I2C operations on the connected DS28E17
|
| /Documentation/userspace-api/ioctl/ |
| D | hdio.rst | 187 - EBUSY Controller busy
237 - EBUSY Controller busy or blockmode already set.
361 - EBUSY Controller busy
1061 - EBUSY Controller busy
1091 - EBUSY Controller busy
1119 - EBUSY Controller busy
1147 - EBUSY Controller busy
1215 the interface is busy.
1243 - EBUSY Controller busy
1271 - EBUSY Controller busy
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 23 and will busy wait for enough loop cycles to achieve
45 -- Backed by busy-wait loop:
|
| /Documentation/devicetree/bindings/mtd/ |
| D | lpc32xx-mlc.txt | 34 nxp,busy-delay = <10000000>;
|
| D | allwinner,sun4i-a10-nand.yaml | 77 Contains the native Ready/Busy IDs.
|
| D | nand-controller.yaml | 146 Contains the native Ready/Busy IDs.
152 Ready/Busy pins. Active state refers to the NAND ready state and
|
| D | fsl-upm-nand.txt | 12 - gpios : may specify optional GPIOs connected to the Ready-Not-Busy pins
|
| /Documentation/hwmon/ |
| D | shtc1.rst | 55 the I2C bus will be busy during that time. By default, non-blocking mode
|
| /Documentation/admin-guide/sysctl/ |
| D | net.rst | 179 Low latency busy poll timeout for socket reads. (needs CONFIG_NET_RX_BUSY_POLL)
180 Approximate time in us to busy loop waiting for packets on the device queue.
192 Low latency busy poll timeout for poll and select. (needs CONFIG_NET_RX_BUSY_POLL)
193 Approximate time in us to busy loop waiting for events.
197 Note that only sockets with SO_BUSY_POLL set will be busy polled,
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 34 - The ioctl can't be handled because the device is busy. This is
|
| /Documentation/userspace-api/media/dvb/ |
| D | video-fopen.rst | 105 - Device or resource busy.
|
| D | audio-fopen.rst | 97 - Device or resource busy.
|
| D | frontend_f_open.rst | 41 driver is temporarily busy.
|
| /Documentation/driver-api/thermal/ |
| D | intel_powerclamp.rst | 281 100% busy state with the disabled state.
288 If the system is not busy and has more than 25% idle time already,
292 If the system is busy (spin test below) and has less than 25% natural
|
| /Documentation/admin-guide/pm/ |
| D | intel-speed-select.rst | 215 To check if the average frequency is equal to the base frequency for a 100% busy
220 Then runs a busy workload on all CPUs, for example::
577 2 of the CPUs are busy and reaching max. frequency (which would be the base
597 From the above turbostat output, both CPU 3 and 4 are very busy and reaching
714 For this reason, this feature is only useful when system is busy utilizing all
785 Based on the data above, when all the CPUS are busy, the max. frequency of 3100
786 MHz can be achieved. If there is some busy workload on cpu 0 - 11 (e.g. stress)
909 This improved performance by around 3.3% improvement on a busy system. Here the
|
| /Documentation/ide/ |
| D | ide-tape.rst | 54 other device while the tape is busy executing a command. The
|
| D | ChangeLog.ide-floppy.1996-2002 | 57 * fix a lost interrupt problem. It appears the busy
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-xen-backend | 47 busy processing previous requests.
|
| /Documentation/networking/ |
| D | driver.rst | 12 transmit function will become busy.
|
12345