| /kernel/linux/linux-5.10/drivers/staging/comedi/drivers/tests/ |
| D | ni_routes_test.c | 28 #define O(x) ((x) + NI_NAMES_BASE) macro
48 static const int bad_dest = O(8), dest0 = O(0), desti = O(5);
50 static const int no_val_dest = O(7), no_val_index = 4;
53 #define rgout0_src0 (O(100))
54 #define rgout0_src1 (O(101))
55 #define brd0_src0 (O(110))
56 #define brd0_src1 (O(111))
57 #define brd1_src0 (O(120))
58 #define brd1_src1 (O(121))
59 #define brd2_src0 (O(130))
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | it87.rst | 10 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)
24 Addresses scanned: from Super I/O config space (8 I/O ports)
32 Addresses scanned: from Super I/O config space (8 I/O ports)
40 Addresses scanned: from Super I/O config space (8 I/O ports)
48 Addresses scanned: from Super I/O config space (8 I/O ports)
56 Addresses scanned: from Super I/O config space (8 I/O ports)
64 Addresses scanned: from Super I/O config space (8 I/O ports)
72 Addresses scanned: from Super I/O config space (8 I/O ports)
80 Addresses scanned: from Super I/O config space (8 I/O ports)
[all …]
|
| D | w83627hf.rst | 7 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 …]
|
| D | f71882fg.rst | 10 Addresses scanned: none, address read from Super I/O config space
18 Addresses scanned: none, address read from Super I/O config space
26 Addresses scanned: none, address read from Super I/O config space
34 Addresses scanned: none, address read from Super I/O config space
42 Addresses scanned: none, address read from Super I/O config space
50 Addresses scanned: none, address read from Super I/O config space
58 Addresses scanned: none, address read from Super I/O config space
66 Addresses scanned: none, address read from Super I/O config space
74 Addresses scanned: none, address read from Super I/O config space
82 Addresses scanned: none, address read from Super I/O config space
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-io.rst | 5 Dm-io provides synchronous and asynchronous I/O services. There are three
6 types of I/O services available, and each type has a sync and an async
10 of the I/O. Each io_region indicates a block-device along with the starting
22 The first I/O service type takes a list of memory pages as the data buffer for
23 the I/O, along with an offset into the first page::
37 The second I/O service type takes an array of bio vectors as the data buffer
38 for the I/O. This service can be handy if the caller has a pre-assembled bio,
48 The third I/O service type takes a pointer to a vmalloc'd memory buffer as the
49 data buffer for the I/O. This service can be handy if the caller needs to do
50 I/O to a large region but doesn't want to allocate a large number of individual
[all …]
|
| D | dm-flakey.rst | 40 unreliability, all I/O returns errors.
43 All write I/O is silently ignored.
44 Read I/O is handled correctly.
47 All write I/O is failed with an error signalled.
48 Read I/O is handled correctly.
|
| /kernel/linux/linux-5.10/Documentation/s390/ |
| D | cds.rst | 6 Device Driver I/O Support Routines
19 I/O access method. This gives relief to the device drivers as they don't
22 I/O (PIO), and other hardware features more. However, this implies that
23 either every single device driver needs to implement the hardware I/O
32 In order to build common device support for ESA/390 I/O interfaces, a
33 functional layer was introduced that provides generic I/O access methods to
36 The common device support layer comprises the I/O support routines defined
67 initiate an I/O request.
73 terminate the current I/O request processed on the device.
77 routine whenever an I/O interrupt is presented to the system. The do_IRQ()
[all …]
|
| D | vfio-ccw.rst | 8 Here we describe the vfio support for I/O subchannel devices for
13 I/O access method, which is so called Channel I/O. It has its own access
23 vfio framework. And we add read/write callbacks for special vfio I/O
25 (the real I/O subchannel device) to do further address translation and
26 to perform I/O instructions.
28 This document does not intend to explain the s390 I/O architecture in
31 - A good start to know Channel I/O in general:
32 https://en.wikipedia.org/wiki/Channel_I/O
47 paravirtualized virtio devices via the "Virtio Over Channel I/O
52 use the standard Channel I/O based mechanism, we also need to provide
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | s390-drivers.rst | 11 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 …]
|
| D | io_ordering.rst | 2 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
|
| D | lightnvm-pblk.rst | 5 block I/O interface. Its primary responsibilities are:
12 - Handle I/O errors.
14 - Maintain consistency across the I/O stack during synchronization points.
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | stat.rst | 30 read merges requests number of read I/Os merged with in-queue I/O
34 write merges requests number of write I/Os merged with in-queue I/O
41 discard merges requests number of discard I/Os merged with in-queue I/O
51 These values increment when an I/O request completes.
56 These values increment when an flush I/O request completes.
64 These values increment when an I/O request is merged with an
65 already-queued I/O request.
73 block size. The counters are incremented when the I/O completes.
78 These values count the number of milliseconds that I/O requests have
79 waited on this block device. If there are multiple I/O requests waiting,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/serial/ |
| D | rocket.rst | 28 The RocketPort ISA board requires I/O ports to be configured by the DIP
32 You pass the I/O port to the driver using the following module parameters:
35 I/O port for the first ISA board
37 I/O port for the second ISA board
39 I/O port for the third ISA board
41 I/O port for the fourth ISA board
91 You must assign and configure the I/O addresses used by the ISA Rocketport
96 Setting the I/O address
100 a range of I/O addresses for it to use. The first RocketPort card
101 requires a 68-byte contiguous block of I/O addresses, starting at one
[all …]
|
| /kernel/linux/linux-5.10/tools/scripts/ |
| D | Makefile.include | 2 ifneq ($(O),)
4 dummy := $(if $(shell cd $(PWD); test -d $(O) || echo $(O)),$(error O=$(O) does not exist),)
5 ABSOLUTE_O := $(shell cd $(PWD); cd $(O) ; pwd)
7 COMMAND_O := O=$(ABSOLUTE_O)
9 objtree := $(O)
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/ |
| D | README | 4 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
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | io.rst | 13 The classic I/O method using the :c:func:`read()` and
18 Other methods must be negotiated. To select the streaming I/O method
20 :ref:`VIDIOC_REQBUFS` ioctl. The asynchronous I/O
23 Video overlay can be considered another I/O method, although the
28 Generally exactly one I/O method, including overlay, is associated with
36 degree, but for simplicity drivers need not support switching the I/O
40 The following sections describe the various I/O methods in more detail.
|
| D | vidioc-prepare-buf.rst | 13 VIDIOC_PREPARE_BUF - Prepare a buffer for I/O
36 using the :ref:`VIDIOC_QBUF <VIDIOC_QBUF>` ioctl, and to prepare it for future I/O. Such
38 in advance saves time during the actual I/O.
51 File I/O is in progress.
|
| D | rw.rst | 17 to or from user memory, so this I/O method is not necessarily less
22 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
|
| /kernel/linux/linux-5.10/Documentation/features/scripts/ |
| D | features-refresh.sh | 13 O=""
16 O="not"
82 if [ "$O" = "" ] && [ ! -z "$K_GREP" ]; then
84 elif [ "$O" = "not" ] && [ -z "$K_GREP" ]; then
|
| /kernel/linux/linux-5.10/block/ |
| D | Kconfig.iosched | 7 tristate "MQ deadline I/O scheduler"
13 tristate "Kyber I/O scheduler"
16 The Kyber I/O scheduler is a low-overhead scheduler suitable for
22 tristate "BFQ I/O scheduler"
24 BFQ I/O scheduler for BLK-MQ. BFQ distributes the bandwidth of
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | par_io.txt | 1 * 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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/ |
| D | test_bpftool_build.sh | 117 make_with_tmpdir tools/bpf O
130 make_with_tmpdir -C tools/bpf/bpftool O
155 make_with_tmpdir bpf O
164 make_with_tmpdir O
|
| /kernel/linux/linux-5.10/drivers/iio/buffer/ |
| D | Kconfig | 3 # Industrial I/O generic buffer implementations
14 tristate "Industrial I/O DMA buffer infrastructure"
23 tristate "Industrial I/O DMA buffer integration with DMAEngine"
34 tristate "Industrial I/O HW buffering"
44 tristate "Industrial I/O buffering based on kfifo"
51 tristate "Industrial I/O triggered buffer support"
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | dmx-reqbufs.rst | 13 DMX_REQBUFS - Initiate Memory Mapping and/or DMA buffer I/O
36 This ioctl is used to initiate a memory mapped or DMABUF based demux I/O.
41 ioctl is merely used to switch the driver into user pointer I/O mode and
44 configures the driver into DMABUF I/O mode without performing any direct
59 When this I/O method is not supported, the ioctl returns an ``EOPNOTSUPP``
75 The the requested I/O method is not supported.
|
| /kernel/linux/linux-5.10/tools/perf/ |
| D | Makefile | 37 ifneq ($(O),)
38 FULL_O := $(shell cd $(PWD); readlink -f $(O) || echo $(O))
|