| /Linux-v4.19/arch/alpha/kernel/ |
| D | machvec_impl.h | 100 #define IO(UP,low) \ macro
105 #define DO_APECS_IO IO(APECS,apecs)
106 #define DO_CIA_IO IO(CIA,cia)
107 #define DO_IRONGATE_IO IO(IRONGATE,irongate)
108 #define DO_LCA_IO IO(LCA,lca)
109 #define DO_MARVEL_IO IO(MARVEL,marvel)
110 #define DO_MCPCIA_IO IO(MCPCIA,mcpcia)
111 #define DO_POLARIS_IO IO(POLARIS,polaris)
112 #define DO_T2_IO IO(T2,t2)
113 #define DO_TSUNAMI_IO IO(TSUNAMI,tsunami)
[all …]
|
| /Linux-v4.19/Documentation/x86/i386/ |
| D | IO-APIC.txt | 1 Most (all) Intel-MP compliant SMP boards have the so-called 'IO-APIC',
4 IO-APIC, interrupts from hardware will be delivered only to the
8 multiple IO-APICs. Multiple IO-APICs are used in high-end servers to
15 If your box boots fine with enabled IO-APIC IRQs, then your
21 0: 1360293 IO-APIC-edge timer
22 1: 4 IO-APIC-edge keyboard
25 14: 1448 IO-APIC-edge ide0
26 16: 28232 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
27 17: 51304 IO-APIC-level eth0
91 board does not do default daisy-chaining. (or the IO-APIC has the PIRQ pins
|
| /Linux-v4.19/Documentation/fb/ |
| D | deferred_io.txt | 1 Deferred IO
4 Deferred IO is a way to delay and repurpose IO. It uses host memory as a
6 IO. The following example may be a useful explanation of how one such setup
10 - deferred IO and driver sets up fault and page_mkwrite handlers
61 2. Setup your deferred IO callback. Eg:
65 The deferred_io callback is where you would perform all your IO to the display
|
| /Linux-v4.19/drivers/net/ethernet/amd/ |
| D | atarilance.c | 234 #define DREG IO->data
235 #define AREG IO->addr
473 struct lance_ioreg *IO; in lance_probe1() local
533 IO = lp->iobase = (struct lance_ioreg *)ioaddr; in lance_probe1()
541 if (addr_accessible( &(IO->eeprom), 0, 0 )) { in lance_probe1()
543 i = IO->mem; in lance_probe1()
594 i = IO->eeprom; in lance_probe1()
599 i = IO->mem; in lance_probe1()
624 IO->ivec = IRQ_SOURCE_TO_VECTOR(dev->irq); in lance_probe1()
643 struct lance_ioreg *IO = lp->iobase; in lance_open() local
[all …]
|
| /Linux-v4.19/drivers/message/fusion/lsi/ |
| D | mpi_history.txt | 88 * 03-11-05 01.05.07 Removed function codes for SCSI IO 32 and
91 * 06-24-05 01.05.08 Added function codes for SCSI IO 32 and
242 * Added Manufacturing pages, IO Unit Page 2, SCSI SPI
273 * Added IO Unit Page 3.
302 * Added structures for Manufacturing Page 4, IO Unit
364 * SAS IO Unit, SAS Expander, SAS Device, and SAS PHY.
368 * Two new bits defined for IO Unit Page 1 Flags field.
371 * Four new Flags bits defined for IO Unit Page 2.
372 * Added IO Unit Page 4.
379 * Added more defines for SAS IO Unit Page 0
[all …]
|
| /Linux-v4.19/drivers/pci/hotplug/ |
| D | ibmphp_res.c | 98 case IO: in alloc_bus_range()
132 case IO: in alloc_bus_range()
257 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
265 rc = alloc_bus_range(&bus_cur, &newrange, curr, IO, 0); in ibmphp_rsrc_init()
270 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
329 new_io->type = IO; in ibmphp_rsrc_init()
384 case IO: in add_bus_range()
407 case IO: in add_bus_range()
457 case IO: in update_resources()
491 case IO: in fix_me()
[all …]
|
| /Linux-v4.19/Documentation/block/ |
| D | queue-sysfs.txt | 62 to make an educated guess at when the IO will complete. Based on this
63 guess, the kernel will put the process issuing IO to sleep for an amount
67 IO to sleep for this amont of microseconds before entering classic
104 This is the smallest preferred IO size reported by the device.
108 This enables the user to disable the lookup logic involved with IO
130 This is the optimal IO size reported by the device.
158 When read, this file will display the current and available IO schedulers
159 for this block device. The currently active IO scheduler will be enclosed
160 in [] brackets. Writing an IO scheduler name to this file will switch
161 control of this block device to that new IO scheduler. Note that writing
[all …]
|
| D | switching-sched.txt | 1 To choose IO schedulers at boot time, use the argument 'elevator=deadline'.
2 'noop' and 'cfq' (the default) are also available. IO schedulers are assigned
17 IO scheduler for a given block device on the fly (thus making it possible,
26 where SCHEDNAME is the name of a defined IO scheduler, and DEV is the
|
| D | 00-INDEX | 4 - BFQ IO scheduler and its tunables
12 - CFQ IO scheduler tunables
18 - Deadline IO scheduler tunables
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | configfs-iio | 6 This represents Industrial IO configuration entry point
14 Industrial IO software triggers directory.
27 Industrial IO software devices directory.
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | armada-xp-mv78460.dtsi | 93 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
95 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
97 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
99 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
102 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
104 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
106 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
108 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
111 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */
114 0x81000000 0xa 0 MBUS_ID(0x08, 0xf0) 0 1 0 /* Port 3.0 IO */>;
|
| D | sun7i-a20-bananapi.dts | 244 "TXD0", "RXD0", "IO-1", "PH3", "USB0-IDDET", "PH5", "", "",
246 "", "", "", "", "IO-4", "IO-5", "", "EMAC-PWR-EN",
249 "", "", "", "IO-GCLK", "", "", "", "",
252 "IO-6", "IO-3", "IO-2", "IO-0", "", "", "", "",
|
| D | armada-xp-mv78260.dtsi | 75 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
77 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
79 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
81 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
84 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
86 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
88 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
90 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
93 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */>;
|
| D | omap-zoom-common.dtsi | 19 reg = <3 0 8>; /* CS3, offset 0, IO size 8 */
55 reg = <3 0x100 8>; /* CS3, offset 0x100, IO size 8 */
66 reg = <3 0x200 8>; /* CS3, offset 0x200, IO size 8 */
77 reg = <3 0x300 8>; /* CS3, offset 0x300, IO size 8 */
|
| D | armada-xp-mv78230.dtsi | 70 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
72 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
74 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
76 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
78 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */>;
|
| /Linux-v4.19/Documentation/networking/ |
| D | hinic.txt | 60 card by AEQs. Also set the addresses of the IO CMDQs in HW.
63 IO components:
66 Completion Event Queues(CEQs) - The completion Event Queues that describe IO
74 Command Queues(CMDQ) - The queues for sending commands for IO management and is
82 IO - de/constructs all the IO components. (hinic_hw_io.c, hinic_hw_io.h)
88 initialization of the driver and the IO components on the case of Interface
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf-timechart.txt | 20 but it's possible to record IO (disk, network) activity using -I argument.
25 events or IO events.
27 In IO mode, every bar has two charts: upper and lower.
70 Don't draw EAGAIN IO events.
73 to see very small and fast IO. It's possible to specify ms or us
118 Record system-wide IO events:
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | blkio-controller.txt | 1 Block IO Controller
6 a need of various kinds of IO control policies (like proportional BW, max BW)
9 and based on user options switch IO policies in the background.
11 Currently two IO control policies are implemented. First one is proportional
14 one is throttling policy which can be used to specify upper IO rate limits
25 - Enable Block IO controller
31 - Compile and boot into kernel and mount IO controller (blkio); see
68 - Enable Block IO controller
127 - Block IO controller.
215 may cause the service time for a given IO to include the service time
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/pci/ |
| D | mvebu-pci.txt | 108 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
110 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
112 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
114 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
117 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
119 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
121 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
123 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
126 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */
129 0x81000000 0xa 0 MBUS_ID(0x08, 0xf0) 0 1 0 /* Port 3.0 IO */>;
|
| /Linux-v4.19/drivers/pinctrl/ti/ |
| D | Kconfig | 9 Say Y here to support Texas Instruments' IO delay pinconf driver.
10 IO delay module is used for the DRA7 SoC family.
|
| /Linux-v4.19/Documentation/core-api/ |
| D | gfp_mask-from-fs-io.rst | 2 GFP masks used from FS/IO context
11 Code paths in the filesystem and IO stacks must be careful when
13 memory reclaim calling back into the FS or IO paths and blocking on
34 mask so no memory allocation can recurse back in the FS/IO.
41 FS/IO code then simply calls the appropriate save function before
|
| /Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/ |
| D | intel,ce4100-ioapic.txt | 4 * Intel I/O Advanced Programmable Interrupt Controller (IO APIC)
16 IO APIC. The second number (S) represents the sense of interrupt which
|
| /Linux-v4.19/drivers/sn/ |
| D | Kconfig | 9 tristate "SGI IOC3 Base IO support"
12 This option enables basic support for the SGI IOC3-based Base IO
|
| /Linux-v4.19/block/ |
| D | Kconfig.iosched | 4 menu "IO Schedulers"
22 a new point in the service tree and doing a batch of IO from there
41 Enable group IO scheduling in CFQ.
72 MQ version of the deadline IO scheduler.
|
| /Linux-v4.19/Documentation/md/ |
| D | raid5-cache.txt | 37 In write-through mode, MD reports IO completion to upper layer (usually
59 In write-back mode, MD reports IO completion to upper layer (usually
81 ID for recovery identification. Data can be IO data and parity data. Data is
89 write-through mode, MD calculates parity for IO data, writes both IO data and
91 parity is settled down in log and finally the IO is finished. Read just reads
94 In write-back mode, MD writes IO data to the log and reports IO completion. The
|
