Home
last modified time | relevance | path

Searched refs:O (Results 1 – 25 of 752) sorted by relevance

12345678910>>...31

/Linux-v4.19/Documentation/s390/
Dvfio-ccw.txt7 Here we describe the vfio support for I/O subchannel devices for
12 I/O access method, which is so called Channel I/O. It has its own access
20 vfio framework. And we add read/write callbacks for special vfio I/O
22 (the real I/O subchannel device) to do further address translation and
23 to perform I/O instructions.
25 This document does not intend to explain the s390 I/O architecture in
27 - A good start to know Channel I/O in general:
28 https://en.wikipedia.org/wiki/Channel_I/O
43 paravirtualized virtio devices via the "Virtio Over Channel I/O
48 use the standard Channel I/O based mechanism, we also need to provide
[all …]
Dcds.txt4 Device Driver I/O Support Routines
15 I/O access method. This gives relief to the device drivers as they don't
18 I/O (PIO), and other hardware features more. However, this implies that
19 either every single device driver needs to implement the hardware I/O
28 In order to build common device support for ESA/390 I/O interfaces, a
29 functional layer was introduced that provides generic I/O access methods to
32 The common device support layer comprises the I/O support routines defined
64 initiate an I/O request.
70 terminate the current I/O request processed on the device.
74 routine whenever an I/O interrupt is presented to the system. The do_IRQ()
[all …]
/Linux-v4.19/block/
DKconfig.iosched10 The no-op I/O scheduler is a minimal scheduler that does basic merging
17 tristate "Deadline I/O scheduler"
20 The deadline I/O scheduler is simple and compact. It will provide
26 tristate "CFQ I/O scheduler"
29 The CFQ I/O scheduler tries to distribute bandwidth equally
34 This is the default I/O scheduler.
45 prompt "Default I/O scheduler"
48 Select the I/O scheduler which will be used by default for all
69 tristate "MQ deadline I/O scheduler"
75 tristate "Kyber I/O scheduler"
[all …]
/Linux-v4.19/Documentation/hwmon/
Dit877 Addresses scanned: from Super I/O config space (8 I/O ports)
11 Addresses scanned: from Super I/O config space (8 I/O ports)
14 Addresses scanned: from Super I/O config space (8 I/O ports)
18 Addresses scanned: from Super I/O config space (8 I/O ports)
22 Addresses scanned: from Super I/O config space (8 I/O ports)
26 Addresses scanned: from Super I/O config space (8 I/O ports)
30 Addresses scanned: from Super I/O config space (8 I/O ports)
34 Addresses scanned: from Super I/O config space (8 I/O ports)
38 Addresses scanned: from Super I/O config space (8 I/O ports)
42 Addresses scanned: from Super I/O config space (8 I/O ports)
[all …]
Dw83627hf7 Addresses scanned: ISA address retrieved from Super I/O registers
10 Addresses scanned: ISA address retrieved from Super I/O registers
13 Addresses scanned: ISA address retrieved from Super I/O registers
16 Addresses scanned: ISA address retrieved from Super I/O registers
19 Addresses scanned: ISA address retrieved from Super I/O registers
42 the Winbond W83627HF, W83627THF, W83697HF and W83637HF Super I/O chips.
47 Super I/O chip and a second i2c-only Winbond chip (often a W83782D),
51 If you really want i2c accesses for these Super I/O chips,
72 be used to force the base I/O address of the hardware monitoring block.
78 # Enter the Super I/O config space
[all …]
Df71882fg7 Addresses scanned: none, address read from Super I/O config space
11 Addresses scanned: none, address read from Super I/O config space
15 Addresses scanned: none, address read from Super I/O config space
19 Addresses scanned: none, address read from Super I/O config space
23 Addresses scanned: none, address read from Super I/O config space
27 Addresses scanned: none, address read from Super I/O config space
31 Addresses scanned: none, address read from Super I/O config space
35 Addresses scanned: none, address read from Super I/O config space
39 Addresses scanned: none, address read from Super I/O config space
43 Addresses scanned: none, address read from Super I/O config space
[all …]
/Linux-v4.19/Documentation/device-mapper/
Ddm-io.txt4 Dm-io provides synchronous and asynchronous I/O services. There are three
5 types of I/O services available, and each type has a sync and an async
9 of the I/O. Each io_region indicates a block-device along with the starting
21 The first I/O service type takes a list of memory pages as the data buffer for
22 the I/O, along with an offset into the first page.
36 The second I/O service type takes an array of bio vectors as the data buffer
37 for the I/O. This service can be handy if the caller has a pre-assembled bio,
47 The third I/O service type takes a pointer to a vmalloc'd memory buffer as the
48 data buffer for the I/O. This service can be handy if the caller needs to do
49 I/O to a large region but doesn't want to allocate a large number of individual
[all …]
/Linux-v4.19/Documentation/driver-api/
Ds390-drivers.rst11 drive s390 based channel attached I/O devices. This includes interfaces
14 I/O layer.
17 with the s390 channel I/O architecture. For a description of this
21 While most I/O devices on a s390 system are typically driven through the
22 channel I/O mechanism described here, there are various other methods
25 The s390 common I/O layer also provides access to some devices that are
26 not strictly considered I/O devices. They are considered here as well,
38 * Standard I/O subchannels, for use by the system. They have a child
40 * I/O subchannels bound to the vfio-ccw driver. See
53 so-called channel attached devices. They are addressed via I/O
[all …]
/Linux-v4.19/Documentation/block/
Dstat.txt24 read merges requests number of read I/Os merged with in-queue I/O
28 write merges requests number of write I/Os merged with in-queue I/O
35 discard merges requests number of discard I/Os merged with in-queue I/O
42 These values increment when an I/O request completes.
47 These values increment when an I/O request is merged with an
48 already-queued I/O request.
56 block size. The counters are incremented when the I/O completes.
61 These values count the number of milliseconds that I/O requests have
62 waited on this block device. If there are multiple I/O requests waiting,
70 This value counts the number of I/O requests that have been issued to
[all …]
/Linux-v4.19/tools/scripts/
DMakefile.include2 ifneq ($(O),)
4 dummy := $(if $(shell test -d $(O) || echo $(O)),$(error O=$(O) does not exist),)
5 ABSOLUTE_O := $(shell cd $(O) ; pwd)
7 COMMAND_O := O=$(ABSOLUTE_O)
9 objtree := $(O)
/Linux-v4.19/Documentation/serial/
Drocket.txt26 The RocketPort ISA board requires I/O ports to be configured by the DIP
30 You pass the I/O port to the driver using the following module parameters:
32 board1 : I/O port for the first ISA board
33 board2 : I/O port for the second ISA board
34 board3 : I/O port for the third ISA board
35 board4 : I/O port for the fourth ISA board
87 You must assign and configure the I/O addresses used by the ISA Rocketport
92 SETTING THE I/O ADDRESS
96 a range of I/O addresses for it to use. The first RocketPort card
97 requires a 68-byte contiguous block of I/O addresses, starting at one
[all …]
/Linux-v4.19/Documentation/media/uapi/v4l/
Dio.rst12 The classic I/O method using the :ref:`read() <func-read>` and
17 Other methods must be negotiated. To select the streaming I/O method
19 :ref:`VIDIOC_REQBUFS` ioctl. The asynchronous I/O
22 Video overlay can be considered another I/O method, although the
27 Generally exactly one I/O method, including overlay, is associated with
35 degree, but for simplicity drivers need not support switching the I/O
39 The following sections describe the various I/O methods in more detail.
Dvidioc-reqbufs.rst12 VIDIOC_REQBUFS - Initiate Memory Mapping, User Pointer I/O or DMA buffer I/O
35 :ref:`user pointer <userp>` or :ref:`DMABUF <dmabuf>` based I/O.
39 ioctl is merely used to switch the driver into user pointer I/O mode and
42 configures the driver into DMABUF I/O mode without performing any direct
49 I/O method and the ``reserved`` array must be zeroed. When the ioctl is
58 When the I/O method is not supported the ioctl returns an ``EINVAL`` error
104 The buffer type (``type`` field) or the requested I/O method
Drw.rst16 to or from user memory, so this I/O method is not necessarily less
21 However this is also the simplest I/O method, requiring little or no
33 must implement one I/O method if they exchange data with applications,
40 supporting all I/O interfaces, but as much as the complex memory
41 mapping I/O can be inadequate for some devices we have no reason to
Dvidioc-prepare-buf.rst12 VIDIOC_PREPARE_BUF - Prepare a buffer for I/O
37 using the :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl, and to prepare it for future I/O. Such
39 in advance saves time during the actual I/O. In case such cache
56 File I/O is in progress.
/Linux-v4.19/arch/powerpc/boot/
DREADME4 objcopy -j .kernel:vmlinux -O binary zImage vmlinux.gz
5 objcopy -j .kernel:System.map -O binary zImage System.map.gz
6 objcopy -j .kernel:.config -O binary zImage config.gz
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
/Linux-v4.19/Documentation/
Dio_ordering.txt2 Ordering I/O writes to memory-mapped addresses
5 On some platforms, so-called memory-mapped I/O is weakly ordered. On such
6 platforms, driver writers are responsible for ensuring that I/O writes to
8 typically done by reading a 'safe' device or bridge register, causing the I/O
12 subsequent writes to I/O space arrived only after all prior writes (much like a
13 memory barrier op, mb(), only with respect to I/O).
49 Here, the reads from safe_register will cause the I/O chipset to flush any
/Linux-v4.19/Documentation/features/scripts/
Dfeatures-refresh.sh13 O=""
16 O="not"
82 if [ "$O" = "" ] && [ ! -z "$K_GREP" ]; then
84 elif [ "$O" = "not" ] && [ -z "$K_GREP" ]; then
/Linux-v4.19/arch/sh/lib64/
Dcopy_user_memcpy.S62 #define LDUAQ(P,O,D0,D1) ldlo.q P,O,D0; ldhi.q P,O+7,D1 argument
63 #define STUAQ(P,O,D0,D1) stlo.q P,O,D0; sthi.q P,O+7,D1 argument
64 #define LDUAL(P,O,D0,D1) ldlo.l P,O,D0; ldhi.l P,O+3,D1 argument
65 #define STUAL(P,O,D0,D1) stlo.l P,O,D0; sthi.l P,O+3,D1 argument
Dmemcpy.S47 #define LDUAQ(P,O,D0,D1) ldlo.q P,O,D0; ldhi.q P,O+7,D1 argument
48 #define STUAQ(P,O,D0,D1) stlo.q P,O,D0; sthi.q P,O+7,D1 argument
49 #define LDUAL(P,O,D0,D1) ldlo.l P,O,D0; ldhi.l P,O+3,D1 argument
50 #define STUAL(P,O,D0,D1) stlo.l P,O,D0; sthi.l P,O+3,D1 argument
/Linux-v4.19/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dpar_io.txt1 * Parallel I/O Ports
3 This node configures Parallel I/O ports for CPUs with QE support.
5 device that using parallel I/O ports, a child node should be created.
12 - num-ports : number of Parallel I/O ports
26 the new device trees. Instead, each Par I/O bank should be represented
/Linux-v4.19/Documentation/media/uapi/dvb/
Ddmx-reqbufs.rst10 DMX_REQBUFS - Initiate Memory Mapping and/or DMA buffer I/O
34 This ioctl is used to initiate a memory mapped or DMABUF based demux I/O.
39 ioctl is merely used to switch the driver into user pointer I/O mode and
42 configures the driver into DMABUF I/O mode without performing any direct
57 When this I/O method is not supported, the ioctl returns an ``EOPNOTSUPP``
74 The the requested I/O method is not supported.
/Linux-v4.19/Documentation/lightnvm/
Dpblk.txt5 block I/O interface. Its primary responsibilities are:
12 - Handle I/O errors.
14 - Maintain consistency across the I/O stack during synchronization points.
/Linux-v4.19/tools/perf/
DMakefile37 ifneq ($(O),)
38 FULL_O := $(shell readlink -f $(O) || echo $(O))
/Linux-v4.19/Documentation/ABI/removed/
Dvideo13946 controller, which were used for isochronous I/O. It was added as an
7 alternative to raw1394's isochronous I/O functionality which had
10 asynchronous I/O for device discovery and configuration.

12345678910>>...31