Home
last modified time | relevance | path

Searched refs:O (Results 1 – 200 of 580) sorted by relevance

123

/linux-4.1.27/tools/scripts/
DMakefile.include1 ifneq ($(O),)
3 dummy := $(if $(shell test -d $(O) || echo $(O)),$(error O=$(O) does not exist),)
4 ABSOLUTE_O := $(shell cd $(O) ; pwd)
6 COMMAND_O := O=$(ABSOLUTE_O)
8 objtree := $(O)
/linux-4.1.27/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 …]
Dswitch.txt5 arbitrary mapping of fixed-size regions of I/O across a fixed set of
9 It maps I/O to underlying block devices efficiently when there is a large
27 stored on another member the I/O will be forwarded as required. This
37 robin algorithm to send I/O across all paths and let the storage array
50 Upper Tier - Determine which array member the I/O should be sent to.
61 a bitmap to look up the location of the I/O and choose the appropriate
62 lower tier device to route the I/O. By using a bitmap we are able to
74 The number of paths across which to distribute the I/O.
Ddm-flakey.txt30 unreliability, all I/O returns errors.
33 All write I/O is silently ignored.
34 Read I/O is handled correctly.
Dcache-policies.txt58 since spindles tend to have good sequential I/O bandwidth. The
59 io_tracker counts contiguous I/Os to try to spot when the I/O is in one
62 If sequential threshold is set to 0 the sequential I/O detection is
63 disabled and sequential I/O will no longer implicitly bypass the cache.
64 Setting the random threshold to 0 does _not_ disable the random I/O
Ddm-service-time.txt6 the incoming I/O.
39 dm-service-time adds the I/O size to 'in-flight-size' when the I/O is
Ddm-queue-length.txt23 dm-queue-length increments/decrements 'in-flight' when an I/O is
Dstriped.txt7 potentially provide improved I/O throughput by utilizing several physical
/linux-4.1.27/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)
15 Addresses scanned: from Super I/O config space (8 I/O ports)
19 Addresses scanned: from Super I/O config space (8 I/O ports)
23 Addresses scanned: from Super I/O config space (8 I/O ports)
27 Addresses scanned: from Super I/O config space (8 I/O ports)
31 Addresses scanned: from Super I/O config space (8 I/O ports)
35 Addresses scanned: from Super I/O config space (8 I/O ports)
39 Addresses scanned: from Super I/O config space (8 I/O ports)
43 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 …]
Dsmsc47m17 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
33 The Standard Microsystems Corporation (SMSC) 47M1xx Super I/O chips
Dw83627ehf7 Addresses scanned: ISA address retrieved from Super I/O registers
11 Addresses scanned: ISA address retrieved from Super I/O registers
15 Addresses scanned: ISA address retrieved from Super I/O registers
19 Addresses scanned: ISA address retrieved from Super I/O registers
23 Addresses scanned: ISA address retrieved from Super I/O registers
27 Addresses scanned: ISA address retrieved from Super I/O registers
31 Addresses scanned: ISA address retrieved from Super I/O registers
35 Addresses scanned: ISA address retrieved from Super I/O registers
50 (NCT6775F), and NCT6776F super I/O chips. We will refer to them collectively
Dsch56277 Addresses scanned: none, address read from Super I/O config space
16 SMSC SCH5627 Super I/O chips include complete hardware monitoring
Dnct677513 Addresses scanned: ISA address retrieved from Super I/O registers
17 Addresses scanned: ISA address retrieved from Super I/O registers
21 Addresses scanned: ISA address retrieved from Super I/O registers
25 Addresses scanned: ISA address retrieved from Super I/O registers
29 Addresses scanned: ISA address retrieved from Super I/O registers
33 Addresses scanned: ISA address retrieved from Super I/O registers
43 and compatible super I/O chips.
Dsch56367 Addresses scanned: none, address read from Super I/O config space
15 SMSC SCH5636 Super I/O chips include an embedded microcontroller for
Df71805f7 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
34 The Fintek F71805F/FG Super I/O chip includes complete hardware monitoring
41 The Fintek F71872F/FG Super I/O chip is almost the same, with two
45 The Fintek F71806F/FG Super-I/O chip is essentially the same as the
Dpc874277 Addresses scanned: none, address read from Super I/O config space
19 The National Semiconductor Super I/O chip includes complete hardware
Dpc873607 Addresses scanned: none, address read from Super I/O config space
37 The National Semiconductor PC87360 Super I/O chip contains monitoring and
41 The National Semiconductor PC87365 and PC87366 Super I/O chips are complete
55 standard Super I/O addresses is used (0x2E/0x2F or 0x4E/0x4F)
Dlm787 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports)
12 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports)
Dnct790442 pwm[1-4] R/O in SmartFan mode, R/W in manual control mode
/linux-4.1.27/Documentation/s390/
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 …]
DCommonIO1 S/390 common I/O-Layer - command line parameters, procfs and debugfs entries
15 The given devices will be ignored by the common I/O-layer; no detection
30 operator). The '!' operator will cause the I/O-layer to _not_ ignore a device.
49 Lists the ranges of devices (by bus id) which are ignored by common I/O.
115 Various debug messages from the common I/O-layer.
118 Logs the calling of functions in the common I/O-layer and, if applicable,
D00-INDEX8 - s390 common device support (common I/O layer).
10 - common I/O layer command line parameters, procfs and debugfs entries
Ddriver-model.txt24 device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O
141 set_online: This function is called by the common I/O layer when the device is
151 set_offline: This function is called by the common I/O layer when the device is
161 notify: This function is called by the common I/O layer for some state changes
170 common I/O layer performs some sanity checks on device number and
/linux-4.1.27/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
38 These values increment when an I/O request completes.
43 These values increment when an I/O request is merged with an
44 already-queued I/O request.
52 counters are incremented when the I/O completes.
57 These values count the number of milliseconds that I/O requests have
58 waited on this block device. If there are multiple I/O requests waiting,
66 This value counts the number of I/O requests that have been issued to
67 the device driver but have not yet completed. It does not include I/O
[all …]
Ddata-integrity.txt14 support for appending integrity metadata to an I/O. The integrity
18 for some protection schemes also that the I/O is written to the right
24 between adjacent nodes in the I/O path. The interesting thing about
26 is well defined and every node in the I/O path can verify the
27 integrity of the I/O and reject it if corruption is detected. This
70 match up for an I/O to complete.
105 that's attached to the I/O.
108 generate the protection information for any I/O. Eventually the
110 user data. Metadata and other I/O that originates within the kernel
174 in case of a WRITE. A READ request will cause the I/O integrity
[all …]
Dwriteback_cache_control.txt9 write back caches. That means the devices signal I/O completion to the
25 has been flushed before the actual I/O operation is started. This explicitly
29 flush without any dependent I/O. It is recommend to use
37 filesystem and will make sure that I/O completion for this request is only
Dbiodoc.txt9 September 2003: Updated I/O Scheduler portions
48 - Highmem I/O support
49 - I/O scheduler modularization
65 3.2.3 I/O completion
69 3.3 I/O submission
70 4. The I/O scheduler
130 Enable I/O to highmem pages, dma_address being the
235 I/O scheduler wrappers are to be used instead of accessing the queue directly.
236 See section 4. The I/O scheduler for details.
429 * main unit of I/O for the block layer and lower layers (ie drivers)
[all …]
Drequest.txt23 I I/O scheduler member
38 void *elevator_private I I/O scheduler private data
D00-INDEX26 - Switching I/O schedulers at runtime
Dcfq-iosched.txt5 I/O bandwidth for all the processes which requests an I/O operation.
7 CFQ maintains the per process queue for the processes which request I/O
10 process's I/O priority.
101 time for each process to issue I/O request before the cfq queue is switched.
143 performance although this can cause the latency of some I/O to increase due
/linux-4.1.27/block/
DKconfig.iosched9 The no-op I/O scheduler is a minimal scheduler that does basic merging
16 tristate "Deadline I/O scheduler"
19 The deadline I/O scheduler is simple and compact. It will provide
25 tristate "CFQ I/O scheduler"
28 The CFQ I/O scheduler tries to distribute bandwidth equally
33 This is the default I/O scheduler.
43 prompt "Default I/O scheduler"
46 Select the I/O scheduler which will be used by default for all
/linux-4.1.27/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-4.1.27/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-4.1.27/Documentation/devicetree/bindings/powerpc/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
Dpincfg.txt14 3 = The pin is I/O
/linux-4.1.27/arch/sh/lib64/
Dmemcpy.S46 #define LDUAQ(P,O,D0,D1) ldlo.q P,O,D0; ldhi.q P,O+7,D1 argument
47 #define STUAQ(P,O,D0,D1) stlo.q P,O,D0; sthi.q P,O+7,D1 argument
48 #define LDUAL(P,O,D0,D1) ldlo.l P,O,D0; ldhi.l P,O+3,D1 argument
49 #define STUAL(P,O,D0,D1) stlo.l P,O,D0; sthi.l P,O+3,D1 argument
Dcopy_user_memcpy.S61 #define LDUAQ(P,O,D0,D1) ldlo.q P,O,D0; ldhi.q P,O+7,D1 argument
62 #define STUAQ(P,O,D0,D1) stlo.q P,O,D0; sthi.q P,O+7,D1 argument
63 #define LDUAL(P,O,D0,D1) ldlo.l P,O,D0; ldhi.l P,O+3,D1 argument
64 #define STUAL(P,O,D0,D1) stlo.l P,O,D0; sthi.l P,O+3,D1 argument
/linux-4.1.27/Documentation/
Dio_ordering.txt1 On some platforms, so-called memory-mapped I/O is weakly ordered. On such
2 platforms, driver writers are responsible for ensuring that I/O writes to
4 typically done by reading a 'safe' device or bridge register, causing the I/O
8 subsequent writes to I/O space arrived only after all prior writes (much like a
9 memory barrier op, mb(), only with respect to I/O).
45 Here, the reads from safe_register will cause the I/O chipset to flush any
Diostats.txt1 I/O statistics fields
66 as only one I/O. This field lets you know how often this was done.
87 This field is incremented at each I/O start, I/O completion, I/O
89 (field 9) times the number of milliseconds spent doing I/O since the
91 I/O completion time and the backlog that may be accumulating.
109 There were significant changes between 2.4 and 2.6 in the I/O subsystem.
Dvolatile-considered-harmful.txt49 The volatile storage class was originally meant for memory-mapped I/O
52 accesses within a critical section. But, within the kernel, I/O memory
53 accesses are always done through accessor functions; accessing I/O memory
74 architectures where direct I/O memory access does work. Essentially,
90 by I/O devices can, sometimes, legitimately be volatile. A ring buffer
Deisa.txt22 allocates I/O resources, allows fancy naming through sysfs, and
29 an I/O region on x86, to the rather more complex, like the hppa
61 res : root device I/O resource
135 res : set of four 256 bytes I/O regions allocated to this device
Dkernel-docs.txt71 Description: O'Reilly's popular book, now also on-line under the
73 Notes: You can also buy it in paper-form from O'Reilly. See below
201 vs block devices, I/O access, hardware interrupts, DMA, access to
232 Keywords: character device drivers, I/O, signals, DMA, accessing
289 * Title: "I/O Event Handling Under Linux"
291 Keywords: IO, I/O, select(2), poll(2), FDs, aio_read(2), readiness
293 Description: From the Introduction: "I/O Event handling is about
418 Keywords: mouse, driver, gpm, races, asynchronous I/O.
526 Publisher: O'Reilly & Associates.
533 Publisher: O'Reilly & Associates.
[all …]
Dcachetlb.txt381 The final category of APIs is for I/O to deliberately aliased address
383 vmap/vmalloc API. Since kernel I/O goes via physical pages, the I/O
386 the kernel trying to do I/O to vmap areas must manually manage
388 I/O and invalidating it after the I/O returns.
394 page. The design is to make this area safe to perform I/O on.
401 speculatively reading data while the I/O was occurring to the
Dvfio.txt1 VFIO - "Virtual Function I/O"[1]
4 to help ensure I/O devices behave within the boundaries they've been
14 I/O performance. From a device and host perspective, this simply
36 Devices are the main target of any I/O driver. Devices typically
37 create a programming interface made up of I/O access, interrupts,
111 The VFIO device API includes ioctls for describing the device, the I/O
308 4) According to sPAPR specification, A Partitionable Endpoint (PE) is an I/O
432 [1] VFIO was originally an acronym for "Virtual Function I/O" in its
Dbt8xxgpio.txt61 --| O |--
/linux-4.1.27/tools/perf/
DMakefile36 ifneq ($(O),)
37 FULL_O := $(shell readlink -f $(O) || echo $(O))
DMakefile.perf374 …$(Q)$(MAKE) -C $(TRACE_EVENT_DIR) $(LIBTRACEEVENT_FLAGS) O=$(OUTPUT) $(OUTPUT)libtraceevent.a plug…
378 $(Q)$(MAKE) -C $(TRACE_EVENT_DIR) O=$(OUTPUT) clean >/dev/null
381 $(Q)$(MAKE) -C $(TRACE_EVENT_DIR) $(LIBTRACEEVENT_FLAGS) O=$(OUTPUT) install_plugins
384 $(Q)$(MAKE) -C $(LIB_DIR) O=$(OUTPUT) $(OUTPUT)libapi.a
388 $(Q)$(MAKE) -C $(LIB_DIR) O=$(OUTPUT) clean >/dev/null
DCREDITS24 Shawn O. Pearce
/linux-4.1.27/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.
Ddv13941 What: dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire)
Draw13941 What: raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire)
/linux-4.1.27/Documentation/devicetree/bindings/pci/
Dnvidia,tegra20-pcie.txt37 - The remaining entries setup the mapping for the standard I/O, memory and
40 - 0x81000000: I/O memory region
70 - vdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
83 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must
85 - hvdd-pex-supply: High-voltage supply for PCIe I/O and PCIe output clocks.
90 - vdd-pexa-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
93 - vdd-pexb-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
98 - dvddio-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
101 - hvdd-pex-supply: High-voltage supply for PCIe I/O and PCIe output clocks.
105 - vddio-pex-ctl-supply: Power supply for PCIe control I/O partition. Must
[all …]
Dversatile.txt17 - ranges: ranges for the PCI memory and I/O regions
35 ranges = <0x01000000 0 0x00000000 0x43000000 0 0x00010000 /* downstream I/O */
Dbrcm,iproc-pcie.txt5 - reg: base address and length of the PCIe controller I/O register space
14 - ranges: ranges for the PCI memory and I/O regions
Dsamsung,exynos5440-pcie.txt29 0x81000000 0 0 0x40001000 0 0x00010000 /* downstream I/O */
49 0x81000000 0 0 0x60001000 0 0x00010000 /* downstream I/O */
Ddesignware-pcie.txt12 - ranges: ranges for the PCI memory and I/O regions
Drcar-pci.txt11 - ranges: ranges for the PCI memory and I/O regions.
/linux-4.1.27/arch/m68k/hp300/
Dhp300map.map195 compose 'O' 'A' to '�'
225 compose '`' 'O' to '�'
227 compose '\'' 'O' to '�'
229 compose '^' 'O' to '�'
231 compose '~' 'O' to '�'
233 compose '"' 'O' to '�'
235 compose '/' 'O' to '�'
/linux-4.1.27/tools/power/cpupower/bench/
DMakefile3 ifneq ($(O),)
4 OUTPUT := $(O)/
/linux-4.1.27/drivers/uio/
DKconfig2 tristate "Userspace I/O drivers"
28 tristate "Userspace I/O platform driver with generic IRQ handling"
30 Platform driver for Userspace I/O devices, including generic
44 Platform driver for Userspace I/O devices, including generic
65 This device differs from other UIO devices since it uses I/O
66 ports instead of memory mapped I/O. In order to make it
78 Userspace I/O interface for the Sercos III PCI card from
149 Userspace I/O interface for the Humusoft MF624 PCI card.
/linux-4.1.27/drivers/zorro/
Dzorro.ids38 4500 A2232 Prototype [Multi I/O]
39 4600 A2232 [Multi I/O]
88 ff00 GPIB/Dual IEEE-488/Twin-X [Multi I/O]
144 0b98 IO-Extender [Multi I/O]
192 1000 MultiFace I [Multi I/O]
208 0500 32Bit Parallel I/O Interface
241 1000 MultiFace I [Multi I/O]
242 1100 MultiFace II [Multi I/O]
243 1200 MultiFace III [Multi I/O]
270 e300 Connection [Multi I/O]
[all …]
/linux-4.1.27/Documentation/zh_CN/
Dio_ordering.txt25 在某些平台上，所谓的内存映射I/O是弱顺序。在这些平台上，驱动开发者有责任
26 保证I/O内存映射地址的写操作按程序图意的顺序达到设备。通常读取一个“安全”
30 屏障操作，mb()，不过仅适用于I/O）。
Dvolatile-considered-harmful.txt62 volatile的存储类型最初是为那些内存映射的I/O寄存器而定义。在内核里，寄存器访问也应
63 该被锁保护，但是人们也不希望编译器“优化”临界区内的寄存器访问。内核里I/O的内存访问
64 是通过访问函数完成的；不赞成通过指针对I/O内存的直接访问，并且不是在所有体系架构上
Dgpio.txt97 注意，这些操作包含所用平台的 I/O 屏障代码，驱动无须显式地调用他们。
134 接下来是设置I/O方向，这通常是在板级启动代码中为所使用的 GPIO 设置
502 模拟的 I/O 接口, 如此精简指令是很有意义的。
/linux-4.1.27/drivers/iio/
DKconfig2 # Industrial I/O subsystem configuration
6 tristate "Industrial I/O support"
9 The industrial I/O subsystem provides a unified framework for
30 tristate "Industrial I/O buffering based on kfifo"
/linux-4.1.27/Documentation/spi/
Dspi-lm70llp42 D7 9 --> SI/O 5
44 Select 13 <-- SI/O 1
60 shows that the SI/O line from the LM70 chip is connected to the base of a
64 Interpreting this circuit, when the LM70 SI/O line is High (or tristate
67 connector. When SI/O is Low (driven by the LM70 or the host) on the other
Dspidev3 full duplex transfers and device I/O configuration are also available.
113 - At this time there is no async I/O support; everything is purely
124 - There's a limit on the number of bytes each I/O request can transfer
129 won't see any I/O errors when talking to a non-existent device.
Dspi-summary89 Many microcontrollers that can run Linux integrate one or more I/O
134 SPI requests always go into I/O queues. Requests for a given SPI device
377 As soon as it enters probe(), the driver may issue I/O requests to
388 + which I/O buffers are used ... each spi_transfer wraps a
414 - The basic I/O primitive is spi_async(). Async requests may be
434 which would normally be called from probe() before the first I/O is
446 - I/O buffers use the usual Linux rules, and must be DMA-safe.
451 I/O buffers into a group of protocol transactions. These can
515 change them right away ... otherwise drivers could corrupt I/O
583 of the driver will be managing the I/O queue fed by the now deprecated
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-bus-css23 Note: This is an I/O-subchannel specific attribute.
31 channel subsystem when last queried by the common I/O
34 Note: This is an I/O-subchannel specific attribute.
Dsysfs-block5 The /sys/block/<disk>/stat files displays the I/O
26 I/O statistics of partition <part>. The format is the
118 minimum I/O size which is the smallest request the
124 workloads where a high number of I/O operations is
131 Storage devices may report an optimal I/O size, which is
132 the device's preferred unit for sustained I/O. This is
137 throughput is desired. If no optimal I/O size is
144 Standard I/O elevator operations include attempts to
145 merge contiguous I/Os. For known random I/O loads these
150 with the previous I/O request are enabled. When set to 2,
Dprocfs-diskstats5 The /proc/diskstats file displays the I/O statistics
Dsysfs-tty54 Shows the current tty port I/O address for this port.
117 Show the I/O type that is to be used with the iomem base
127 The I/O memory base for this port.
/linux-4.1.27/arch/ia64/kernel/
Drelocate_kernel.S63 #define O(member) IA64_CPUINFO_##member##_OFFSET macro
66 addl r17=O(PTCE_STRIDE),r2
67 addl r2=O(PTCE_BASE),r2
69 ld8 r18=[r2],(O(PTCE_COUNT)-O(PTCE_BASE));; // r18=ptce_base
79 #undef O
Dmca_asm.S60 #define O(member) IA64_CPUINFO_##member##_OFFSET macro
64 addl r17=O(PTCE_STRIDE),r2
65 addl r2=O(PTCE_BASE),r2
67 ld8 r18=[r2],(O(PTCE_COUNT)-O(PTCE_BASE));; // r18=ptce_base
77 #undef O
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-build.sh56 configinit.sh $T/config O=$builddir
63 make O=$builddir -j$ncpus $TORTURE_KMAKE_ARG > $builddir/Make.out 2>&1
/linux-4.1.27/Documentation/vm/
Dzswap.txt6 for potentially reduced swap I/O.  This trade-off can also result in a
18 * Overcommitted guests that share a common I/O resource can
19     dramatically reduce their swap I/O pressure, avoiding heavy handed I/O
21 impact to the guest workload and guests sharing the I/O subsystem
/linux-4.1.27/Documentation/hid/
Duhid.txt1 UHID - User-space I/O driver support for HID subsystem
9 device connected to the user-space controlled bus. The UHID API defines the I/O
21 If a new device is detected by your HID I/O Driver and you want to register this
42 I/O with readv()/writev().
52 event. If you receive the UHID_OPEN event, you should start I/O. If the last
58 You may decide to ignore UHID_OPEN/UHID_CLOSE, though. I/O is allowed even
90 This creates the internal HID device. No I/O is possible until you send this
92 contains information about your device. You can start I/O now.
95 This destroys the internal HID device. No further I/O will be accepted. There
109 field to 0 if no error occurred or to EIO if an I/O error occurred.
[all …]
Dhid-transport.txt1 HID I/O Transport Drivers
7 Bluetooth, I2C and user-space I/O drivers.
12 The HID subsystem is designed as a bus. Any I/O subsystem may provide HID
24 | I/O Driver | | I/O Driver |
45 I/O: USB, I2C, Bluetooth-l2cap
55 I/O drivers normally provide hotplug detection or device enumeration APIs to the
88 driver must provide two bi-directional I/O channels to each HID device. These
247 However, once ->open() is called, transport drivers must be ready for I/O.
254 Transport drivers can put devices asleep and terminate any I/O of all
301 Transport drivers are responsible of reading data from I/O devices. They must
[all …]
/linux-4.1.27/Documentation/sound/oss/
DESS186820 For configuring the sound card's I/O addresses, IRQ and DMA, here is a
39 In this setup, the main card I/O is 0x0220, FM synthesizer is 0x0388, and
43 the sound modules with the proper I/O information. Here is my setup:
DAudioExcelDSP1626 set up I/O addresses, IRQ lines and DMA channels. Some parameters are
33 io I/O base address (0x220 or 0x240)
38 mss_base I/O base address for activate MSS mode (default SBPRO)
40 mpu_base I/O base address for activate MPU-401 mode
DOPL35 Change the I/O address in the very unlikely case this card is differently
DSoundblaster10 io I/O address of the Sound Blaster chip (0x220,0x240,0x260,0x280)
14 mpu_io I/O for MPU chip if present (0x300,0x330)
Dultrasound9 io I/O address of the Ultrasound card (eg. io=0x220)
/linux-4.1.27/fs/squashfs/
DKconfig74 bool "Use multiple decompressors for parallel I/O"
77 poor performance on parallel I/O workloads when using multiple CPU
80 If you have a parallel I/O workload and your system has enough memory,
81 using this option may improve overall I/O performance.
88 bool "Use percpu multiple decompressors for parallel I/O"
91 poor performance on parallel I/O workloads when using multiple CPU
178 the optimal I/O size is 4K (even though the devices can support
181 Using a 4K device block size may also improve overall I/O
/linux-4.1.27/Documentation/networking/
Darcnet-hardware.txt256 - the I/O address: this is the "port" your ARCnet card is on. Probed
404 No Name Taiwan R.O.C? 8
458 (I/O and Memory | 1 1 * 0 0 0 0 * 1 1 0 1 |
470 a: The first digit of the I/O address.
478 b: The second digit of the I/O address.
488 The I/O address is in the form ab0. For example, if
568 | Offs|Base |I/O Addr |
593 S1 1-3: I/O Base Address Select
617 Setting the I/O Base Address
621 of eight possible I/O Base addresses using the following table
[all …]
Dnetlink_mmap.txt1 This file documents how to use memory mapped I/O with netlink.
8 Memory mapped netlink I/O can be used to increase throughput and decrease
14 Memory mapped netlink I/O used two circular ring buffers for RX and TX which
18 user-space memory without copying them as done with regular socket I/O,
29 In order to use memory mapped netlink I/O, user-space needs three main changes:
51 On kernel side, in order to make use of memory mapped I/O on receive, the
52 originating netlink subsystem needs to support memory mapped I/O, otherwise
55 Dumps of kernel databases automatically support memory mapped I/O.
62 Structured and definitions for using memory mapped I/O are contained in
185 not support memory mapped I/O. Appropriate action is
Dvxge.txt14 This Linux driver supports all Neterion's X3100 series 10 GbE PCIe I/O
36 iii) PCI-SIG's I/O Virtualization
DREADME.sb100059 to redefine the value of READ_DATA_PORT to match the I/O address used
68 of "pnpdump" to a file and editing this file to set the correct I/O ports,
72 errors and fix as necessary. (As an aside, I use I/O ports 0x110 and
153 option in the lines that allocate the two I/O addresses for the SB1000 card.
154 This first popped up on RH 6.0. Delete "(CHECK)" for the SB1000 I/O addresses.
Dcs89x0.txt46 5.4 Resolving I/O Conflicts
167 Base I/O Address: 300
245 writing to I/O space until it knows that there is a cs89x0
249 the I/O address, but it is a flag to tell the driver
316 (non-modular) then its I/O address is automatically determined by
500 5.4 RESOLVING I/O CONFLICTS
532 I/O Address Device IRQ Device
534 200-20F Game I/O adapter 3 COM2, Bus Mouse
/linux-4.1.27/Documentation/i2c/busses/
Di2c-parport-light6 on the parport driver, and uses direct I/O access instead. This might be
17 * base: base I/O address
Di2c-nforce237 I/O ports at c000 [size=32]
48 the driver to work with direct I/O access, which is different to the EC
Di2c-pca-isa13 I/O base address
Di2c-amd811121 I/O ports at d400 [size=32]
Di2c-sis559543 * force_addr=0xaddr Set the I/O base address. Useful for boards
Di2c-ali15x387 just enable the SMB alone. The SMB and the ACPI have separate I/O spaces.
101 This driver requests the I/O space for only the SMB
/linux-4.1.27/Documentation/devicetree/bindings/gpio/
Dgpio-pcf857x.txt1 * PCF857x-compatible I/O expanders
3 The PCF857x-compatible chips have "quasi-bidirectional" I/O lines that can be
45 The I/O expander can detect input state changes, and thus optionally act as
60 Example: PCF8575 I/O expander node
Dgpio-max732x.txt1 * MAX732x-compatible I/O expanders
23 The I/O expander can detect input state changes, and thus optionally act as
Dgpio-grgpio.txt1 Aeroflex Gaisler GRGPIO General Purpose I/O cores.
/linux-4.1.27/Documentation/video4linux/
DCARDLIST.ivtv13 13 -> I/O Data GV-MVP/RX [10fc:d01e,10fc:d038,10fc:d039]
14 14 -> I/O Data GV-MVP/RX2E [10fc:d025]
Dvideobuf8 to implement many of the standard POSIX I/O system calls, including read(),
10 implement the bulk of the V4L2 ioctl() calls related to streaming I/O,
80 buf_setup() is called early in the I/O process, when streaming is being
81 initiated; its purpose is to tell videobuf about the I/O stream. The count
101 When a buffer is queued for I/O, it is passed to buf_queue(), which should
110 used. The driver should ensure that there is no I/O active on the buffer,
125 One way to ensure that a buffer is no longer under I/O is to pass it to:
129 Here, vb is the buffer, non_blocking indicates whether non-blocking I/O
211 When streaming I/O is done to kernel-space buffers, the driver must support
226 The call to videobuf_stop() terminates any I/O in progress - though it is
[all …]
Dcafe_ccic36 - min_buffers: The minimum number of streaming I/O buffers that the driver
41 - max_buffers: The maximum number of streaming I/O buffers; default is
/linux-4.1.27/Documentation/scsi/
Dadvansys.txt87 specifying a 5th (ASC_NUM_IOPORT_PROBE + 1) I/O Port. The
88 first three hex digits of the pseudo I/O Port must be set to
163 This option can be used to either disable I/O port scanning or to limit
164 scanning to 1 - 4 I/O ports. Regardless of the option setting EISA and
169 1. Eliminate I/O port scanning:
173 2. Limit I/O port scanning to one I/O port:
175 3. Limit I/O port scanning to four I/O ports:
185 I/O Port may be added to specify the driver debug level. Refer to
DBusLogic.txt139 device or logical unit, and can improve I/O performance substantially. In
141 performance, and scatter/gather I/O can support as many segments as can be
142 effectively utilized by the Linux I/O subsystem. Control over the use of
180 driver will interrogate the PCI configuration space and use the I/O port
181 addresses assigned by the system BIOS, rather than the ISA compatible I/O
182 port addresses. The ISA compatible I/O port address is then disabled by the
184 used to disable the ISA compatible I/O port entirely as it is not necessary.
185 The ISA compatible I/O port is disabled by default on the BT-948/958/958D.
295 o PCI I/O Port Assignments
298 recognize the PCI I/O port assignments made by the motherboard's PCI BIOS.
[all …]
DNinjaSCSI.txt12 PC card: I-O data PCSC-F (NinjaSCSI-3)
13 I-O data CBSC-II in 16 bit mode (NinjaSCSI-32Bi)
14 SCSI device: I-O data CDPS-PX24 (CD-ROM drive)
/linux-4.1.27/Documentation/virtual/kvm/devices/
Ds390_flic.txt4 FLIC handles floating (non per-cpu) interrupts, i.e. I/O, service and some
53 Register an I/O adapter interrupt source. Takes a kvm_s390_io_adapter
64 id contains the unique id for the adapter, isc the I/O interruption subclass
70 Modifies attributes of an existing I/O adapter interrupt source. Takes
/linux-4.1.27/Documentation/PCI/
Dpci-error-recovery.txt18 halting all I/O to it. The goal of a disconnection is to avoid system
34 It also gives the drivers a chance to defer incoming I/O as
41 of reset it desires, the choices being a simple re-enabling of I/O
46 After a reset and/or a re-enabling of I/O, all drivers are
88 pci_channel_io_normal, /* I/O channel is in normal state */
89 pci_channel_io_frozen, /* I/O to channel is blocked */
118 is isolated, in that all I/O is blocked: all reads return 0xffffffff,
129 already have "noticed" the error because of a failing I/O, but this
174 >>> attempts I/O at this point, or not. I/O's will fail, returning
176 >>> EEH_MAX_FAILS I/O's are attempted to a frozen adapter, EEH
[all …]
D00-INDEX10 - the PCI Express I/O Virtualization HOWTO
Dpci-iov-howto.txt1 PCI Express I/O Virtualization Howto
13 Single Root I/O Virtualization (SR-IOV) is a PCI Express Extended
/linux-4.1.27/drivers/tty/vt/
Ddefkeymap.map300 compose 'O' 'A' to '�'
330 compose '`' 'O' to '�'
332 compose '\'' 'O' to '�'
334 compose '^' 'O' to '�'
336 compose '~' 'O' to '�'
338 compose '"' 'O' to '�'
340 compose '/' 'O' to '�'
Ddefkeymap.c_shipped231 {'O', 'A', 0305}, {'o', 'a', 0345},
246 {'`', 'O', 0322}, {'`', 'o', 0362},
247 {'\'', 'O', 0323}, {'\'', 'o', 0363},
248 {'^', 'O', 0324}, {'^', 'o', 0364},
249 {'~', 'O', 0325}, {'~', 'o', 0365},
250 {'"', 'O', 0326}, {'"', 'o', 0366},
251 {'/', 'O', 0330}, {'/', 'o', 0370},
/linux-4.1.27/drivers/parisc/
DREADME.dino6 ** equipped with third-party or customer-installed PCI I/O expansion
9 ** when data is transmitted through PCI I/O expansion cards on the
DKconfig21 bool "U2/Uturn I/O MMU"
26 U2/Uturn chip in "Virtual Mode" and use the I/O MMU.
29 bool "Lasi I/O support"
40 bool "Wax I/O support"
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/
Dguts.txt3 The global utilities block controls power management, I/O device
5 I/O signal configuration, alternate function selection for multiplexed
/linux-4.1.27/Documentation/input/
Damijoy.txt166 This register controls a 4 bit bi-direction I/O port
173 | 14 | DATRY | I/O data Paula pin 33 |
175 | 12 | DATRX | I/O data Paula pin 32 |
177 | 10 | DATLY | I/O data Paula pin 36 |
179 | 08 | DATLX | I/O data Paula pin 35 |
Dwalkera0701.txt26 / O 4 3 O \ pin 3 (GND) LED ________________ 10 ACK
27 ( O 2 1 O ) | C
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dmmc.txt37 - mmc-ddr-1_8v: eMMC high-speed DDR mode(1.8V I/O) is supported
38 - mmc-ddr-1_2v: eMMC high-speed DDR mode(1.2V I/O) is supported
39 - mmc-hs200-1_8v: eMMC HS200 mode(1.8V I/O) is supported
40 - mmc-hs200-1_2v: eMMC HS200 mode(1.2V I/O) is supported
41 - mmc-hs400-1_8v: eMMC HS400 mode(1.8V I/O) is supported
42 - mmc-hs400-1_2v: eMMC HS400 mode(1.2V I/O) is supported
Dsdhci-pxa.txt20 I/O clock.
22 "io" for I/O clock and "core" for optional core clock.
/linux-4.1.27/sound/oss/
DKconfig70 Memory-mapped I/O base address for the MultiSound Classic and
74 hex "MSND Classic I/O 210, 220, 230, 240, 250, 260, 290, 3E0"
78 I/O port address for the MultiSound Classic and related cards.
133 Memory-mapped I/O base address for the primary synthesizer on
137 hex "MSND Pinnacle I/O 210, 220, 230, 240, 250, 260, 290, 3E0"
141 Memory-mapped I/O base address for the primary synthesizer on
145 bool "MSND Pinnacle has S/PDIF I/O"
184 hex "MSND Pinnacle MPU I/O (e.g. 330)"
188 Memory-mapped I/O base address for the Kurzweil daughterboard
200 hex "MSND Pinnacle IDE I/O 0 (e.g. 170)"
[all …]
/linux-4.1.27/drivers/scsi/pcmcia/
DKconfig47 I-O DATA CDPS-PX24's card (PCSC-F)
54 [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")]
55 I-O DATA CBSC-II
/linux-4.1.27/drivers/net/fddi/
DKconfig36 This instructs the driver to use EISA or PCI memory-mapped I/O
37 (MMIO) as appropriate instead of programmed I/O ports (PIO).
40 adapters. TURBOchannel does not have the concept of I/O ports,
/linux-4.1.27/drivers/iio/pressure/
Dt5403.c73 s32 S, O, X; in t5403_comp_pressure() local
92 O = T5403_C(6) * 0x4000 + T5403_C(7) * t_r / 8 + in t5403_comp_pressure()
96 X = (S * p_r + O) / 0x4000; in t5403_comp_pressure()
/linux-4.1.27/drivers/pci/hotplug/
DKconfig93 tristate "Generic port I/O CompactPCI Hotplug driver"
98 standard port I/O.
128 tristate "RPA Dynamic Logical Partitioning for I/O slots"
132 for I/O slots.
/linux-4.1.27/drivers/net/wireless/b43legacy/
DKconfig78 Include both, Direct Memory Access (DMA) and Programmed I/O (PIO)
93 bool "PIO (Programmed I/O) only"
96 Only include Programmed I/O (PIO).
/linux-4.1.27/Documentation/laptops/
Ddisk-shock-protection.txt24 a shock protection facility. The idea is to stop all I/O operations on
43 of the respective drive off the platter and block all I/O operations
62 /dev/sda and stop all I/O operations for five seconds:
82 been issued to a device successfully, all I/O operations on the
92 actually result in stopping I/O to a whole bunch of devices. However,
104 I/O operations on that drive (and the reset itself) will be delayed
D00-INDEX18 - info on Linux Sony Programmable I/O Device support.
/linux-4.1.27/drivers/scsi/aacraid/
DTODO3 o I/O size increase
/linux-4.1.27/Documentation/filesystems/
DLocking234 ->readpage() unlocks the page, either synchronously or via I/O
238 I/O against them. They come unlocked upon I/O completion.
245 it *must* start I/O against the page, even if that would involve
246 blocking on in-progress I/O.
251 currently-in-progress I/O.
254 would need to block against in-progress I/O to be able to start new I/O
260 in-progress I/O and then start new I/O.
272 page, write I/O can be submitted and the write I/O completion handler must run
273 end_page_writeback() once the I/O is complete. If no I/O is submitted, the
294 sync operations. The address_space should start I/O against at least
Dsysfs-pci.txt57 [1] rw for RESOURCE_IO (I/O port) regions only
65 value from any attempted mmap. The most notable of these are I/O port
92 Legacy I/O port and ISA memory resources are also provided in sysfs if the
103 do legacy port I/O. The application should open the file, seek to the desired
/linux-4.1.27/drivers/media/radio/
DKconfig325 hex "Aztech/Packard Bell I/O port (0x350 or 0x358)"
339 I/O port address and settings below. The following cards either have
350 hex "Fixed I/O port (0x20c, 0x30c, 0x24c, 0x34c, 0x248 or 0x28c)"
358 On Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the I/O
361 If automatic I/O port probing is enabled this port will be used only
365 bool "Automatic I/O port probing"
440 Enter the I/O port of your Trust FM radio card. If unsure, try the
459 hex "Typhoon I/O port (0x316 or 0x336)"
463 Enter the I/O port of your Typhoon or EcoRadio radio card.
493 hex "ZOLTRIX I/O port (0x20c or 0x30c)"
[all …]
/linux-4.1.27/Documentation/sound/alsa/
DHD-Audio-Controls.txt11 jack-retasking of multi-I/O jacks.
54 when the pin is a multi-I/O jack for surround channels.
61 An enum control to re-task the multi-I/O jacks for surround outputs.
111 jack-retasking of multi-I/O jacks.
DCMIPCI.txt104 Digital I/O
213 You need to set the module option "mpu_port" to a valid I/O port address
214 to enable MIDI support. Valid I/O ports are 0x300, 0x310, 0x320 and
244 If the auto-detection fails, try to pass the exact I/O address.
/linux-4.1.27/Documentation/accounting/
Dtaskstats-struct.txt108 /* Delay waiting for synchronous block I/O to complete
109 * does not account for delays in I/O submission
114 /* Delay waiting for page fault I/O (swap in only) */
159 /* The following four fields are I/O statistics of a task. */
Ddelay-accounting.txt12 b) completion of synchronous block I/O initiated by the task
45 delay seen for cpu, sync block I/O, swapin, memory reclaim etc.
Dcgroupstats.txt18 about tasks blocked on I/O. If CONFIG_TASK_DELAY_ACCT is disabled, this
/linux-4.1.27/Documentation/devicetree/bindings/serial/
Defm32-uart.txt9 - energymicro,location : Decides the location of the USART I/O pins.
/linux-4.1.27/drivers/md/
DKconfig159 tristate "Multipath I/O support"
216 bool "request-based DM: use blk-mq I/O path by default"
219 This option enables the blk-mq based I/O path for request-based
238 This interface allows you to do buffered I/O on a device and acts
389 tristate "I/O Path Selector based on the number of in-flight I/Os"
398 tristate "I/O Path Selector based on the service time"
402 the path expected to complete the incoming I/O in the shortest
408 tristate "I/O delaying target"
426 A target that intermittently fails I/O for debugging purposes.
453 mapping of fixed-size regions of I/O across a fixed set of paths.
/linux-4.1.27/tools/power/x86/turbostat/
DMakefile7 BUILD_OUTPUT := $(O)
/linux-4.1.27/scripts/
Dmkmakefile41 MAKEARGS += O=\$(if \$(patsubst /%,,\$(makedir)),\$(CURDIR)/)\$(patsubst %/,%,\$(makedir))
/linux-4.1.27/drivers/net/ethernet/wiznet/
DKconfig56 after mapping to Memory-Mapped I/O space.
63 which are directly mapped to Memory-Mapped I/O space.
/linux-4.1.27/Documentation/devicetree/bindings/w1/
Dw1-gpio.txt7 - the first one is used as data I/O pin
/linux-4.1.27/lib/
DKconfig.kgdb35 This is a kgdb I/O module specifically designed to test
36 kgdb's internal functions. This kgdb I/O module is
40 the tests. The most basic of this I/O module is to boot
/linux-4.1.27/arch/mn10300/
DKconfig.debug69 would like kernel messages to be formatted into GDB $O packets so
96 bool "Debug GDB stub I/O"
100 low-level I/O.
/linux-4.1.27/Documentation/devicetree/bindings/x86/
Dinterrupt.txt4 * Intel I/O Advanced Programmable Interrupt Controller (IO APIC)
/linux-4.1.27/tools/power/cpupower/debug/x86_64/
DMakefile3 OUTPUT := $(O)/
/linux-4.1.27/drivers/gpio/
DKconfig166 This option enables support for GPIOs found on Fintek Super-I/O
225 Say yes here to support GPIO functionality of IT8761E super I/O chip.
375 tristate "SMSC SCH311x SuperI/O GPIO"
378 SCH3116 "Super I/O" chipsets.
423 This driver supports Digital I/O exposed by pin blocks found on some
451 tristate "NEC VR4100 series General-purpose I/O Uint support"
454 Say yes here to support the NEC VR4100 series General-purpose I/O Uint
557 Input (designated by 'I'), Push-Pull Output ('O'), or Open-Drain
561 8 bits: max7319 (8I), max7320 (8O), max7321 (8P),
585 tristate "PCA95[357]x, PCA9698, TCA64xx, and MAX7310 I/O ports"
[all …]
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-transport-srp22 layer error has been observed before failing I/O. Zero means
23 failing I/O immediately. Setting this attribute to "off" will
Dsysfs-driver-ib_srp14 byte I/O controller GUID portion of the 16-byte target port
28 * io_class, a hexadecimal number specifying the SRP I/O class.
29 Must be either 0xff00 (rev 10) or 0x0100 (rev 16a). The I/O
129 Description: Eight-byte I/O controller GUID portion of the 16-byte target
Dfirewire-cdev92 Unmap the isochronous I/O buffer from the process address space.
95 Besides stopping and freeing I/O contexts that were associated
/linux-4.1.27/drivers/net/can/cc770/
DKconfig11 connected to the ISA bus using I/O port, memory mapped or
/linux-4.1.27/drivers/sn/
DKconfig18 I/O controller or a PCI IOC3 serial card say Y.
/linux-4.1.27/Documentation/devicetree/bindings/sound/
Dtas2552.txt11 "iovdd" I/O Voltage
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Dbrcm,iproc-i2c.txt9 Define the base and range of the I/O address space that contain the iProc
Di2c-efm32.txt13 - energymicro,location : Decides the location of the USART I/O pins.
/linux-4.1.27/drivers/staging/fwserial/
DTODO4 - I/O is handled asynchronously which presents some issues when error
/linux-4.1.27/arch/mips/dec/
Dint-handler.S234 FEXPORT(asic_all_int) # various I/O ASIC junk
243 FEXPORT(asic_dma_int) # I/O ASIC DMA events
/linux-4.1.27/arch/powerpc/boot/dts/
Damigaone.dts49 ranges = <0x01000000 0 0x00000000 0xfe000000 0 0x00c00000 // PCI I/O
73 /* First 4k for I/O at 0x0 on PCI mapped to 0x0 on ISA. */
/linux-4.1.27/tools/perf/tests/
Dmake101 # to distinguish O=... tests
104 # disable some tests for O=...
214 cmd="cd $(PERF) && make -f $(MK) O=$$TMP_O DESTDIR=$$TMP_DEST $($(patsubst %_O,%,$@))"; \
/linux-4.1.27/arch/nios2/
DKconfig184 bool "Set custom I/O region base address"
187 This option allows you to set the virtual address of the I/O region.
192 hex "Virtual base address of the I/O region" if NIOS2_IO_REGION_BASE_BOOL
/linux-4.1.27/Documentation/usb/
Dehci.txt47 It's believed to do all the right PCI magic so that I/O works even on
118 usb-storage doing disk I/O; watch the request queues!)
194 I/O completion and the driver issuing the next request will take longer
195 than the I/O. If that same loop used 16 KB chunks, it'd be better; a
198 But rather than depending on such large I/O buffers to make synchronous
199 I/O be efficient, it's better to just queue up several (bulk) requests
Ddma.txt2 over how DMA may be used to perform I/O operations. The APIs are detailed
39 tear down the IOMMU mappings with each request than perform the I/O!
59 systems where the I/O would otherwise thrash an IOMMU mapping. (See
/linux-4.1.27/drivers/mmc/
DKconfig10 Digital I/O support.
/linux-4.1.27/drivers/staging/comedi/
DKconfig31 This is set to 20480 KiB so that a fast I/O card with 16
52 Currently, it only handles digital I/O subdevices.
72 A cheap and easy way to get a few more digital I/O lines. Steal
148 tristate "Simple Digital I/O board support (8-bit ports)"
150 Enable support for various simple ISA or PC/104 Digital I/O boards.
151 These boards all use 8-bit I/O ports.
420 tristate "I/O Products PC/104 AIO12-8 Analog I/O Board support"
423 Enable support for I/O Products PC/104 AIO12-8 Analog I/O Board
429 tristate "I/O Products PC/104 IIRO16 Board support"
431 Enable support for I/O Products PC/104 IIRO16 Relay And Isolated
[all …]
/linux-4.1.27/drivers/idle/
DKconfig23 chipsets. The chipset must have I/O AT support, such as the
/linux-4.1.27/drivers/staging/iio/trigger/
DKconfig2 # Industrial I/O standalone triggers
/linux-4.1.27/arch/frv/kernel/
Dhead-uc-fr451.S58 # set the I/O region protection registers for FR401/3/5
64 movgs gr5,dampr11 ; General I/O tile
Dhead-mmu-fr451.S234 # DAMPR11 0xE0000000-0xFFFFFFFF Uncached I/O
241 # set the I/O region protection registers for FR451 in MMU mode
248 movgs gr5,damlr11 ; General I/O tile
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dsamsung-s5c73m3.txt20 - vddio-host-supply : host I/O power supply (1.8V to 2.8V);
21 - vddio-cis-supply : CIS I/O power supply (1.2V to 1.8V);
Dsamsung-s5k6a3.txt12 - svddio-supply : I/O voltage supply;
/linux-4.1.27/arch/arm/boot/dts/
Dspear1310.dtsi99 ranges = <0x81000000 0 0 0x80020000 0 0x00010000 /* downstream I/O */
117 ranges = <0x81000000 0 0 0x90020000 0 0x00010000 /* downstream I/O */
135 ranges = <0x81000000 0 0 0xc0020000 0 0x00010000 /* downstream I/O */
Dversatile-pb.dts43 ranges = <0x01000000 0 0x00000000 0x43000000 0 0x00010000 /* downstream I/O */
/linux-4.1.27/drivers/iio/trigger/
DKconfig2 # Industrial I/O standalone triggers
/linux-4.1.27/Documentation/devicetree/bindings/hwmon/
Dlm90.txt43 interrupts = <TEGRA_GPIO(O, 4) IRQ_TYPE_LEVEL_LOW>;
/linux-4.1.27/Documentation/scsi/scsi_transport_srp/
Drport_state_diagram.dot11 failfast [ label = "fail I/O\nfast" ];
/linux-4.1.27/tools/power/cpupower/debug/i386/
DMakefile3 OUTPUT := $(O)/
/linux-4.1.27/arch/tile/gxio/
DKconfig7 # Support direct access to the common I/O DMA facility within the
/linux-4.1.27/Documentation/infiniband/
Duser_verbs.txt45 Direct userspace I/O requires that memory regions that are potential
46 I/O targets be kept resident at the same physical address. The
/linux-4.1.27/drivers/block/zram/
DKconfig10 itself. These disks allow very fast I/O and compression provides
/linux-4.1.27/Documentation/mmc/
Dmmc-dev-attrs.txt44 1. A single erase command will make all other I/O on
47 I/O for another partition on the same card wait for the
/linux-4.1.27/drivers/staging/media/mn88473/
DTODO15 trivial stuff. *Do not* add missing register I/O error checks. Those are
/linux-4.1.27/drivers/staging/media/mn88472/
DTODO15 trivial stuff. *Do not* add missing register I/O error checks. Those are
/linux-4.1.27/arch/sparc/boot/
DMakefile53 quiet_cmd_uimage.o = UIMAGE.O $@
/linux-4.1.27/drivers/staging/iio/
DKconfig2 # Industrial I/O subsystem configuration
/linux-4.1.27/scripts/package/
Dbuildtar60 make ARCH="${ARCH}" O="${objtree}" KBUILD_SRC= INSTALL_MOD_PATH="${tmpdir}" modules_install
/linux-4.1.27/Documentation/misc-devices/mei/
Dmei-client-bus.txt47 Once registered on the ME Client bus, a driver will typically try to do some I/O on
120 The handler implementation will typically call some I/O routine depending on
/linux-4.1.27/arch/mn10300/kernel/
Dmn10300-serial-low.S65 # E2 I/O port base
111 # E2 I/O port base
Dgdb-io-serial-low.S3 # 16550 serial Rx interrupt handler for gdbstub I/O
Dgdb-io-ttysm-low.S3 # MN10300 On-chip serial Rx interrupt handler for GDB stub I/O
/linux-4.1.27/drivers/net/ethernet/sfc/
DKconfig36 This enables support for the SFC9000 I/O Virtualization
/linux-4.1.27/Documentation/w1/slaves/
Dw1_ds240624 CRCs are checked on read and write. Failed checks cause an I/O error to be
/linux-4.1.27/Documentation/blockdev/
Dzram.txt8 in memory itself. These disks allow very fast I/O and compression provides
115 invalid_io RO the number of non-page-size-aligned I/O requests
154 The stat file represents device's I/O statistics not accounted by block
/linux-4.1.27/Documentation/kbuild/
Dkbuild.txt77 The output directory can also be specified using "O=...".
78 Setting "O=..." takes precedence over KBUILD_OUTPUT.
173 The output directory is often set using "O=..." on the commandline.
/linux-4.1.27/Documentation/DocBook/media/
Dfieldseq_tb.gif.b6450 Jgi4x03wcZebIOeet8JJu27ftDvfELetnRUi5YVbvBP1Jsi9Ix7xfQ+k3/8O+Zf+Az6QgRf85GY+
298 fmYgPuXr5+I/PYk/vumaO0VnCOtmfn5yO7s/O+kz7tonaed7fuSC/m5ne+rjp+lz/L2cAQvkvu7v
396 D+O/kAECFix5AOQJPIgwocKFDBs6fAgx4kMSAA7Ko9cpo8aNHDt6/AgypMiRJDNeOkhRosqVLFu6
431 DfCAC3z+4AQvuMEPjvCEK/zfxbD2obIDhldIfOIUr7jFL47xjGt84xzvuMTB4HBAYSYBCy+5yU+O
/linux-4.1.27/Documentation/devicetree/bindings/misc/
Dfsl,qoriq-mc.txt7 queues, buffer pools, I/O interfaces. These resources are building
/linux-4.1.27/arch/frv/
DKconfig.debug45 would like kernel messages to be formatted into GDB $O packets so
/linux-4.1.27/Documentation/ABI/obsolete/
Dsysfs-bus-usb19 free to wake up in response to I/O requests, you should
/linux-4.1.27/fs/gfs2/
DKconfig13 a lock module to allow the computers coordinate their I/O so
/linux-4.1.27/Documentation/fmc/
DFMC-and-SDB.txt2 FMC (FPGA Mezzanine Card) is the standard we use for our I/O devices,
5 In our I/O environments we need to write drivers for each mezzanine
/linux-4.1.27/tools/lguest/
Dlguest.txt15 - Simple I/O model for communication.
54 O=<builddir>".

123