Searched full:blocking (Results 1 – 25 of 1615) sorted by relevance
12345678910>>...65
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/ |
| D | ca-fopen.rst | 43 - open in non-blocking mode
44 (blocking mode is the default)
53 significance of blocking or non-blocking mode is described in the
56 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | dmx-fopen.rst | 46 - open in non-blocking mode
47 (blocking mode is the default)
63 The significance of blocking or non-blocking mode is described in the
66 in blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | frontend_f_open.rst | 61 non-blocking or blocking mode was specified. A front-end device opened
62 in blocking mode can later be put into non-blocking mode (and vice
|
| D | fe-get-event.rst | 37 not available, the behavior depends on whether the device is in blocking
38 or non-blocking mode. In the latter case, the call fails immediately
58 - There is no event pending, and the device is in non-blocking mode.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | ca-fopen.rst | 43 - open in non-blocking mode
44 (blocking mode is the default)
53 significance of blocking or non-blocking mode is described in the
56 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | dmx-fopen.rst | 46 - open in non-blocking mode
47 (blocking mode is the default)
63 The significance of blocking or non-blocking mode is described in the
66 in blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | video-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode
59 - (blocking mode is the default)
68 significance of blocking or non-blocking mode is described in the
71 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | audio-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode
59 - (blocking mode is the default)
67 blocking or non-blocking mode is described in the documentation for
69 of the open() call itself. A device opened in blocking mode can later be
70 put into non-blocking mode (and vice versa) using the F_SETFL command
|
| D | frontend_f_open.rst | 61 non-blocking or blocking mode was specified. A front-end device opened
62 in blocking mode can later be put into non-blocking mode (and vice
|
| D | fe-get-event.rst | 37 not available, the behavior depends on whether the device is in blocking
38 or non-blocking mode. In the latter case, the call fails immediately
58 - There is no event pending, and the device is in non-blocking mode.
|
| /kernel/linux/linux-6.6/drivers/staging/media/av7110/ |
| D | video-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode
59 - (blocking mode is the default)
68 significance of blocking or non-blocking mode is described in the
71 blocking mode can later be put into non-blocking mode (and vice versa)
|
| D | audio-fopen.rst | 54 - O_NONBLOCK open in non-blocking mode
59 - (blocking mode is the default)
67 blocking or non-blocking mode is described in the documentation for
69 of the open() call itself. A device opened in blocking mode can later be
70 put into non-blocking mode (and vice versa) using the F_SETFL command
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | shtc1.rst | 53 1. blocking (pull the I2C clock line down while performing the measurement) or
54 non-blocking mode. Blocking mode will guarantee the fastest result but
55 the I2C bus will be busy during that time. By default, non-blocking mode
57 want to use blocking mode.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | shtc1.rst | 53 1. blocking (pull the I2C clock line down while performing the measurement) or
54 non-blocking mode. Blocking mode will guarantee the fastest result but
55 the I2C bus will be busy during that time. By default, non-blocking mode
57 want to use blocking mode.
|
| D | sht3x.rst | 33 1. blocking (pull the I2C clock line down while performing the measurement) or
34 non-blocking mode. Blocking mode will guarantee the fastest result but
35 the I2C bus will be busy during that time. By default, non-blocking mode
37 want to use blocking mode.
|
| /kernel/linux/linux-5.10/fs/btrfs/ |
| D | locking.c | 30 * - blocking lock semantics
39 * is done by read-write spinlock and the blocking part is implemented using
45 * blocking semantics - the low-level rwlock is not held but the counter
46 * denotes how many times the blocking lock was held;
91 * Locking pattern - blocking
94 * The blocking write uses the following scheme. The +--+ denotes the spinning
106 * Blocking read is similar.
188 * Mark already held read lock as blocking. Can be nested in write lock by the
194 * The rwlock is released and blocking reader counter is increased.
213 * Mark already held write lock as blocking.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | mailbox.rst | 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 */
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | mailbox.rst | 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 */
|
| /kernel/linux/linux-6.6/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/ |
| D | event_fifo_public.h | 22 /*! Blocking read from an event source EVENT[ID]
31 /*! Conditional blocking wait for an event source EVENT[ID]
42 /*! Blocking read from an event source EVENT[ID]
51 /*! Blocking write to an event sink EVENT[ID]
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/hive_isp_css_include/host/ |
| D | event_fifo_public.h | 22 /*! Blocking read from an event source EVENT[ID]
31 /*! Conditional blocking wait for an event source EVENT[ID]
42 /*! Blocking read from an event source EVENT[ID]
51 /*! Blocking write to an event sink EVENT[ID]
|
| /kernel/linux/linux-6.6/kernel/ |
| D | notifier.c | 63 * @nl: Pointer to head of the blocking notifier chain
110 * @nl: Pointer to head of the blocking notifier chain
253 * Blocking notifier chain routines. All access to the chain is
278 * blocking_notifier_chain_register - Add notifier to a blocking notifier chain
279 * @nh: Pointer to head of the blocking notifier chain
282 * Adds a notifier to a blocking notifier chain.
295 * blocking_notifier_chain_register_unique_prio - Add notifier to a blocking notifier chain
296 * @nh: Pointer to head of the blocking notifier chain
299 * Adds a notifier to an blocking notifier chain if there is no other
312 * blocking_notifier_chain_unregister - Remove notifier from a blocking notifier chain
[all …]
|
| /kernel/linux/linux-5.10/kernel/ |
| D | notifier.c | 54 * @nl: Pointer to head of the blocking notifier chain
100 * @nl: Pointer to head of the blocking notifier chain
226 * Blocking notifier chain routines. All access to the chain is
231 * blocking_notifier_chain_register - Add notifier to a blocking notifier chain
232 * @nh: Pointer to head of the blocking notifier chain
235 * Adds a notifier to a blocking notifier chain.
261 * blocking_notifier_chain_unregister - Remove notifier from a blocking notifier chain
262 * @nh: Pointer to head of the blocking notifier chain
265 * Removes a notifier from a blocking notifier chain.
310 * blocking_notifier_call_chain - Call functions in a blocking notifier chain
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/cec/ |
| D | cec-ioc-receive.rst | 42 If the file descriptor is in non-blocking mode and there are no received
44 error code. If the file descriptor is in blocking mode and ``timeout``
52 2. the transmit result of an earlier non-blocking transmit (the ``sequence``
55 3. the reply to an earlier non-blocking transmit (the ``sequence`` field will
68 If the file descriptor is in non-blocking mode then the transmit will
71 If a non-blocking transmit also specified waiting for a reply, then
128 the transmit result for a non-blocking transmit. This allows the application
131 In addition, if a non-blocking transmit will wait for a reply (ii.e. ``timeout``
171 When calling :ref:`ioctl CEC_TRANSMIT <CEC_TRANSMIT>` in non-blocking mode,
351 No messages are in the receive queue, and the filehandle is in non-blocking mode.
|
| /kernel/linux/linux-6.6/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 15 The intention of non-blocking (asynchronous) MMC requests is to minimize the
19 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
26 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
48 truly non-blocking. If there is an ongoing async request it waits
|
| /kernel/linux/linux-5.10/Documentation/driver-api/mmc/ |
| D | mmc-async-req.rst | 15 The intention of non-blocking (asynchronous) MMC requests is to minimize the
19 dma_unmap_sg are processing. Using non-blocking MMC requests makes it
26 The mmc_blk_issue_rw_rq() in the MMC block driver is made non-blocking.
48 truly non-blocking. If there is an ongoing async request it waits
|
12345678910>>...65