| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | ca-fopen.rst | 45 - open in non-blocking mode
46 (blocking mode is the default)
56 significance of blocking or non-blocking mode is described in the
59 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | audio-fopen.rst | 56 - O_NONBLOCK open in non-blocking mode
61 - (blocking mode is the default)
70 blocking or non-blocking mode is described in the documentation for
72 of the open() call itself. A device opened in blocking mode can later be
73 put into non-blocking mode (and vice versa) using the F_SETFL command
|
| D | video-fopen.rst | 55 - O_NONBLOCK open in non-blocking mode
60 - (blocking mode is the default)
70 significance of blocking or non-blocking mode is described in the
73 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | dmx-fopen.rst | 47 - open in non-blocking mode
48 (blocking mode is the default)
65 The significance of blocking or non-blocking mode is described in the
68 in blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | fe-get-event.rst | 38 not available, the behavior depends on whether the device is in blocking
39 or non-blocking mode. In the latter case, the call fails immediately
62 - There is no event pending, and the device is in non-blocking mode.
|
| D | frontend_f_open.rst | 64 non-blocking or blocking mode was specified. A front-end device opened
65 in blocking mode can later be put into non-blocking mode (and vice
|
| D | video-get-event.rst | 58 in blocking or non-blocking mode. In the latter case, the call fails
101 - There is no event pending, and the device is in non-blocking mode.
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | shtc1 | 31 1. blocking (pull the I2C clock line down while performing the measurement) or
32 non-blocking mode. Blocking mode will guarantee the fastest result but
33 the I2C bus will be busy during that time. By default, non-blocking mode
35 want to use blocking mode.
|
| D | sht3x | 27 1. blocking (pull the I2C clock line down while performing the measurement) or
28 non-blocking mode. Blocking mode will guarantee the fastest result but
29 the I2C bus will be busy during that time. By default, non-blocking mode
31 want to use blocking mode.
|
| /Linux-v4.19/Documentation/ |
| D | mailbox.txt | 43 The client might want to operate in blocking mode (synchronously
44 send a message through before returning) or non-blocking/async mode (submit
93 /* Populate non-blocking mode client */
103 /* Populate blocking mode client */
106 dc_sync->cl.tx_done = NULL; /* operate in blocking mode */
123 /* Send message to remote in blocking mode */
|
| /Linux-v4.19/Documentation/mmc/ |
| D | mmc-async-req.txt | 9 The intention of non-blocking (asynchronous) MMC requests is to minimize the
12 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
19 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
39 truly non-blocking. If there is an ongoing async request it waits
|
| /Linux-v4.19/Documentation/block/ |
| D | null_blk.txt | 78 blocking=[0/1]: Default: 0
79 0: Register as a non-blocking blk-mq driver device.
80 1: Register as a blocking blk-mq driver device, null_blk will set
|
| /Linux-v4.19/include/linux/ceph/ |
| D | msgpool.h | 19 int front_len, int size, bool blocking,
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | gfs2-glocks.txt | 10 2. A non-blocking bit lock, GLF_LOCK, which is used to prevent other
151 1. DLM lock time (non-blocking requests)
152 2. DLM lock time (blocking requests)
155 A non-blocking request is one which will complete right
160 "try lock" flag is set. A blocking request covers all the other
209 srtt - Smoothed round trip time for non-blocking dlm requests
211 srttb - Smoothed round trip time for (potentially) blocking dlm requests
|
| /Linux-v4.19/drivers/staging/vc04_services/interface/vchiq_arm/ |
| D | vchiq_ioctl.h | 81 int blocking; member
|
| /Linux-v4.19/Documentation/media/uapi/cec/ |
| D | cec-ioc-receive.rst | 40 If the file descriptor is in non-blocking mode and there are no received
42 error code. If the file descriptor is in blocking mode and ``timeout``
50 2. the result of an earlier non-blocking transmit (the ``sequence`` field will
63 If the file descriptor is in non-blocking mode then the transmit will
124 the transmit result (when transmit was called in non-blocking mode). This
317 No messages are in the receive queue, and the filehandle is in non-blocking mode.
|
| D | cec-ioc-dqevent.rst | 35 non-blocking mode and no event is pending, then it will return -1 and
239 This is returned when the filehandle is in non-blocking mode and there
243 An interrupt (e.g. Ctrl-C) arrived while in blocking mode waiting for
|
| /Linux-v4.19/drivers/block/ |
| D | null_blk.h | 60 bool blocking; /* blocking blk-mq device */ member
|
| /Linux-v4.19/net/ceph/ |
| D | msgpool.c | 38 int front_len, int size, bool blocking, const char *name) in ceph_msgpool_init() argument
|
| /Linux-v4.19/kernel/rcu/ |
| D | Kconfig | 56 permits arbitrary sleeping or blocking within RCU read-side critical
198 This option also prevents heavy loads from blocking RCU
212 readers blocking that grace period. Note that any RCU reader
213 blocking an expedited RCU grace period is boosted immediately.
|
| /Linux-v4.19/Documentation/s390/ |
| D | monreader.txt | 119 There are two alternative methods for reading: either non-blocking read in
120 conjunction with polling, or blocking read without polling. IOCTLs are not
172 EAGAIN: occurs on a non-blocking read if there is no data available at the
174 use polling for non-blocking reads.
|
| /Linux-v4.19/Documentation/devicetree/bindings/mailbox/ |
| D | stm32-ipcc.txt | 3 The IPCC block provides a non blocking signaling mechanism to post and
|
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-s-hw-freq-seek.rst | 59 If this ioctl is called from a non-blocking filehandle, then ``EAGAIN``
134 non-blocking mode.
|
| /Linux-v4.19/Documentation/RCU/ |
| D | rcu.txt | 41 counters. These counters allow limited types of blocking within
43 counters, and permits general blocking within RCU read-side
|
| /Linux-v4.19/Documentation/input/joydev/ |
| D | joystick-api.rst | 20 information. The joystick device can be used in either blocking or
38 By default, the device is opened in blocking mode::
152 If you open the device in blocking mode, a read will block (that is,
161 b) open the device in non-blocking mode (O_NONBLOCK)
|
