| /Documentation/devicetree/bindings/arm/ |
| D | fsl.yaml | 7 title: Freescale i.MX Platforms Device Tree Bindings
18 - description: i.MX1 based Boards
25 - description: i.MX23 based Boards
32 - description: i.MX25 Product Development Kit
38 - description: i.MX27 Product Development Kit
46 - description: i.MX28 based Boards
56 - description: i.MX28 Duckbill 2 based Boards
65 - description: i.MX31 based Boards
72 - description: i.MX35 based Boards
78 - description: i.MX35 Eukrea CPUIMX35 Board
[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 …]
|
| D | biodoc.rst | 18 September 2003: Updated I/O Scheduler portions
59 - Highmem I/O support
60 - I/O scheduler modularization
66 2. New flexible and generic but minimalist i/o structure or descriptor
67 (instead of using buffer heads at the i/o layer)
76 3.2.3 I/O completion
79 3.3 I/O submission
80 4. The I/O scheduler
105 capabilities to the maximum extent for better i/o performance. This is
113 Sophisticated devices with large built-in caches, intelligent i/o scheduling
[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/devicetree/bindings/nvmem/ |
| D | imx-ocotp.yaml | 7 title: Freescale i.MX6 On-Chip OTP Controller (OCOTP) device tree bindings
14 i.MX6Q/D, i.MX6DL/S, i.MX6SL, i.MX6SX, i.MX6UL, i.MX6ULL/ULZ, i.MX6SLL,
15 i.MX7D/S, i.MX7ULP, i.MX8MQ, i.MX8MM, i.MX8MN and i.MX8MP SoCs.
39 # i.MX8MP not really compatible with fsl,imx8mm-ocotp, however
|
| D | imx-iim.yaml | 7 title: Freescale i.MX IC Identification Module (IIM) device tree bindings
14 i.MX25, i.MX27, i.MX31, i.MX35, i.MX51 and i.MX53 SoCs.
|
| /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-pcu20be.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[19:12]`
37 - I'\ :sub:`0[11:4]`
38 - I'\ :sub:`0[3:0]; B2[3:0]=pad`
41 - I'\ :sub:`1[19:12]`
42 - I'\ :sub:`1[11:4]`
43 - I'\ :sub:`1[3:0]; B2[3:0]=pad`
|
| 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/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/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/filesystems/ext4/ |
| D | eainode.rst | 11 inode's i\_atime field is used to store a checksum of the xattr value;
12 and i\_ctime/i\_version store a 64-bit reference count, which enables
15 i\_mtime/i\_generation *may* store a back-reference to the inode number
16 and i\_generation of the **one** owning inode (in cases where the EA
|
| /Documentation/translations/it_IT/process/ |
| D | license-rules.rst | 13 Il kernel Linux viene rilasciato sotto i termini definiti dalla seconda
24 loro interezza, quindi i singoli file sorgenti possono avere diverse licenze ma
34 A parte questo, i singolo file possono essere forniti con una doppia licenza,
38 I file d'intestazione per l'API verso lo spazio utente (UAPI) descrivono
41 confine oltre il quale non si estendono i requisiti della GPL per quei
42 programmi che le usano per comunicare con il kernel. Dato che i file
59 concordati fra i soci nell'industria, gli sviluppatori di strumenti, e i
63 Il kernel Linux richiede un preciso identificatore SPDX in tutti i file
92 .dts{i}: // SPDX-License-Identifier: <SPDX License Expression>
95 principale per i commenti, allora dev'essere usato il meccanismo accettato
[all …]
|
| /Documentation/powerpc/ |
| D | mpc52xx.rst | 31 DBug> dn -i zImage.initrd.lite5200
37 is not supported, and I'm not sure anyone is interesting in working on it
38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
39 nothing to do with the MPC5200. I also included the 'MPC' for the same
41 - Of course, I inspired myself from the 2.4 port. If you think I forgot to
42 mention you/your company in the copyright of some code, I'll correct it
|