Searched full:pipes (Results 1 – 24 of 24) sorted by relevance
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 50 For this hardware example, we have 4 pipes (if you don't know what AMD pipe
53 configuration for optimal single display output (e.g., 2 pipes per plane).
56 display - will see 4 pipes in use, 2 per plane.
204 the two displays, we need to use 2 pipes. See the example below where we avoid
207 - 1 display (1 pipe) + MPO (1 pipe), we will use two pipes
208 - 2 displays (2 pipes) + MPO (1-2 pipes); we will use 4 pipes. MPO in the
209 middle of both displays needs 2 pipes.
210 - 3 Displays (3 pipes) + MPO (1-2 pipes), we need 5 pipes.
217 * When ASIC has 3 pipes, AMD hardware can NOT support 2 displays with MPO
218 * When ASIC has 4 pipes, AMD hardware can NOT support 3 displays with MPO
[all …]
|
| D | dc-glossary.rst | 92 Display Pipes and Planes
174 Multiple pipes and plane combine
|
| D | dcn-overview.rst | 191 for most other updates that don't require enabling or disabling of new pipes.
193 (Note: There are many scenarios when DC will decide to reserve extra pipes
|
| D | dc-debug.rst | 51 Sometimes we need to debug if DCN is splitting pipes correctly, and visual
|
| /Documentation/driver-api/ |
| D | xillybus.rst | 17 -- Seekable pipes
23 -- Channels, pipes, and the message channel
85 project to another (the number of data pipes needed in each direction and
90 Xillybus presents independent data streams, which resemble pipes or TCP/IP
125 possibly pressing CTRL-C as some stage, even though the xillybus_* pipes have
128 The driver and hardware are designed to behave sensibly as pipes, including:
138 device files are treated like two independent pipes (except for sharing a
144 Xillybus pipes are configured (on the IP core) to be either synchronous or
154 For FPGA to host pipes, asynchronous pipes allow data transfer from the FPGA
156 has been requested by a read() call. On synchronous pipes, only the amount
[all …]
|
| /Documentation/filesystems/ |
| D | splice.rst | 2 splice and pipes
13 pipes API
|
| D | 9p.rst | 213 This can be used to share devices/named pipes/sockets between
|
| D | hpfs.rst | 330 2.03 Char, block devices and pipes are correctly created
|
| D | fscrypt.rst | 1278 that is, named pipes, device nodes, and UNIX domain sockets --- will
|
| /Documentation/admin-guide/sysctl/ |
| D | fs.rst | 152 Maximum total number of pages a non-privileged user may allocate for pipes.
153 Once this limit is reached, no new pipes may be allocated until usage goes
161 Maximum total number of pages a non-privileged user may allocate for pipes
163 new pipes will be limited to a single page in size for this user in order to
166 allocate up to 1024 pipes at their default size. When set to 0, no limit is
|
| /Documentation/driver-api/nfc/ |
| D | nfc-hci.rst | 40 those gates have pipes connected when the hci device is set up.
41 In case the chip supports pre-opened gates and pseudo-static pipes, the driver
44 HCI Gates and Pipes
49 implementation, pipes are totally hidden. The public API only knows gates.
|
| /Documentation/crypto/ |
| D | userspace-if.rst | 350 int pipes[2];
352 pipe(pipes);
354 vmsplice(pipes[1], iov, iovlen, SPLICE_F_GIFT);
356 splice(pipes[0], NULL, opfd, NULL, ret, 0);
|
| /Documentation/core-api/ |
| D | watch_queue.rst | 6 whereby it effectively splices notification messages from the kernel into pipes
28 such pipes due to them wanting to, under some circumstances, revert their
34 insert messages into it. Note that a source may be bound to multiple pipes and
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 28 file system objects (e.g. block devices, pipes, sockets).
|
| /Documentation/devicetree/bindings/media/ |
| D | microchip,csi2dc.yaml | 25 CSI2DC provides two pipes, one video pipe and one data pipe. Video pipe
|
| /Documentation/gpu/amdgpu/ |
| D | thermal.rst | 108 dynamically when there is no workload on gfx or compute pipes. GFXOFF is on by
|
| /Documentation/admin-guide/ |
| D | devices.rst | 135 Sockets and pipes
138 Non-transient sockets and named pipes may exist in /dev. Common entries are:
|
| /Documentation/networking/caif/ |
| D | linux_caif.rst | 20 The Utility Channels are general purpose pipes between modem and host.
|
| /Documentation/mhi/ |
| D | mhi.rst | 76 MHI channels are logical, unidirectional data pipes between a host and a device.
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 69 basically creates the pipes that enable virtualization management
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 144 The ImgU contains two independent pipes, each modelled as a V4L2 sub-device
239 ImgU works based on firmware, currently the ImgU firmware support run 2 pipes
|
| /Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 160 with character device files, pipes, fifos and sockets.
|
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 558 File system objects including files, directories, named pipes, symbolic links,
|
| /Documentation/virt/uml/ |
| D | user_mode_linux_howto_v2.rst | 31 pipes, etc.
|