Searched +full:buffer +full:- +full:size (Results 1 – 25 of 402) sorted by relevance
12345678910>>...17
| /Documentation/core-api/ |
| D | swiotlb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 swiotlb is a memory buffer allocator used by the Linux kernel DMA layer. It is
9 buffer because of hardware limitations or other requirements. In such a case,
10 the DMA layer calls swiotlb to allocate a temporary memory buffer that conforms
11 to the limitations. The DMA is done to/from this temporary memory buffer, and
12 the CPU copies the data between the temporary buffer and the original target
13 memory buffer. This approach is generically called "bounce buffering", and the
14 temporary memory buffer is called a "bounce buffer".
19 These APIs use the device DMA attributes and kernel-wide settings to determine
24 Because the CPU copies data between the bounce buffer and the original target
[all …]
|
| D | circular-buffers.rst | 12 (1) Convenience functions for determining information about power-of-2 sized
16 buffer don't want to share a lock.
25 (*) What is a circular buffer?
27 (*) Measuring power-of-2 buffers.
30 - The producer.
31 - The consumer.
35 What is a circular buffer?
38 First of all, what is a circular buffer? A circular buffer is a buffer of
39 fixed, finite size into which there are two indices:
41 (1) A 'head' index - the point at which the producer inserts items into the
[all …]
|
| D | librs.rst | 2 Reed-Solomon Library Programming Interface
10 The generic Reed-Solomon Library provides encoding, decoding and error
13 Reed-Solomon codes are used in communication and storage applications to
30 ------------
54 --------
56 The encoder calculates the Reed-Solomon code over the given data length
57 and stores the result in the parity buffer. Note that the parity buffer
60 The expanded data can be inverted on the fly by providing a non-zero
63 Reed-Solomon code for all 0x00 is all 0x00. The code is inverted before
67 The databytes are expanded to the given symbol size on the fly. There is
[all …]
|
| /Documentation/ABI/testing/ |
| D | dell-smbios-wmi | 1 What: /dev/wmi/dell-smbios
7 through the Dell ACPI-WMI interface.
9 IOCTL's and buffer formats are defined in:
13 first determine the minimum size of the calling interface
14 buffer for your machine.
17 Commonly this size is either 4k or 32k.
19 To determine the size of the buffer read() a u64 dword from
20 the WMI character device /dev/wmi/dell-smbios.
22 2) After you've determined the minimum size of the calling
23 interface buffer, you can allocate a structure that represents
[all …]
|
| D | configfs-most | 9 # mount -t configfs none /sys/kernel/config/
19 configure the buffer size for this channel
22 configure the sub-buffer size for this channel
39 configure DBR data buffer size (this is used
60 configuration, the creation is post-poned until
74 configure the buffer size for this channel
77 configure the sub-buffer size for this channel
94 configure DBR data buffer size (this is used
115 configuration, the creation is post-poned until
129 configure the buffer size for this channel
[all …]
|
| D | configfs-usb-gadget-uac1_legacy | 1 What: /config/usb-gadget/gadget/functions/uac1_legacy.name
7 audio_buf_size - audio buffer size
8 fn_cap - capture pcm device file name
9 fn_cntl - control device file name
10 fn_play - playback pcm device file name
11 req_buf_size - ISO OUT endpoint request buffer size
12 req_count - ISO OUT endpoint request count
|
| /Documentation/userspace-api/media/v4l/ |
| D | buffer.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 A buffer contains data exchanged by application and driver using one of
11 the Streaming I/O methods. In the multi-planar API, the data is held in
12 planes, while the buffer structure acts as a container for the planes.
14 copied. These pointers, together with meta-information like timestamps
18 :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` ioctl. In the multi-planar API,
19 some plane-specific members of struct :c:type:`v4l2_buffer`,
27 ``V4L2_BUF_FLAG_TSTAMP_SRC_MASK`` in :ref:`buffer-flags`. These flags
33 mem-to-mem devices is an exception to the rule: the timestamp source
34 flags are copied from the OUTPUT video buffer to the CAPTURE video
[all …]
|
| D | selection-api-intro.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
8 shrink or enlarge it to an image of arbitrary size. Next, the devices
16 image stored in a memory buffer. The composing area specifies which part
17 of the buffer is actually written to by the hardware.
19 On a video *output* device the source is an image in a memory buffer,
22 select the part of display where the image should be displayed. The size
26 the device does supports neither cropping nor composing. Their size and
28 scaling then the cropping and composing rectangles have the same size.
|
| D | vidioc-create-bufs.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_CREATE_BUFS - Create buffers for Memory Mapped or User Pointer or DMA Buffer I/O
35 or :ref:`user pointer <userp>` or :ref:`DMA buffer <dmabuf>` I/O. It
53 ``type`` field the requested buffer size (for single-planar) or plane
54 sizes (for multi-planar formats) will be used for the allocated buffers.
55 The driver may return an error if the size(s) are not supported by the
58 The buffers created by this ioctl will have as minimum size the size
63 it is larger, then the value will be used as-is. In other words, the
64 driver may reject the requested size, but if it is accepted the driver
77 .. flat-table:: struct v4l2_create_buffers
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | circular-buffers.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
3 .. include:: ../disclaimer-zh_CN.rst
5 :Original: Documentation/core-api/circular-buffers.rst
41 - 生产者
42 - 消费者
53 (1) 'head'索引 - 生产者将元素插入缓冲区的位置。
55 (2) 'tail'索引 - 消费者在缓冲区中找到下一个元素的位置。
108 这里的每一个宏名义上都会返回一个介于0和buffer_size-1之间的值，但是：
138 ------
144 unsigned long head = buffer->head;
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-orion-net.txt | 12 set of controller registers. Each port node describes port-specific properties.
16 only one port associated. Multiple ports are implemented as multiple single-port
23 - #address-cells: shall be 1.
24 - #size-cells: shall be 0.
25 - compatible: shall be one of "marvell,orion-eth", "marvell,kirkwood-eth".
26 - reg: address and length of the controller registers.
29 - clocks: phandle reference to the controller clock.
30 - marvell,tx-checksum-limit: max tx packet size for hardware checksum.
35 - compatible: shall be one of "marvell,orion-eth-port",
36 "marvell,kirkwood-eth-port".
[all …]
|
| D | litex,liteeth.yaml | 1 # SPDX-License-Identifier: GPL-2.0-or-later OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Joel Stanley <joel@jms.id.au>
17 https://github.com/enjoy-digital/liteeth/.
20 - $ref: ethernet-controller.yaml#
28 - description: MAC registers
29 - description: MDIO registers
30 - description: Packet buffer
32 reg-names:
[all …]
|
| D | marvell-neta-bm.txt | 1 * Marvell Armada 380/XP Buffer Manager driver (BM)
5 - compatible: should be "marvell,armada-380-neta-bm".
6 - reg: address and length of the register set for the device.
7 - clocks: a pointer to the reference clock for this device.
8 - internal-mem: a phandle to BM internal SRAM definition.
12 - pool<0 : 3>,capacity: size of external buffer pointers' ring maintained
17 - pool<0 : 3>,pkt-size: maximum size of a packet accepted by a given buffer
23 refer to Documentation/devicetree/bindings/net/marvell-armada-370-neta.txt.
27 - main node:
30 compatible = "marvell,armada-380-neta-bm";
[all …]
|
| /Documentation/userspace-api/gpio/ |
| D | gpio-v2-line-event-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINE_EVENT_READ - Read edge detection events for lines from a request.
24 :c:type:`request.fd<gpio_v2_line_request>` by gpio-v2-get-line-ioctl.rst.
27 The buffer to contain the :c:type:`events<gpio_v2_line_event>`.
31 least the size of a :c:type:`gpio_v2_line_event`.
49 occurrence and stores them in a buffer from where they can be read by
52 Events read from the buffer are always in the same order that they were
56 The size of the kernel event buffer is fixed at the time of line request
59 The default size is 16 times the number of lines requested.
61 The buffer may overflow if bursts of events occur quicker than they are read
[all …]
|
| D | gpio-v2-lineinfo-changed-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 GPIO_V2_LINEINFO_CHANGED_READ - Read line info changed events for watched
27 The buffer to contain the :c:type:`events<gpio_v2_line_info_changed>`.
30 The number of bytes available in ``buf``, which must be at least the size
43 not its value. Use gpio-v2-line-event-read.rst to receive events when a
46 A line must be watched using gpio-v2-get-lineinfo-watch-ioctl.rst to generate
50 The kernel timestamps events when they occur and stores them in a buffer
53 The size of the kernel event buffer is fixed at 32 events per ``chip_fd``.
55 The buffer may overflow if bursts of events occur quicker than they are read
59 Events read from the buffer are always in the same order that they were
[all …]
|
| D | gpio-lineinfo-changed-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-lineinfo-changed-read.rst.
16 GPIO_LINEINFO_CHANGED_READ - Read line info change events for watched lines
31 The buffer to contain the :c:type:`events<gpioline_info_changed>`.
34 The number of bytes available in ``buf``, which must be at least the size
47 not its value. Use gpio-lineevent-data-read.rst to receive events when a
50 A line must be watched using gpio-get-lineinfo-watch-ioctl.rst to generate
54 The kernel timestamps events when they occur and stores them in a buffer
57 The size of the kernel event buffer is fixed at 32 events per ``chip_fd``.
59 The buffer may overflow if bursts of events occur quicker than they are read
[all …]
|
| D | gpio-lineevent-data-read.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 gpio-v2-line-event-read.rst.
16 GPIO_LINEEVENT_DATA_READ - Read edge detection events from a line event.
28 :c:type:`request.fd<gpioevent_request>` by gpio-get-lineevent-ioctl.rst.
31 The buffer to contain the :c:type:`events<gpioevent_data>`.
35 least the size of a :c:type:`gpioevent_data`.
53 occurrence and stores them in a buffer from where they can be read by
62 Events read from the buffer are always in the same order that they were
65 The size of the kernel event buffer is fixed at 16 events.
67 The buffer may overflow if bursts of events occur quicker than they are read
[all …]
|
| /Documentation/sound/designs/ |
| D | compress-accel.rst | 2 ALSA Co-processor Acceleration API
16 is able to handle "tasks" that are not bound to real-time operations
24 - serialization of multiple tasks for user space to allow multiple
27 - separate buffers (input + output) for each operation
29 - expose buffers using mmap to user space
31 - signal user space when the task is finished (standard poll mechanism)
47 Data I/O mechanism is using standard dma-buf interface with all advantages
48 like mmap, standard I/O, buffer sharing etc. One buffer is used for the
49 input data and second (separate) buffer is used for the output data. Each task
53 for given device. The fragment_size limits the input buffer size for the given
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | omap3isp-uapi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 ------
33 generated whenever a statistics buffer can be dequeued by a user space
37 - V4L2_EVENT_OMAP3ISP_AEWB
38 - V4L2_EVENT_OMAP3ISP_AF
39 - V4L2_EVENT_OMAP3ISP_HIST
43 event as usual, but no related statistics buffer. In this case
44 omap3isp_stat_event_status.buf_err is set to non-zero.
48 --------------
52 does not fall under the standard IOCTLs --- gamma tables and configuration of
[all …]
|
| /Documentation/gpu/ |
| D | msm-crash-dump.rst | 14 by a (-).
17 --------
38 rbbm-status
52 last-fence
55 retired-fence
64 size
65 Maximum size of the ringbuffer programmed in the hardware.
73 Each buffer object will have a uinque iova.
76 GPU address of the buffer object.
78 size
[all …]
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | ramoops.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reserved-memory/ramoops.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 recovered after a reboot. This is a child-node of "/reserved-memory", and
16 as kernel log messages, or for optional ECC error-correction data. The total
17 size of these optional buffers must fit in the reserved region.
19 Any remaining space will be used for a circular buffer of oops and panic
20 records. These records have a configurable size, with a size of 0 indicating
23 At least one of "record-size", "console-size", "ftrace-size", or "pmsg-size"
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-querybuf.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 DMX_QUERYBUF - Query the status of a buffer
37 be used to query the status of a buffer at any time after buffers have
47 On success, the ``offset`` will contain the offset of the buffer from the
48 start of the device memory, the ``length`` field its size, and the
49 ``bytesused`` the number of bytes occupied by data in the buffer (payload).
55 buffer from the start of the device memory, the ``length`` field its size,
56 and the ``bytesused`` the number of bytes occupied by data in the buffer
59 On error it returns -1 and the ``errno`` variable is set
61 :ref:`Generic Error Codes <gen-errors>` chapter.
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 2 BPF ring buffer
5 This document describes BPF ring buffer design, API, and implementation details.
12 ----------
15 existing perf buffer, which prompted creation of a new ring buffer
18 - more efficient memory utilization by sharing ring buffer across CPUs;
19 - preserving ordering of events that happen sequentially in time, even across
22 These two problems are independent, but perf buffer fails to satisfy both.
23 Both are a result of a choice to have per-CPU perf ring buffer. Both can be
24 also solved by having an MPSC implementation of ring buffer. The ordering
25 problem could technically be solved for perf buffer with some in-kernel
[all …]
|
| /Documentation/scsi/ |
| D | st.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 flexible method and applicable to single-user workstations. However,
28 parameters, like block size and density using the MTSETDRVBUFFER ioctl.
32 drive performs auto-detection of the tape format well (like some
33 QIC-drives). The result is that any tape can be read, writing can be
37 does not perform auto-detection well enough and there is a single
40 or not :-).
57 between formats in multi-tape operations (the explicitly overridden
71 The driver supports fixed and variable block size (within buffer
72 limits). Both the auto-rewind (minor equals device number) and
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 2 dm-zoned
5 The dm-zoned device mapper target exposes a zoned block device (ZBC and
7 pattern constraints. In effect, it implements a drive-managed zoned
10 host-managed zoned block devices and can mitigate the potential
11 device-side performance degradation due to excessive random writes on
12 host-aware zoned block devices.
21 http://www.t13.org/Documents/UploadedDocuments/docs2015/di537r05-Zoned_Device_ATA_Command_Set_ZAC.p…
23 The dm-zoned implementation is simple and minimizes system overhead (CPU
25 host-managed disk with 256 MB zones, dm-zoned memory usage per disk
29 dm-zoned target devices are formatted and checked using the dmzadm
[all …]
|
12345678910>>...17