Searched +full:wait +full:- +full:queue (Results 1 – 25 of 97) sorted by relevance
1234
| /Documentation/userspace-api/media/cec/ |
| D | cec-func-poll.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 .. _cec-func-poll:
13 cec-poll - Wait for some event on a file descriptor
18 .. code-block:: c
34 Timeout to wait for events
39 With the :c:func:`poll()` function applications can wait for CEC
45 is non-zero). CEC devices set the ``POLLIN`` and ``POLLRDNORM`` flags in
46 the ``revents`` field if there are messages in the receive queue. If the
47 transmit queue has room for new messages, the ``POLLOUT`` and
48 ``POLLWRNORM`` flags are set. If there are events in the event queue,
[all …]
|
| D | cec-ioc-receive.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
14 CEC_RECEIVE, CEC_TRANSMIT - Receive or transmit a CEC message
42 If the file descriptor is in non-blocking mode and there are no received
43 messages pending, then it will return -1 and set errno to the ``EAGAIN``
45 is non-zero and no message arrived within ``timeout`` milliseconds, then
46 it will return -1 and set errno to the ``ETIMEDOUT`` error code.
51 be 0, ``tx_status`` will be 0 and ``rx_status`` will be non-zero).
52 2. the transmit result of an earlier non-blocking transmit (the ``sequence``
53 field will be non-zero, ``tx_status`` will be non-zero and ``rx_status``
55 3. the reply to an earlier non-blocking transmit (the ``sequence`` field will
[all …]
|
| /Documentation/block/ |
| D | stat.rst | 30 read merges requests number of read I/Os merged with in-queue I/O
32 read ticks milliseconds total wait time for read requests
34 write merges requests number of write I/Os merged with in-queue I/O
36 write ticks milliseconds total wait time for write requests
39 time_in_queue milliseconds total wait time for all requests
41 discard merges requests number of discard I/Os merged with in-queue I/O
43 discard ticks milliseconds total wait time for discard requests
45 flush ticks milliseconds total wait time for flush requests
65 already-queued I/O request.
72 standard UNIX 512-byte sectors, not any device- or filesystem-specific
[all …]
|
| D | null_blk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 block-layer implementations. It emulates a block device of X gigabytes in size.
13 the request queue. The following instances are possible:
15 Multi-queue block-layer
17 - Request-based.
18 - Configurable submission queues per device.
20 No block-layer (Known as bio-based)
22 - Bio-based. IO requests are submitted directly to the device driver.
23 - Directly accepts bio data structure and returns them.
25 All of them have a completion queue for each core in the system.
[all …]
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | fsl-mx25-tcq.txt | 1 Freescale mx25 TS conversion queue module
3 mx25 touchscreen conversion queue module which controls the ADC unit of the
7 - compatible: Should be "fsl,imx25-tcq".
8 - reg: Memory range of the device.
9 - interrupts: Should be the interrupt number associated with this module within
11 - fsl,wires: Should be '<4>' or '<5>'
14 - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
15 - fsl,pen-threshold: Pen-down threshold for the touchscreen. This is a value
20 - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
21 the actual touch detection to wait for an even charge distribution in the
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-zip | 3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
9 Contact: linux-crypto@vger.kernel.org
15 Contact: linux-crypto@vger.kernel.org
24 Contact: linux-crypto@vger.kernel.org
31 Contact: linux-crypto@vger.kernel.org
41 Contact: linux-crypto@vger.kernel.org
48 Contact: linux-crypto@vger.kernel.org
49 Description: One QM may contain multiple queues. Select specific queue to
55 Contact: linux-crypto@vger.kernel.org
[all …]
|
| D | debugfs-hisi-sec | 3 Contact: linux-crypto@vger.kernel.org
11 Contact: linux-crypto@vger.kernel.org
19 Contact: linux-crypto@vger.kernel.org
29 Contact: linux-crypto@vger.kernel.org
36 Contact: linux-crypto@vger.kernel.org
38 queue to show its debug registers in above 'regs'.
43 Contact: linux-crypto@vger.kernel.org
51 Contact: linux-crypto@vger.kernel.org
58 Contact: linux-crypto@vger.kernel.org
59 Description: Dump the number of QM async event queue interrupts.
[all …]
|
| D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
3 Contact: linux-crypto@vger.kernel.org
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
9 Contact: linux-crypto@vger.kernel.org
16 Contact: linux-crypto@vger.kernel.org
25 Contact: linux-crypto@vger.kernel.org
32 Contact: linux-crypto@vger.kernel.org
42 Contact: linux-crypto@vger.kernel.org
48 Contact: linux-crypto@vger.kernel.org
55 Contact: linux-crypto@vger.kernel.org
[all …]
|
| D | sysfs-class-pktcdvd | 2 ---------------
23 pktcdvd[0-7] <pktdevid> <blkdevid>
27 What: /sys/class/pktcdvd/pktcdvd[0-7]/dev
28 What: /sys/class/pktcdvd/pktcdvd[0-7]/uevent
38 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_started
39 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/packets_finished
40 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_written
41 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read
42 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/kb_read_gather
43 What: /sys/class/pktcdvd/pktcdvd[0-7]/stat/reset
[all …]
|
| /Documentation/scheduler/ |
| D | completion.rst | 2 Completions - "wait for completion" barrier APIs
6 -------------
8 If you have one or more threads that must wait for some kernel activity
10 race-free solution to this problem. Semantically they are somewhat like a
11 pthread_barrier() and have similar use-cases.
14 misuse of locks/semaphores and busy-loops. Any time you think of using
34 ------
38 - the initialization of the 'struct completion' synchronization object
39 - the waiting part through a call to one of the variants of wait_for_completion(),
40 - the signaling side through a call to complete() or complete_all().
[all …]
|
| /Documentation/input/joydev/ |
| D | joystick-api.rst | 1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
65 -------------
86 ---------------
108 --------------
110 For an axis, ``value`` is a signed integer between -32767 and +32767
141 -------------
153 wait) forever until an event is generated and effectively read. There
154 are two alternatives if you can't afford to wait forever (which is,
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | request-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
4 .. _media-request-api:
12 the same pipeline to reconfigure and collaborate closely on a per-frame basis.
14 to specific frames (aka 'per-frame controls') in order to be used efficiently.
16 While the initial use-case was V4L2, it can be extended to other subsystems
20 it is, it is terribly inefficient: user-space would have to flush all activity
21 on the media pipeline, reconfigure it for the next frame, queue the buffers to
22 be processed with that configuration, and wait until they are all available for
28 specific buffers. This allows user-space to schedule several tasks ("requests")
34 -------------
[all …]
|
| D | media-request-ioc-queue.rst | 1 .. SPDX-License-Identifier: GPL-2.0 OR GFDL-1.1-no-invariants-or-later
13 MEDIA_REQUEST_IOC_QUEUE - Queue a request
31 If the media device supports :ref:`requests <media-request-api>`, then
32 this request ioctl can be used to queue a previously allocated request.
35 :ref:`polled <request-func-poll>` to wait for the request to complete.
49 queued directly and you next try to queue a request, or vice versa.
57 On success 0 is returned, on error -1 and the ``errno`` variable is set
59 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 2 PXA/MMP - DMA Slave controller
11 This implies that the queuing doesn't wait for the previous transfer end,
14 A transfer which is submitted and issued on a phy doesn't wait for a phy to
22 at the time of irq/dma tx2 is already finished, tx1->complete() and
23 tx2->complete() should be called.
36 A driver should be able to request a priority, especially the real-time
46 b) Transfer anatomy for a scatter-gather transfer
50 +------------+-----+---------------+----------------+-----------------+
51 | desc-sg[0] | ... | desc-sg[last] | status updater | finisher/linker |
52 +------------+-----+---------------+----------------+-----------------+
[all …]
|
| D | client.rst | 8 ``Documentation/crypto/async-tx-api.rst``
11 Below is a guide to device driver writers on how to use the Slave-DMA API of the
19 - Allocate a DMA slave channel
21 - Set slave and controller specific parameters
23 - Get a descriptor for transaction
25 - Submit the transaction
27 - Issue pending requests and wait for callback notification
40 .. code-block:: c
66 .. code-block:: c
79 DMA-engine are:
[all …]
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
9 -
11 name: xdp-act
12 render-max: true
14 -
19 -
23 -
24 name: ndo-xmit
27 -
28 name: xsk-zerocopy
[all …]
|
| /Documentation/networking/ |
| D | driver.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 ------------------
21 ----------
25 be aborted. If necessary, poll or wait for completion of
28 Auto-close
29 ----------
38 ----------------------
45 Instead it must maintain the queue properly. For example,
46 for a driver implementing scatter-gather this means:
48 .. code-block:: c
[all …]
|
| D | napi.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
30 of the NAPI instance while the method is the driver-specific event
37 -----------
55 ------------
64 argument - drivers can process completions for any number of Tx
95 not call napi_complete_done() and wait to be called again,
96 or return ``budget - 1``.
101 -------------
109 As mentioned in the :ref:`drv_ctrl` section - napi_disable() and subsequent
110 calls to the poll method only wait for the ownership of the instance
[all …]
|
| D | snmp_counter.rst | 17 .. _RFC1213 ipInReceives: https://tools.ietf.org/html/rfc1213#page-26
30 .. _RFC1213 ipInDelivers: https://tools.ietf.org/html/rfc1213#page-28
41 .. _RFC1213 ipOutRequests: https://tools.ietf.org/html/rfc1213#page-28
60 .. _Explicit Congestion Notification: https://tools.ietf.org/html/rfc3168#page-6
73 .. _RFC1213 ipInHdrErrors: https://tools.ietf.org/html/rfc1213#page-27
81 .. _RFC1213 ipInAddrErrors: https://tools.ietf.org/html/rfc1213#page-27
98 .. _RFC1213 ipInUnknownProtos: https://tools.ietf.org/html/rfc1213#page-27
111 .. _RFC1213 ipInDiscards: https://tools.ietf.org/html/rfc1213#page-28
118 .. _RFC1213 ipOutDiscards: https://tools.ietf.org/html/rfc1213#page-28
125 .. _RFC1213 ipOutNoRoutes: https://tools.ietf.org/html/rfc1213#page-29
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-stateless-decoder.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 Memory-to-memory Stateless Video Decoder Interface
18 This section describes how user-space ("the client") is expected to communicate
24 Stateless decoders make use of the :ref:`media-request-api`. A stateless
26 ``OUTPUT`` queue when :c:func:`VIDIOC_REQBUFS` or :c:func:`VIDIOC_CREATE_BUFS`
33 ``OUTPUT`` queue.
39 calls :c:func:`VIDIOC_ENUM_FMT` on the ``OUTPUT`` queue.
42 irrespective of the format currently set on the ``CAPTURE`` queue.
45 codec-specific capability controls (such as H.264 profiles) to the set
49 :c:func:`VIDIOC_ENUM_FMT` on the ``CAPTURE`` queue.
[all …]
|
| D | userp.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
21 data are exchanged, these pointers and meta-information are passed in
23 :c:type:`v4l2_plane` in the multi-planar API case). The
33 .. code-block:: c
41 if (ioctl (fd, VIDIOC_REQBUFS, &reqbuf) == -1) {
74 application waits until a filled buffer can be dequeued, and re-enqueues
78 buffers it must wait until an empty buffer can be dequeued and reused.
81 <VIDIOC_QBUF>` blocks when no buffer is in the outgoing queue. When the
85 <func-select>` or :c:func:`poll()` function are always
109 Anyway, the process of swapping, locking or generating scatter-gather
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 5 channels and flows for the QMSS(Queue Manager SubSystem) who triggers
13 ------------------
15 ------------------
17 |-> DMA instance #0
19 |-> DMA instance #1
23 |-> DMA instance #n
27 - compatible: Should be "ti,keystone-navigator-dma"
28 - clocks: phandle to dma instances clocks. The clock handles can be as
31 - ti,navigator-cloud-address: Should contain base address for the multi-core
34 into DMA and the DMA uses it as the physical addresses to reach queue
[all …]
|
| /Documentation/locking/ |
| D | mutex-design.rst | 10 -----------------
24 --------------
28 (->owner) to keep track of the lock state during its lifetime. Field owner
32 if waiter list is non-empty). In its most basic form it also includes a
33 wait-queue and a spinlock that serializes access to it. Furthermore,
34 CONFIG_MUTEX_SPIN_ON_OWNER=y systems use a spinner MCS lock (->osq), described
52 The MCS lock (proposed by Mellor-Crummey and Scott) is a simple spinlock
55 cacheline bouncing that common test-and-set spinlock implementations
56 incur. An MCS-like lock is specially tailored for optimistic spinning
59 the MCS spinlock queue when they need to reschedule. This further helps
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | internal.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
54 internal-api
63 Lower-level packet transport is implemented in the *packet transport layer
68 packet payloads to higher-level layers.
71 around command-type packet payloads, i.e. requests (sent from host to EC),
90 Refer to Documentation/driver-api/surface_aggregator/client.rst for
93 that chapter and the Documentation/driver-api/surface_aggregator/ssh.rst
104 -------
140 queue and pending set.
147 the packet queue and cleared when it is dequeued.
[all …]
|
| /Documentation/core-api/ |
| D | watch_queue.rst | 14 "General setup"/"General notification queue"
29 additions to the ring - which might end up interleaved with notification
45 Note that when producing a notification, the kernel does not wait for the
65 internally by the watch queue itself. There are two subtypes:
81 and 255. Multiple watches may share a queue, and this provides a means to
84 * A type-specific field (WATCH_INFO_TYPE_INFO). This is set by the
100 non-global watch list is typically referred to by reference to the object it
122 Watch Queue (Notification Output) API
125 A "watch queue" is the buffer allocated by an application that notification
134 This can be used to look up an opaque pointer to the watch queue from the
[all …]
|
1234