Searched +full:co +full:- +full:located (Results 1 – 12 of 12) sorted by relevance
| /Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _yuv-formats: 33 - `4:4:4`: No subsampling 34 - `4:2:2`: Horizontal subsampling by 2, no vertical subsampling 35 - `4:2:0`: Horizontal subsampling by 2, vertical subsampling by 2 36 - `4:1:1`: Horizontal subsampling by 4, no vertical subsampling 37 - `4:1:0`: Horizontal subsampling by 4, vertical subsampling by 4 40 located in different spatial locations: 42 - .. _yuv-chroma-centered: 49 - .. _yuv-chroma-cosited: [all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | nixge.txt | 4 - compatible: Should be "ni,xge-enet-3.00", but can be "ni,xge-enet-2.00" for 5 older device trees with DMA engines co-located in the address map, 7 - reg: Address and length of the register set for the device. It contains the 8 information of registers in the same order as described by reg-names. 9 - reg-names: Should contain the reg names 12 - interrupts: Should contain tx and rx interrupt 13 - interrupt-names: Should be "rx" and "tx" 14 - phy-mode: See ethernet.txt file in the same directory. 15 - nvmem-cells: Phandle of nvmem cell containing the MAC address 16 - nvmem-cell-names: Should be "address" [all …]
|
| /Documentation/filesystems/ |
| D | virtiofs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 virtiofs: virtio-fs host<->guest shared file system 9 - Copyright (C) 2019 Red Hat, Inc. 14 VIRTIO "virtio-fs" device for guest<->host file system sharing. It allows a 19 booting from a root file system located on the host, persistent storage for 24 expose the storage network to the guest. The virtio-fs device was designed to 27 Furthermore the virtio-fs device takes advantage of the co-location of the 35 .. code-block:: sh 37 guest# mount -t virtiofs myfs /mnt 39 Please see https://virtio-fs.gitlab.io/ for details on how to configure QEMU [all …]
|
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 26 But unlike the LOCALIO protocol, the sockaddr-based matching didn't 42 - With LOCALIO: 48 - Without LOCALIO: 55 - With LOCALIO: 61 - Without LOCALIO: 93 deciding if the NFS client and server are co-located on the same 103 in shared kernel memory if they are truly co-located. 115 onus on the server to somehow discover that the client is co-located 122 6. Why is having the client perform a server-side file OPEN, without 131 client perform a server-side file open, without using RPC, is ideal. [all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,imsics.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/riscv,imsics.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: RISC-V Incoming MSI Controller (IMSIC) 10 - Anup Patel <anup@brainfault.org> 13 The RISC-V advanced interrupt architecture (AIA) defines a per-CPU incoming 14 MSI controller (IMSIC) for handling MSIs in a RISC-V platform. The RISC-V 15 AIA specification can be found at https://github.com/riscv/riscv-aia. 17 The IMSIC is a per-CPU (or per-HART) device with separate interrupt file [all …]
|
| /Documentation/admin-guide/media/ |
| D | fimc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 Copyright |copy| 2012 - 2013 Samsung Electronics Co., Ltd. 16 availability, LCD writeback support, etc. The driver is located at 17 drivers/media/platform/samsung/exynos4-is directory. 20 -------------- 22 S5PC100 (mem-to-mem only), S5PV210, Exynos4210 25 ------------------ 27 - camera parallel interface capture (ITU-R.BT601/565); 28 - camera serial interface capture (MIPI-CSI2); 29 - memory-to-memory processing (color space conversion, scaling, mirror [all …]
|
| /Documentation/power/ |
| D | opp.rst | 5 (C) 2009-2010 Nishanth Menon <nm@ti.com>, Texas Instruments Incorporated 20 ------------------------------------------------- 22 Complex SoCs of today consists of a multiple sub-modules working in conjunction. 25 facilitate this, sub-modules in a SoC are grouped into domains, allowing some 41 - {300000000, 1000000} 42 - {800000000, 1200000} 43 - {1000000000, 1300000} 46 ---------------------------------------- 49 information. The library is located in drivers/opp/ directory and the header 50 is located in include/linux/pm_opp.h. OPP library can be enabled by enabling [all …]
|
| /Documentation/arch/s390/ |
| D | vfio-ccw.rst | 2 vfio-ccw: the basic infrastructure 6 ------------ 9 Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a 16 - Channel programs run asynchronously on a separate (co)processor. 17 - The channel subsystem will access any memory designated by the caller 31 - A good start to know Channel I/O in general: 33 - s390 architecture: 34 s390 Principles of Operation manual (IBM Form. No. SA22-7832) 35 - The existing QEMU code which implements a simple emulated channel 41 - Documentation/driver-api/vfio-mediated-device.rst [all …]
|
| /Documentation/hid/ |
| D | intel-ish-hid.rst | 6 processing to a dedicated low power co-processor. This allows the core 11 Sensor usage tables. These may be found in tablets, 2-in-1 convertible laptops 27 ----------------- ---------------------- 28 | USB HID | --> | ISH HID | 29 ----------------- ---------------------- 30 ----------------- ---------------------- 31 | USB protocol | --> | ISH Transport | 32 ----------------- ---------------------- 33 ----------------- ---------------------- 34 | EHCI/XHCI | --> | ISH IPC | [all …]
|
| /Documentation/driver-api/media/drivers/ |
| D | cx2341x-devel.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 ----------------------- 12 .. note:: the memory long words are little-endian ('intel format'). 21 .. code-block:: none 23 ivtvctl -O min=0x02000000,max=0x020000ff 26 register space :-). 35 .. code-block:: none 37 0x00000000-0x00ffffff Encoder memory space 38 0x00000000-0x0003ffff Encode.rom 39 ???-??? MPEG buffer(s) [all …]
|
| /Documentation/scsi/ |
| D | ncr53c8xx.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 95170 DEUIL LA BARRE - FRANCE 64 10.4 PCI configuration fix-up boot option 81 16.1 Synchronous timings for 53C875 and 53C860 Ultra-SCSI controllers 82 16.2 Synchronous timings for fast SCSI-2 53C8XX controllers 97 - Gerard Roudier <groudier@free.fr> 101 - Wolfgang Stanglmeier <wolf@cologne.de> 102 - Stefan Esser <se@mi.Uni-Koeln.de> 106 - ncr53c8xx generic driver that supports all the SYM53C8XX family including 109 - sym53c8xx enhanced driver (a.k.a. 896 drivers) that drops support of oldest [all …]
|
| /Documentation/sound/kernel-api/ |
| D | writing-an-alsa-driver.rst | 11 Architecture) <http://www.alsa-project.org/>`__ driver. The document 19 low-level driver implementation details. It only describes the standard 26 ------- 56 -------------- 60 sub-directories contain different modules and are dependent upon the 74 This directory and its sub-directories are for the ALSA sequencer. This 76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when 85 ----------------- 88 to be exported to user-space, or included by several files in different 94 ----------------- [all …]
|