| /Documentation/devicetree/bindings/arm/ |
| D | fsl.yaml | 7 title: Freescale i.MX Platforms
17 - description: i.MX1 based Boards
24 - description: i.MX23 based Boards
34 - description: i.MX25 Product Development Kit
41 - description: i.MX25 Eukrea CPUIMX25 Boards
48 - description: i.MX25 Eukrea MBIMXSD25 Boards
58 - description: i.MX27 based Boards
65 - description: i.MX27 APF27 SoM Board
71 - description: i.MX27 Eukrea CPUIMX27 SoM Board
77 - description: i.MX27 Phytec pca100 Board
[all …]
|
| /Documentation/virt/acrn/ |
| D | io-request.rst | 3 I/O request handling
6 An I/O request of a User VM, which is constructed by the hypervisor, is
7 distributed by the ACRN Hypervisor Service Module to an I/O client
8 corresponding to the address range of the I/O request. Details of I/O request
11 1. I/O request
14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
15 communication between the hypervisor and Service VM. An I/O request is a
17 an I/O handler of the hypervisor when a trapped I/O access happens in a User
20 used as an array of 16 I/O request slots with each I/O request slot being 256
23 2. I/O clients
[all …]
|
| /Documentation/block/ |
| D | stat.rst | 29 read I/Os requests number of read I/Os processed
30 read merges requests number of read I/Os merged with in-queue I/O
33 write I/Os requests number of write I/Os processed
34 write merges requests number of write I/Os merged with in-queue I/O
37 in_flight requests number of I/Os currently in flight
40 discard I/Os requests number of discard I/Os processed
41 discard merges requests number of discard I/Os merged with in-queue I/O
44 flush I/Os requests number of flush I/Os processed
48 read I/Os, write I/Os, discard I/0s
51 These values increment when an I/O request completes.
[all …]
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | imx-ocotp.yaml | 7 title: Freescale i.MX On-Chip OTP Controller (OCOTP)
16 i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL, i.MX6ULL/ULZ, i.MX6SLL,
17 i.MX7D/S, i.MX7ULP, i.MX8MQ, i.MX8MM, i.MX8MN i.MX8MP and i.MX93/5 SoCs.
44 # i.MX8MP not really compatible with fsl,imx8mm-ocotp, however
|
| D | imx-iim.yaml | 7 title: Freescale i.MX IC Identification Module (IIM)
16 i.MX25, i.MX27, i.MX31, i.MX35, i.MX51 and i.MX53 SoCs.
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 118 not be separately listed. For example, `ptp_tx[i]_packets` will not be
119 explicitly documented since `tx[i]_packets` describes the behavior of both
120 counters, except `ptp_tx[i]_packets` is only counted when precision time
129 standard counters which counts it (i.e. accelerated traffic is counted twice).
132 notation for ring counters includes the [i] index without the braces. The
133 notation for port counters doesn't include the [i]. A counter name
134 `rx[i]_packets` will be printed as `rx0_packets` for ring 0 and `rx_packets` for
144 * - `rx[i]_packets`
145 - The number of packets received on ring i.
148 * - `rx[i]_bytes`
[all …]
|
| /Documentation/scheduler/ |
| D | sched-pelt.c | 20 int i; in calc_runnable_avg_yN_inv() local
25 for (i = 0; i < HALFLIFE; i++) { in calc_runnable_avg_yN_inv()
26 x = ((1UL<<32)-1)*pow(y, i); in calc_runnable_avg_yN_inv()
28 if (i % 6 == 0) printf("\n\t"); in calc_runnable_avg_yN_inv()
38 int i; in calc_runnable_avg_yN_sum() local
41 for (i = 1; i <= HALFLIFE; i++) { in calc_runnable_avg_yN_sum()
42 if (i == 1) in calc_runnable_avg_yN_sum()
47 if (i % 11 == 0) in calc_runnable_avg_yN_sum()
84 int i, x = sum; in calc_accumulated_sum_32() local
87 for (i = 1; i <= n/HALFLIFE+1; i++) { in calc_accumulated_sum_32()
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | winucase_convert.pl | 31 for ($i = 0; $i < 256; $i++) {
32 next if (!$top[$i]);
34 printf("static const wchar_t t2_%2.2x[256] = {", $i);
41 printf("0x%4.4x,", $top[$i][$j] ? $top[$i][$j] : 0);
46 printf("static const wchar_t *const toplevel[256] = {", $i);
47 for ($i = 0; $i < 256; $i++) {
48 if (($i % 8) == 0) {
50 } elsif ($top[$i]) {
56 if ($top[$i]) {
57 printf("t2_%2.2x,", $i);
|
| /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 …]
|
| /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 | striped.rst | 5 Device-Mapper's "striped" target is used to create a striped (i.e. RAID-0)
8 potentially provide improved I/O throughput by utilizing several physical
40 my ($min_dev_size, $stripe_dev_size, $i);
47 for ($i = 1; $i < $num_devs; $i++) {
48 my $this_size = `blockdev --getsz $devs[$i]`;
57 for ($i = 0; $i < $num_devs; $i++) {
58 $table .= " $devs[$i] 0";
|
| D | unstriped.rst | 55 for i in $(seq 0 ${SEQ_END}); do
56 dd if=/dev/zero of=member-${i} bs=${MEMBER_SIZE} count=1 oflag=direct
57 losetup /dev/loop${i} member-${i}
58 DM_PARMS+=" /dev/loop${i} 0"
62 for i in $(seq 0 ${SEQ_END}); do
63 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i}
66 for i in $(seq 0 ${SEQ_END}); do
67 dd if=/dev/urandom of=/dev/mapper/set-${i} bs=${BS} count=${COUNT} oflag=direct
68 diff /dev/mapper/set-${i} member-${i}
71 for i in $(seq 0 ${SEQ_END}); do
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-indexed.rst | 40 - i\ :sub:`7`
41 - i\ :sub:`6`
42 - i\ :sub:`5`
43 - i\ :sub:`4`
44 - i\ :sub:`3`
45 - i\ :sub:`2`
46 - i\ :sub:`1`
47 - i\ :sub:`0`
|
| D | mmap.rst | 7 Streaming I/O (Memory Mapping)
10 Input and output devices support this I/O method when the
18 Streaming is an I/O method where only pointers to buffers are exchanged
23 the most efficient I/O method available for a long time, many other
66 unsigned int i;
93 for (i = 0; i < reqbuf.count; i++) {
99 buffer.index = i;
106 buffers[i].length = buffer.length; /* remember for munmap() */
108 buffers[i].start = mmap(NULL, buffer.length,
113 if (MAP_FAILED == buffers[i].start) {
[all …]
|
| D | pixfmt-sdr-pcu18be.rst | 15 number consist of two parts called In-phase and Quadrature (IQ). Both I
18 padded with 0. I value starts first and Q value starts at an offset
19 equalling half of the buffer size (i.e.) offset = buffersize/2. Out of
36 - I'\ :sub:`0[17:10]`
37 - I'\ :sub:`0[9:2]`
38 - I'\ :sub:`0[1:0]; B2[5:0]=pad`
41 - I'\ :sub:`1[17:10]`
42 - I'\ :sub:`1[9:2]`
43 - I'\ :sub:`1[1:0]; B2[5:0]=pad`
|
| /Documentation/fb/ |
| D | cmap_xfbdev.rst | 19 for (i = 0; i < 8; i++)
20 info->cmap.red[i] = (((2*i)+1)*(0xFFFF))/16;
26 for (i=0; i < 8; i++) {
29 sprintf(colorspec, "rgb:%x/%x/%x", i*36,i*36,i*36);
33 grays[i] = wantedColor;
|
| /Documentation/usb/ |
| D | gadget_hid.rst | 10 and HID reports can be sent/received through I/O on the
106 For example type: g i s t r --left-shift
197 int i = 0;
210 for (i = 0; kval[i].opt != NULL; i++)
211 if (strcmp(tok, kval[i].opt) == 0) {
212 report[2 + key++] = kval[i].val;
215 if (kval[i].opt != NULL)
225 for (i = 0; kmod[i].opt != NULL; i++)
226 if (strcmp(tok, kmod[i].opt) == 0) {
227 report[0] = report[0] | kmod[i].val;
[all …]
|
| D | usbdevfs-drop-permissions.c | 44 int i, res; in claim_some_intf() local
46 for (i = 0; i < 4; i++) { in claim_some_intf()
47 res = ioctl(fd, USBDEVFS_CLAIMINTERFACE, &i); in claim_some_intf()
49 printf("OK: claimed if %d\n", i); in claim_some_intf()
52 i, -res, strerror(-res)); in claim_some_intf()
79 * free interfaces (i.e., those not used by kernel drivers) in main()
88 "Which option shall I run?: "); in main()
106 printf("I don't recognize that\n"); in main()
109 printf("Which test shall I run next?: "); in main()
|
| /Documentation/driver-api/mtd/ |
| D | nand_ecc.rst | 9 I felt there was room for optimisation. I bashed the code for a few hours
12 Still I was not too happy as I felt there was additional room for improvement.
14 Bad! I was hooked.
15 I decided to annotate my steps in this file. Perhaps it is useful to someone
26 This is done by means of a Hamming code. I'll try to explain it in
27 laymans terms (and apologies to all the pro's in the field in case I do
29 years ago, and I must admit it was not one of my favourites).
31 As I said before the ecc calculation is performed on sectors of 256
88 The story now becomes quite boring. I guess you get the idea.
112 I detected after writing this that ST application note AN1823
[all …]
|
| /Documentation/arch/s390/ |
| 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
18 in the channel program directly, i.e. there is no iommu involved.
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:
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 …]
|
| /Documentation/translations/it_IT/process/ |
| D | botching-up-ioctls.rst | 32 Prima i prerequisiti. Seguite i seguenti suggerimenti se non volete fallire in
35 * Usate solamente interi a lunghezza fissa. Per evitare i conflitti coi tipi
40 esplicitamente i vuoti. Non necessariamente le piattaforme a 32-bit allineano
41 i valori a 64-bit rispettandone l'allineamento, ma le piattaforme a 64-bit lo
42 fanno. Dunque, per farlo correttamente in entrambe i casi dobbiamo sempre
43 riempire i vuoti.
51 * I puntatori sono di tipo ``__u64``, con un *cast* da/a ``uintptr_t`` da lato
79 su un kernel vecchio non noterebbe che i campi nuovi alla fine della struttura
83 * Verificate tutti i campi e *flag* inutilizzati ed i riempimenti siano a 0,
88 quella di contenere spazzatura. Per questo dovrete esplicitamente riempire i
[all …]
|
| /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 …]
|
| /Documentation/translations/zh_CN/admin-guide/ |
| D | cpu-load.rst | 68 int i;
79 for (i = 0; i < HIST; ++i) v[i] = ULONG_MAX - hog (ULONG_MAX);
80 for (i = 0; i < HIST; ++i) tmp += v[i];
89 sigwait (&set, &i);
|
| /Documentation/translations/zh_TW/admin-guide/ |
| D | cpu-load.rst | 74 int i;
85 for (i = 0; i < HIST; ++i) v[i] = ULONG_MAX - hog (ULONG_MAX);
86 for (i = 0; i < HIST; ++i) tmp += v[i];
95 sigwait (&set, &i);
|
| /Documentation/translations/it_IT/locking/ |
| D | locktypes.rst | 30 I blocchi ad attesa con sospensione possono essere acquisiti solo in un contesti
36 di queste primitive. Insomma, non usate i blocchi ad attesa con sospensioni in
48 Nei kernel con PREEMPT_RT, i seguenti blocchi sono convertiti in blocchi ad
72 Nei kernel non-PREEMPT_RT, i seguenti blocchi sono ad attesa attiva:
77 Implicitamente, i blocchi ad attesa attiva disabilitano la prelazione e le
90 Eccetto i semafori, i sopracitati tipi di blocchi hanno tutti una semantica
95 I semafori rw_semaphores hanno un'interfaccia speciale che permette anche ai non
96 proprietari del blocco di rilasciarlo per i lettori.
101 I blocchi a mutua esclusione RT (*rtmutex*) sono un sistema a mutua esclusione
109 PREEMPT_RT. Tuttavia, i kernel PREEMPT_RT eseguono la maggior parte delle
[all …]
|