Home
last modified time | relevance | path

Searched refs:IO (Results 1 – 200 of 321) sorted by relevance

12

/linux-4.4.14/arch/alpha/kernel/
Dmachvec_impl.h99 #define IO(UP,low) \ macro
104 #define DO_APECS_IO IO(APECS,apecs)
105 #define DO_CIA_IO IO(CIA,cia)
106 #define DO_IRONGATE_IO IO(IRONGATE,irongate)
107 #define DO_LCA_IO IO(LCA,lca)
108 #define DO_MARVEL_IO IO(MARVEL,marvel)
109 #define DO_MCPCIA_IO IO(MCPCIA,mcpcia)
110 #define DO_POLARIS_IO IO(POLARIS,polaris)
111 #define DO_T2_IO IO(T2,t2)
112 #define DO_TSUNAMI_IO IO(TSUNAMI,tsunami)
[all …]
/linux-4.4.14/Documentation/x86/i386/
DIO-APIC.txt1 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-4.4.14/Documentation/blockdev/
Dmflash.txt15 2 different operation (ATA, IO) modes. ATA mode doesn't need any new
17 one chip SSD. IO mode is ATA-like custom mode for the host that doesn't have
20 Followings are brief descriptions about IO mode.
21 A. IO mode based on ATA protocol and uses some custom command. (read confirm,
23 B. IO mode uses SRAM bus interface.
24 C. IO mode supports 4kB boot area, so host can boot from mflash.
Dcpqarray.txt35 give it the controller's IO port address at boot time (it is not
/linux-4.4.14/Documentation/fb/
Ddeferred_io.txt1 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
Dmetronomefb.txt17 to do all physical IO work. Currently, an example is implemented for the
33 Metronomefb uses the deferred IO interface so that it can provide a memory
D00-INDEX19 - an introduction to deferred IO.
/linux-4.4.14/drivers/net/ethernet/amd/
Datarilance.c234 #define DREG IO->data
235 #define AREG IO->addr
474 struct lance_ioreg *IO; in lance_probe1() local
534 IO = lp->iobase = (struct lance_ioreg *)ioaddr; in lance_probe1()
542 if (addr_accessible( &(IO->eeprom), 0, 0 )) { in lance_probe1()
544 i = IO->mem; in lance_probe1()
595 i = IO->eeprom; in lance_probe1()
600 i = IO->mem; in lance_probe1()
625 IO->ivec = IRQ_SOURCE_TO_VECTOR(dev->irq); in lance_probe1()
644 struct lance_ioreg *IO = lp->iobase; in lance_open() local
[all …]
/linux-4.4.14/drivers/message/fusion/lsi/
Dmpi_history.txt88 * 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-4.4.14/Documentation/block/
Dqueue-sysfs.txt83 This is the smallest preferred IO size reported by the device.
87 This enables the user to disable the lookup logic involved with IO
109 This is the optimal IO size reported by the device.
137 When read, this file will display the current and available IO schedulers
138 for this block device. The currently active IO scheduler will be enclosed
139 in [] brackets. Writing an IO scheduler name to this file will switch
140 control of this block device to that new IO scheduler. Note that writing
141 an IO scheduler name to this file will attempt to load that IO scheduler
Dswitching-sched.txt1 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
Dcfq-iosched.txt30 IO priority becomes weaker.
77 IO controller working.
124 When a queue is selected for execution, the queues IO requests are only
215 This effectively becomes the fairness in terms of IOPS (IO operations per
223 CFQ IO scheduler Idling Theory
233 did not move the disk head and kept on dispatching sequential IO from
240 All cfq queues doing synchronous sequential IO go on to sync-idle tree.
246 of queues or the tree. So if there are 4 queues waiting for IO to dispatch
247 we will idle only once last queue has dispatched the IO and there is
248 no more IO on this service tree.
[all …]
D00-INDEX8 - CFQ IO scheduler tunables
14 - Deadline IO scheduler tunables
Dnull_blk.txt13 - Implements IO scheduling algorithms (CFQ, Deadline, noop).
18 - Bio-based. IO requests are submitted directly to the device driver.
52 2: Timer: Waits a specific period (completion_nsec) for each IO before
Ddeadline-iosched.txt1 Deadline IO scheduler tunables
8 Selecting IO schedulers
Dioprio.txt47 If pid isn't given, the current process is assumed. IO priority settings
/linux-4.4.14/drivers/pci/hotplug/
Dibmphp_res.c116 case IO: in alloc_bus_range()
151 case IO: in alloc_bus_range()
278 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
286 rc = alloc_bus_range (&bus_cur, &newrange, curr, IO, 0); in ibmphp_rsrc_init()
291 rc = alloc_bus_range(&newbus, &newrange, curr, IO, 1); in ibmphp_rsrc_init()
350 new_io->type = IO; in ibmphp_rsrc_init()
406 case IO: in add_bus_range()
429 case IO: in add_bus_range()
479 case IO: in update_resources()
513 case IO: in fix_me()
[all …]
Dibmphp_pci.c412 io[count]->type = IO; in configure_device()
681 bus_io[count]->type = IO; in configure_bridge()
841 io->type = IO; in configure_bridge()
1270 if (ibmphp_find_resource (bus, start_address, &io, IO) < 0) { in unconfigure_boot_device()
1280 if (ibmphp_find_resource (bus, start_address, &io, IO) < 0) { in unconfigure_boot_device()
1397 if (ibmphp_find_resource (bus, start_address, &io, IO) < 0) { in unconfigure_boot_bridge()
/linux-4.4.14/Documentation/sound/oss/
DCMI833085 (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
92 (IO 0 (SIZE 8) (BASE 0x0530))
93 (IO 1 (SIZE 8) (BASE 0x0388))
103 (IO 0 (SIZE 2) (BASE 0x0330))
112 (IO 0 (SIZE 8) (BASE 0x0200))
120 (IO 0 (SIZE 16) (BASE 0x0220))
DVIBRA1635 (CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING
41 (IO 0 (SIZE 16) (BASE 0x0220))
42 (IO 2 (SIZE 4) (BASE 0x0388))
50 (IO 0 (SIZE 1) (BASE 0x0200))
DESS186824 (IO 0 (BASE 0x0220))
25 (IO 1 (BASE 0x0388))
26 (IO 2 (BASE 0x0330))
/linux-4.4.14/arch/arm/boot/dts/
Domap-zoom-common.dtsi18 reg = <3 0 8>; /* CS3, offset 0, IO size 8 */
54 reg = <3 0x100 8>; /* CS3, offset 0x100, IO size 8 */
65 reg = <3 0x200 8>; /* CS3, offset 0x200, IO size 8 */
76 reg = <3 0x300 8>; /* CS3, offset 0x300, IO size 8 */
Darmada-xp-mv78460.dtsi130 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
132 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
134 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
136 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
139 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
141 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
143 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
145 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
148 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */
151 0x81000000 0xa 0 MBUS_ID(0x08, 0xf0) 0 1 0 /* Port 3.0 IO */>;
Darmada-xp-mv78260.dtsi112 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
114 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
116 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
118 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
121 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */
123 0x81000000 0x6 0 MBUS_ID(0x08, 0xd0) 0 1 0 /* Port 1.1 IO */
125 0x81000000 0x7 0 MBUS_ID(0x08, 0xb0) 0 1 0 /* Port 1.2 IO */
127 0x81000000 0x8 0 MBUS_ID(0x08, 0x70) 0 1 0 /* Port 1.3 IO */
130 0x81000000 0x9 0 MBUS_ID(0x04, 0xf0) 0 1 0 /* Port 2.0 IO */>;
Darmada-xp-mv78230.dtsi107 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
109 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 0.1 IO */
111 0x81000000 0x3 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 0.2 IO */
113 0x81000000 0x4 0 MBUS_ID(0x04, 0x70) 0 1 0 /* Port 0.3 IO */
115 0x81000000 0x5 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */>;
Darmada-385.dtsi96 0x81000000 0x1 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 0 IO */
98 0x81000000 0x2 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 1 IO */
100 0x81000000 0x3 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 2 IO */
102 0x81000000 0x4 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 3 IO */>;
Darmada-380.dtsi91 0x81000000 0x1 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 0 IO */
93 0x81000000 0x2 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 1 IO */
95 0x81000000 0x3 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 2 IO */>;
Dkirkwood-6282.dtsi18 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
20 0x81000000 0x2 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 1.0 IO */>;
Dkirkwood-98dx4122.dtsi16 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */>;
Domap3430-sdp.dts109 reg = <1 0 4>; /* CS1, offset 0, IO size 4 */
153 reg = <2 0 0x20000>; /* CS2, offset 0, IO size 4 */
Darmada-39x.dtsi417 0x81000000 0x1 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 0 IO */
419 0x81000000 0x2 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 1 IO */
421 0x81000000 0x3 0 MBUS_ID(0x04, 0xd0) 0 1 0 /* Port 2 IO */
423 0x81000000 0x4 0 MBUS_ID(0x04, 0xb0) 0 1 0 /* Port 3 IO */>;
Dkirkwood-6281.dtsi16 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */>;
Dkirkwood-6192.dtsi16 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */>;
Domap2420-n8x0-common.dtsi50 reg = <0 0 0x20000>; /* CS0, offset 0, IO size 128K */
Domap3-devkit8000-common.dtsi207 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
263 6 0x400 2>; /* CS6, offset 0 and 0x400, IO size 2 */
Ddm8168-evm.dts89 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
Dlogicpd-torpedo-som.dtsi42 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
Domap3-n950-n9.dtsi128 reg = <0 0 0x20000>; /* CS0, offset 0, IO size 128K */
Darmada-370.dtsi88 0x81000000 0x1 0 MBUS_ID(0x04, 0xe0) 0 1 0 /* Port 0.0 IO */
90 0x81000000 0x2 0 MBUS_ID(0x08, 0xe0) 0 1 0 /* Port 1.0 IO */>;
Dimx6qdl-microsom-ar8035.dtsi73 /* AR8035 pin strapping: IO voltage: pull up */
Domap3-igep.dtsi99 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
Dam335x-chilisom.dtsi211 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
Domap3-evm-37xx.dts162 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
Dam335x-igep0033.dtsi132 reg = <0 0 4>; /* CS0, offset 0, IO size 4 */
/linux-4.4.14/tools/perf/Documentation/
Dperf-timechart.txt20 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.
68 Don't draw EAGAIN IO events.
71 to see very small and fast IO. It's possible to specify ms or us
116 Record system-wide IO events:
/linux-4.4.14/arch/frv/kernel/
Ddma.c39 #define __get_DMAC(IO,X) ({ *(volatile unsigned long *)((IO) + DMAC_##X##x); }) argument
41 #define __set_DMAC(IO,X,V) \ argument
43 *(volatile unsigned long *)((IO) + DMAC_##X##x) = (V); \
47 #define ___set_DMAC(IO,X,V) \ argument
49 *(volatile unsigned long *)((IO) + DMAC_##X##x) = (V); \
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dmvebu-pci.txt108 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 */>;
Dhost-generic-pci.txt8 presenting a set of fixed windows describing a subset of IO, Memory and
25 or both of prefetchable Memory and IO Space may also
/linux-4.4.14/net/netlink/
DKconfig6 bool "NETLINK: mmaped IO"
8 This option enables support for memory mapped netlink IO. This
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-ioapic.txt4 * Intel I/O Advanced Programmable Interrupt Controller (IO APIC)
16 IO APIC. The second number (S) represents the sense of interrupt which
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt1 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
128 - Block IO controller.
216 may cause the service time for a given IO to include the service time
[all …]
D00-INDEX4 - Description for Block IO Controller, implementation and usage details.
/linux-4.4.14/drivers/sn/
DKconfig9 tristate "SGI IOC3 Base IO support"
12 This option enables basic support for the SGI IOC3-based Base IO
/linux-4.4.14/block/
DKconfig.iosched3 menu "IO Schedulers"
21 a new point in the service tree and doing a batch of IO from there
40 Enable group IO scheduling in CFQ.
DKconfig97 the IO rate to a device. IO rate policies are per cgroup and
99 cgroups and specifying per device IO rate policies.
/linux-4.4.14/arch/powerpc/platforms/pseries/
DKconfig61 bool "IO Event Interrupt support"
65 Select this option, if you want to enable support for IO Event
66 interrupts. IO event interrupt is a mechanism provided by RTAS
72 This option will only enable the IO event platform code. You
74 that use this infrastructure to handle IO event interrupts.
/linux-4.4.14/arch/x86/
DKconfig.debug233 # IO delay types:
253 prompt "IO delay type"
257 bool "port 0x80 based port-IO delay [recommended]"
259 This is the traditional Linux IO delay used for in/out_p.
263 bool "port 0xed based port-IO delay"
265 Use port 0xed as the IO delay. This frees up port 0x80 which is
269 bool "udelay based port-IO delay"
271 Use udelay(2) as the IO delay method. This provides the delay
272 while not having any side-effect on the IO port space.
275 bool "no port-IO delay"
[all …]
/linux-4.4.14/Documentation/
Dbus-virt-phys-mapping.txt7 [ This is a mail message in response to a query on IO mapping, thus the
44 2 GB-3 GB "system IO" (inb/out and similar accesses on x86)
45 3 GB-4 GB "IO memory" (shared memory over the IO bus)
49 address 0 actually shows up as address 2 GB for any IO master.
135 This memory is called "PCI memory" or "shared memory" or "IO memory" or
176 OK, that just about covers the basics of accessing IO portably. Questions?
197 much in the actual IO accesses as in error handling and timeouts etc).
Dbcache.txt25 Since random IO is what SSDs excel at, there generally won't be much benefit
26 to caching large sequential IO. Bcache detects sequential IO and skips it;
27 it also keeps a rolling average of the IO sizes per task, and as long as the
28 average is above the cutoff it will skip all IO from that task - instead of
32 In the event of a data IO error on the flash it will try to recover by reading
110 Bcache tries to transparently handle IO errors to/from the cache device without
147 By default, bcache doesn't cache everything. It tries to skip sequential IO -
148 because you really want to be caching the random IO, and if you copy a 10
164 slower SSDs, many disks being cached by one SSD, or mostly sequential IO. So
232 A sequential IO will bypass the cache once it passes this threshold; the
[all …]
DIRQ-affinity.txt36 …44: 1068 1785 1785 1783 0 0 0 0 IO-A…
53 …44: 1068 1785 1785 1783 1784 1069 1070 1069 IO-A…
Dvgaarbiter.txt56 An IO state string is of the form {io,mem,io+mem,none}, mc and
130 be used. Then, the card is marked as locking these resources and the IO and/or
135 VGA memory and IO afaik). If the card already owns the resources, the function
Dsgi-ioc4.txt17 on a shipping IO card.
DIntel-IOMMU.txt16 IOVA - IO Virtual address.
DSubmitChecklist62 14: If the patch affects IO/Disk, etc: has been tested with and without
/linux-4.4.14/drivers/staging/vme/devices/
DKconfig19 slave card, implementing 32 solid-state relay switched IO lines, in
20 4 groups of 8. Each bank of IO lines is built to function as input,
/linux-4.4.14/Documentation/devicetree/bindings/x86/
Dce4100.txt6 Many of the "generic" devices like HPET or IO APIC have the ce4100
33 If the OS is using the IO-APIC for interrupt routing then the reported
/linux-4.4.14/Documentation/zh_CN/
Dio_ordering.txt27 设备寄存器或桥寄存器，触发IO芯片清刷未处理的写操作到达设备后才处理读操作，
66 在解决方案中，读取safe_register寄存器，触发IO芯片清刷未处理的写操作，
/linux-4.4.14/arch/arm/mach-iop32x/
DKconfig11 bool "Enable support for the IO-Data GLAN Tank"
14 NAS appliance or machines from IO-Data's HDL-Gxxx, HDL-GWxxx
/linux-4.4.14/Documentation/networking/
Dcs89x0.txt107 * 16 bytes of contiguous IO space available between 210h - 370h
216 This example loads the module and configures the adapter to use an IO port base
220 * io=### - specify IO address (200h-360h)
254 For example, to scan for an adapter located at IO base 0x300,
255 specify an IO address of 0x301.
410 * IO Register Read/Write Test
411 The IO Register Read/Write test insures that the CS8900/20 can be
412 accessed in IO mode, and that the IO base address is correct.
502 An IO conflict occurs when two or more adapter use the same ISA resource (IO
503 address, memory address or IRQ). You can usually detect an IO conflict in one
[all …]
Dcops.txt8 such as more IO ports. As this driver is tested it will
28 Use modprobe like this: /sbin/modprobe cops.o (IO #) (IRQ #)
29 If you do not specify any options the driver will try and use the IO = 0x240,
Ddm9000.txt89 Extra platform data for the DM9000 can describe the IO bus width to the
97 The IO should be done with 8bit operations.
101 The IO should be done with 16bit operations.
105 The IO should be done with 32bit operations.
/linux-4.4.14/Documentation/x86/x86_64/
Dboot-options.txt70 apic Use IO-APIC. Default
72 noapic Don't use the IO-APIC.
78 pirq=... See Documentation/x86/i386/IO-APIC.txt
82 no_timer_check Don't check the IO-APIC timer. This can work around
200 for IO (SWIOTLB)"
249 <pages> Prereserve that many 128K pages for the software IO
251 force Force all IO through the software TLB.
263 table itself in main memory. The smallest table, 64k, covers an IO
264 space of 32MB; the largest, 8MB table, can cover an IO space of
/linux-4.4.14/fs/f2fs/
DKconfig95 bool "F2FS IO tracer"
99 F2FS IO trace is based on a function trace, which gathers process
100 information and block IO patterns in the filesystem level.
/linux-4.4.14/firmware/cis/
DRS-COM-2P.cis.ihex9 # Replacement CIS for dual-serial-port IO card
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/
Dnfcmrvl.txt59 /* Reset IO */
83 /* Reset IO */
/linux-4.4.14/Documentation/usb/
Dcallbacks.txt71 particular interface. The device will not be suspended and you may do IO
81 You are not allowed any IO to a device after returning from this
88 to deal with failing IO even prior to the callback.
99 contains the interface passed as an argument. Cease IO, wait for all
Danchors.txt5 a driver to cease all IO to an interface. To do so, a
/linux-4.4.14/drivers/scsi/cxlflash/
DKconfig10 Allows CAPI Accelerated IO to Flash
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-pci-drivers-janz-cmodio6 Value representing the HEX switch S2 of the janz carrier board CMOD-IO or CAN-PCI2
Dsysfs-class-led25 You can change triggers in a similar manner to the way an IO
Dsysfs-memory-page-offline33 triggering IO errors if needed. Note this may kill
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-mcp23s08.txt53 those that have 16 IOs) have two IO banks: IO 0-7 form bank 1 and
54 IO 8-15 are bank 2. These chips have two different interrupt outputs:
Dgpio-mxs.txt7 GPIO ports share the same IO space with PIN controller, the GPIO node
/linux-4.4.14/Documentation/devicetree/bindings/power/
Drockchip-io-domain.txt1 Rockchip SRAM for IO Voltage Domains:
4 IO domain voltages on some Rockchip SoCs are variable but need to be
43 to report their voltage. The IO Voltage Domain for any non-specified
/linux-4.4.14/Documentation/scsi/
DNinjaSCSI.txt34 product info: "IO DATA", "CBSC16 ", "1"
79 card "WorkBit NinjaSCSI-32Bi (16bit) / IO-DATA"
80 version "IO DATA", "CBSC16 ", "1"
DChangeLog.sym53c8xx_256 - Add optionnal code that handles IO timeouts from the driver.
97 - Check pci dma mapping failures and complete the IO with some
141 - Use u_long instead of U32 for the IO base cookie. This is more
143 - Use MMIO per default for Power PC instead of some fake normal IO,
DChangeLog.megaraid_sas49 5. Set IO request timeout value provided by OS timeout for Tape devices.
144 IO.
382 (reduced interrupt operation). In this mode, IO completion
386 to prevent IO completion processing from being delayed
468 5. Performing diskdump while running IO in RHEL 4 was failing. Fixed.
478 i. Under heavy IO mid-layer prints "DRIVER_TIMEOUT" errors
481 previous release) to resume IO.
490 i. Under heavy IO mid-layer prints "DRIVER_TIMEOUT" errors
492 Fix: The driver is now throttling IO.
495 is 2 or greater,the driver stops sending cmd to FW temporarily. IO is
Din2000.txt83 inline code for IO writes. Made a few other changes and
159 sw1-3 sw1-4 IO port address (hex)
DChangeLog.megaraid396 i. Fix data corruption. Because of a typo in the driver, the IO packets
397 were wrongly shared by the ioctl path. This causes a whole IO command
518 IO module is loaded and then unloaded, followed by executing any
527 Also, during unregistration of the IO module, the resources are
Dncr53c8xx.txt197 named LOAD and STORE that allow to move up to 1 DWORD from/to an IO register
342 IO port address 0x6000, IRQ number 10
343 Using memory mapped IO at virtual address 0x282c000
569 suffers no performance loss with this option since all IO is memory
660 installs the sym53c8xx driver on all adapters except the one at IO port
661 address 0x1400 and then installs the ncr53c8xx driver to the adapter at IO
755 burst:255 get burst length from initial IO register settings.
1013 to be started, bit 1 of SCNTL1 IO register must be set when the chip is
1042 'bad reselections', etc... when using IARB on heavy IO load, you should not
1335 that contains some minimal comments on IO register bits.
Daic79xx.txt341 Definition: Set IO Cell precompensation value on a per-controller
355 Definition: Set IO Cell slew rate on a per-controller basis.
368 Definition: Set IO Cell signal amplitude on a per-controller basis.
/linux-4.4.14/arch/arm/mach-imx/
Dmm-imx1.c31 imx_map_entry(MX1, IO, MT_DEVICE),
/linux-4.4.14/Documentation/isdn/
DREADME.hfc-pci25 IO-address of the desired card.
27 There tree cards installed in your machine at IO-base addresses 0xd000, 0xd400
DREADME.act200010 The ISA-Bus Version uses 8 IO-ports. The base port address has to be set
/linux-4.4.14/sound/firewire/
DKconfig115 * Focusrite Saffire/Saffire LE/SaffirePro10 IO/SaffirePro26 IO
118 * M-Audio FireWire 1814/ProjectMix IO
/linux-4.4.14/Documentation/sound/alsa/soc/
Dcodec.txt13 2) Codec control IO - using RegMap API
65 2 - Codec control IO
69 Regmap API for all codec IO. Please see include/linux/regmap.h and existing
Dplatform.txt76 3) DMA IO to/from DSP buffers (if applicable)
Doverview.txt57 definition and codec IO functions. This class extends to BT, FM and MODEM
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt8 Persistent memory based storage is able to perform IO at byte (or more
152 A lane number is obtained at the start of any IO, and is used for indexing into
153 all the on-disk and in-memory data structures for the duration of the IO. If
163 a new IO, but the (slow) reader thread is still reading from it. In other words,
220 5. If TRIM flag set in map, return zeroes, and end IO (go to step 8)
221 6. If ERROR flag set in map, end IO with EIO (go to step 8)
262 Any block driver that supports byte granularity IO to the storage may register
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmicrel-ks8851.txt17 - vdd-io-supply: digital 1.8V IO supply for Ethernet mac
Dsmsc-lan91c111.txt10 - reg-io-width : Mask of sizes (in bytes) of the IO accesses that
Dsmsc911x.txt13 - reg-io-width : Specify the size (in bytes) of the IO accesses that
/linux-4.4.14/drivers/scsi/pcmcia/
DKconfig42 IO-DATA PCSC-FP
54 [I-O DATA (OEM) (version string: "IO DATA","CBSC16 ","1")]
/linux-4.4.14/Documentation/xtensa/
Dmmu.txt48 The default location of IO peripherals is above 0xf0000000. This may change
63 6. The IO area covers the entire 256MB segment of parent-bus-address; the
/linux-4.4.14/drivers/block/drbd/
DKconfig47 Say Y here if you want to simulate IO errors, in order to test DRBD's
50 The actual simulation of IO errors is done by writing 3 values to
/linux-4.4.14/drivers/usb/misc/
DKconfig180 tristate "IO Warrior driver support"
182 Say Y here if you want to support the IO Warrior devices from Code
184 IO Warrior 40
185 IO Warrior 24
186 IO Warrior 56
187 IO Warrior 24 Power Vampire
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dsbs_sbs-battery.txt9 IO failure.
/linux-4.4.14/Documentation/arm/
DPorting79 (In other words, you can't put IO mappings below TASK_SIZE, and
113 `pio' is the physical address of an 8MB region containing IO for
130 Machine specific function to map IO areas (including the debug
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsunxi-ir.txt9 - reg : should contain IO map address for IR.
/linux-4.4.14/Documentation/s390/
DDebugging390.txt13 390 IO in any detail. It is intended to complement the documents in the
30 s/390 & z/Architecture IO Overview
31 Debugging IO on s/390 & z/Architecture under VM
389 Thankfully because Linux doesn't have support for nested IO interrupts
1043 till a driver is open before you start tracing IO, but know in your
1053 TR IO 7c08-7c09 inst int run
1054 or whatever the IO channels you wish to trace are & hit b
1084 If you are running on a guest with several cpus & you have a IO related problem
1293 s/390 & z/Architecture IO Overview
1296 I am not going to give a course in 390 IO architecture as this would take me
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Des8328.txt10 - PVDD-supply : Regulator providing digital IO supply voltage 1.8 - 3.6V
Dtlv320aic32x4.txt9 "iov" - digital IO power supply
/linux-4.4.14/drivers/net/arcnet/
DKconfig83 tristate "ARCnet COM90xx (IO mapped) chipset driver"
86 IO-mapped mode instead of memory-mapped mode. This is slower than
97 time only using memory-mapped mode, and no IO ports at all. This
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,nsp.txt9 SATA and several other IO controllers.
/linux-4.4.14/drivers/power/avs/
DKconfig15 tristate "Rockchip IO domain support"
/linux-4.4.14/Documentation/vm/
Dpagemap.txt82 page is being locked for exclusive access, eg. by undergoing read/write IO
130 [IO related page flags]
131 1. ERROR IO error occurred
145 9. RECLAIM page will be reclaimed soon after its pageout IO completed
Dnuma10 or more CPUs, local memory, and/or IO buses. For brevity and to
29 away the cell containing the CPU or IO bus making the memory access is from the
48 CPUs, memory and/or IO buses. And, again, memory accesses to memory on
/linux-4.4.14/Documentation/devicetree/bindings/input/
Delants_i2c.txt18 - vccio-supply: a phandle for the regulator supplying IO power.
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dsm501fb.txt10 - Second entry: IO space (Display Controller register)
/linux-4.4.14/arch/cris/arch-v32/drivers/
DKconfig165 tristate "IO-processor hotplug firmware loading support"
169 Enables IO-processor hotplug firmware loading support.
179 tristate "MMC/SD host driver using IO-processor"
184 IO-Processor. Only the SPU is used in this implementation.
/linux-4.4.14/drivers/net/can/sja1000/
DKconfig99 PLD IO base addresses are read from jumpers JP1 and JP2,
101 SJA1000 IO base addresses are chosen heuristically (first that works).
/linux-4.4.14/drivers/parport/
DKconfig57 tristate "Multi-IO cards (parallel and serial)"
60 This adds support for multi-IO PCI cards that have parallel and
81 Saying Y here enables some probes for Super-IO chipsets in order to
/linux-4.4.14/Documentation/devicetree/bindings/arm/omap/
Dl4.txt17 - ranges : contains the IO map range for the bus
/linux-4.4.14/Documentation/accounting/
Ddelay-accounting.txt96 IO count delay total
112 IO count delay total
/linux-4.4.14/arch/powerpc/boot/dts/
Dep405.dts208 /* Outbound ranges, one memory and one IO,
210 * IO range but we don't use it for now
Dwalnut.dts215 /* Outbound ranges, one memory and one IO,
217 * IO range but we don't use it for now
Dkatmai.dts291 /* Outbound ranges, one memory and one IO,
335 /* Outbound ranges, one memory and one IO,
376 /* Outbound ranges, one memory and one IO,
417 /* Outbound ranges, one memory and one IO,
Dredwood.dts251 /* Outbound ranges, one memory and one IO,
292 /* Outbound ranges, one memory and one IO,
333 /* Outbound ranges, one memory and one IO,
Dhotfoot.dts269 /* Outbound ranges, one memory and one IO,
271 * IO range but we don't use it for now
Dsam440ep.dts278 /* Outbound ranges, one memory and one IO,
280 * IO range but we don't use it for now
Dbamboo.dts268 /* Outbound ranges, one memory and one IO,
270 * IO range but we don't use it for now
Dicon.dts301 /* Outbound ranges, one memory and one IO,
331 /* Outbound ranges, one memory and one IO,
372 /* Outbound ranges, one memory and one IO,
Dyosemite.dts311 /* Outbound ranges, one memory and one IO,
313 * IO range but we don't use it for now
Dpcm032.dts2 * phyCORE-MPC5200B-IO (pcm032) board Device Tree Source
Drainier.dts329 /* Outbound ranges, one memory and one IO,
331 * IO range but we don't use it for now
Dgef_sbc610.dts84 6 0 0xfd000000 0x00800000 // IO FPGA (8-bit)
85 7 0 0xfd800000 0x00800000>; // IO FPGA (32-bit)
Dgef_ppc9a.dts84 6 0 0xfd000000 0x00800000 // IO FPGA (8-bit)
85 7 0 0xfd800000 0x00800000>; // IO FPGA (32-bit)
Dxpedite5200.dts101 * 0: BRD_CFG0 (1: P14 IO present)
103 * 2: BRD_CFG2 (1: XMC IO present)
Dxpedite5200_xmon.dts105 * 0: BRD_CFG0 (1: P14 IO present)
107 * 2: BRD_CFG2 (1: XMC IO present)
Dsequoia.dts387 /* Outbound ranges, one memory and one IO,
389 * IO range but we don't use it for now
Dmakalu.dts284 /* Outbound ranges, one memory and one IO,
325 /* Outbound ranges, one memory and one IO,
Dcanyonlands.dts437 /* Outbound ranges, one memory and one IO,
468 /* Outbound ranges, one memory and one IO,
510 /* Outbound ranges, one memory and one IO,
Dglacier.dts474 /* Outbound ranges, one memory and one IO,
505 /* Outbound ranges, one memory and one IO,
547 /* Outbound ranges, one memory and one IO,
Dkilauea.dts338 /* Outbound ranges, one memory and one IO,
379 /* Outbound ranges, one memory and one IO,
/linux-4.4.14/Documentation/device-mapper/
Dthin-provisioning.txt132 If data space is exhausted the pool will either error or queue IO
134 space is exhausted or a metadata operation fails: the pool will error IO
142 transaction is aborted. Given that the pool will cache IO whose
143 completion may have already been acknowledged to upper IO layers
311 either queue or error the IO destined to the data device. The
312 default is to queue the IO until more space is added or the
Dlog-writes.txt4 This target takes 2 devices, one to pass all IO to normally, and one to log all
60 dev_path : Device that all of the IO will go to normally.
Dcache-policies.txt124 long time for the cache to adapt between varying IO patterns.
132 levels. This lets it adapt to new IO patterns very quickly.
Ddm-crypt.txt67 Perform encryption using the same cpu that IO was submitted on.
/linux-4.4.14/drivers/iio/imu/
DKconfig46 A set of IO helper functions for the Analog Devices ADIS* device family.
/linux-4.4.14/drivers/lightnvm/
DKconfig41 cost-based garbage collection. It is optimized for 4K IO sizes.
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmtk-sd.txt18 - vqmmc-supply: power to the IO
Dtmio_mmc.txt1 * Toshiba Mobile IO SD/MMC controller
/linux-4.4.14/arch/microblaze/
DKconfig165 space as well as some memory mapped IO. That means that, if you
166 have a large amount of physical memory and/or IO, not all of the
237 larger dma transfers increasing IO efficiency and reducing
/linux-4.4.14/arch/s390/kernel/
Dhead.S68 mvc 0x1f0(16),.Lnewpsw # set up IO interrupt psw
93 lctl %c6,%c6,.Lcr6 # set IO subclass mask
240 bas %r14,.Lirqwait # wait for IO interrupt
/linux-4.4.14/arch/arm/mach-pxa/include/mach/
Didp.h48 #error Your custom IO space is getting a bit large !!
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-mt6577.txt26 - mediatek,use-push-pull: IO config use push-pull mode.
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Dinfo.txt4 All but index, number of crypto threads and maximum IO size can changed via remount.
68 Change IO priority to 123 (node with the highest priority gets read requests).
Ddesign_notes.txt59 operations (like lookups or directory listings) between them according to IO priorities.
62 are connected with write permission turned on. IO priority and permissions can be changed in
/linux-4.4.14/Documentation/devicetree/bindings/iio/
Dst-sensors.txt15 VDD IO power to the sensor.
/linux-4.4.14/Documentation/i2c/busses/
Di2c-sis63045 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO]
/linux-4.4.14/arch/m68k/ifpsp060/
DCHANGES92 bit 15 = 1 (IO)
114 bit 15 = 0 (IO)
/linux-4.4.14/Documentation/filesystems/
Dproc.txt39 3.3 /proc/<pid>/io - Display the IO accounting fields
323 blkio_ticks time spent waiting for block IO
643 0: 1243498 1214548 IO-APIC-edge timer
644 1: 8949 8958 IO-APIC-edge keyboard
646 5: 11286 10161 IO-APIC-edge soundblaster
647 8: 1 0 IO-APIC-edge rtc
648 9: 27422 27407 IO-APIC-edge 3c503
649 12: 113645 113873 IO-APIC-edge PS/2 Mouse
651 14: 22491 24012 IO-APIC-edge ide0
652 15: 2183 2415 IO-APIC-edge ide1
[all …]
Dxfs-delayed-logging-design.txt72 minimise the impact of the log IO on transaction throughput.
81 buffers are full and under IO, then no more transactions can be committed until
84 IO permanently. Hence the XFS journalling subsystem can be considered to be IO
256 double linked list. Items are inserted into this list during log buffer IO
259 and then moved forward in the AIL when the log buffer IO completes for that
395 completion callback. Log IO completion will call that callback, which can then
706 <log buffer IO dispatched>
707 <log buffer IO completes>
719 <item IO completion>
763 <log buffer IO dispatched>
[all …]
Dxfs-self-describing-metadata.txt150 - immediately prior to write IO submission
163 that it should see, and the IO completion process verifies that the metadata
166 error (same as for IO errors), and if it needs to take special action due to a
181 into the object. Once this is done the write IO is allowed to continue. If any
324 metadata. Once this is done, we can issue the IO.
/linux-4.4.14/Documentation/devicetree/bindings/misc/
Dsram.txt3 Simple IO memory regions to be managed by the genalloc API.
/linux-4.4.14/Documentation/devicetree/bindings/net/can/
Dsja1000.txt15 - reg-io-width : Specify the size (in bytes) of the IO accesses that
/linux-4.4.14/Documentation/watchdog/
Dwdt.txt24 pass IO address and IRQ boot parameters. E.g.:
Dpcwd-watchdog.txt9 the Revision C card allows you to monitor any IO Port to automatically
/linux-4.4.14/Documentation/PCI/
Dpci.txt309 determine MMIO and IO Port resource availability _after_ calling
313 (for MMIO ranges) and request_region() (for IO Port ranges).
426 Disable device from responding to MMIO/IO Port addresses
427 Release MMIO/IO Port resource(s)
491 4.6 Disable Device from responding to MMIO/IO Port addresses
493 io_unmap() MMIO or IO Port resources and then call pci_disable_device().
498 4.7 Release MMIO/IO Port Resource(s)
500 Call pci_release_region() to mark the MMIO or IO Port range as available.
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
Dpwrap.txt8 optionally be encrypted. Also a non standard Dual IO SPI mode can be
/linux-4.4.14/Documentation/devicetree/bindings/serial/
D8250.txt35 - reg-io-width : the size (in bytes) of the IO accesses that should be
Dsnps-dw-apb-uart.txt24 - reg-io-width : the size (in bytes) of the IO accesses that should be
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dcros-ec.txt35 - reg: List of (IO address, size) pairs defining the interface uses
Dda9063.txt33 bio : BUCK IO
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DCPUfreq.txt64 The board needs to supply information about whether it needs the IO bank
/linux-4.4.14/Documentation/sound/alsa/
DREADME.maya4433 - all inputs/outputs on the M/IO/DIO extension card
37 *In particular, we would appreciate testing of these functions by anyone who has access to an M/IO/…
/linux-4.4.14/drivers/tty/
Drocket_int.h1118 #define sWriteTxByte(IO,DATA) sOutB(IO,DATA) argument
/linux-4.4.14/Documentation/x86/
Dpat.txt107 Note that this set of APIs only works with IO (non RAM) regions. If driver
121 combine areas of IO memory desired to remain uncacheable with areas where
/linux-4.4.14/arch/powerpc/platforms/83xx/
DKconfig49 into the PIB (Platform IO Board) board from Freescale which provide
/linux-4.4.14/arch/metag/
DKconfig83 space as well as some memory mapped IO. That means that, if you
84 have a large amount of physical memory and/or IO, not all of the
/linux-4.4.14/Documentation/ia64/
DIRQ-redir.txt41 IO-SAPIC interrupts are initialized with CPU#0 as their default target
/linux-4.4.14/drivers/video/fbdev/riva/
Dnv_driver.c337 par->riva.IO = (MISCin(par) & 0x01) ? 0x3D0 : 0x3B0; in riva_common_setup()
/linux-4.4.14/Documentation/trace/
Dmmiotrace.txt13 Mmiotrace was built for reverse engineering any memory-mapped IO device with
101 Access to hardware IO-memory is gained by mapping addresses from PCI bus by
/linux-4.4.14/sound/pci/
DKconfig295 referred to as NS CS5535 IO or AMD CS5535 IO companion in
422 tristate "(Echoaudio) Indigo IO"
426 Say 'Y' or 'M' to include support for Echoaudio Indigo IO.
674 tristate "Korg 1212 IO"
677 Say Y here to include support for Korg 1212IO soundcards.
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dxlnx,zynq-pinctrl.txt70 - io-standard: Configure the pin to use the selected IO standard according to
Dnvidia,tegra114-pinmux.txt20 - nvidia,io-reset: Integer. Reset the IO path. 0: no, 1: yes.
Dnvidia,tegra30-pinmux.txt18 - nvidia,io-reset: Integer. Reset the IO path. 0: no, 1: yes.
Dpinctrl-st.txt39 IO timing margins of external synchronous interfaces.
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS17 If this 64MB area overlaps the IO memory of the Bt848 you also have to
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dsrio.txt52 IO space utilized by the controller. This corresponds to the
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-dma.txt7 client modules like NETCP(Network Coprocessor), SRIO(Serial Rapid IO),
/linux-4.4.14/drivers/pci/
DKconfig110 to access more than one IO address space at the same time. To make
/linux-4.4.14/arch/um/
DKconfig.um97 This driver allows a host file to be used as emulated IO memory inside
/linux-4.4.14/drivers/w1/slaves/
DKconfig20 tristate "8-Channel Addressable Switch (IO Expander) 0x29 family support (DS2408)"
/linux-4.4.14/Documentation/video4linux/
DCARDLIST.em28xx66 65 -> IO-DATA GV-MVP/SZ (em2820/em2840) [04bb:0515]
/linux-4.4.14/Documentation/leds/
Dleds-class.txt27 You can change triggers in a similar manner to the way an IO scheduler
/linux-4.4.14/arch/arm/mach-bcm/
DKconfig50 NAND flash, SATA and several other IO controllers.
/linux-4.4.14/include/trace/events/
Dkvm.h12 ERSN(UNKNOWN), ERSN(EXCEPTION), ERSN(IO), ERSN(HYPERCALL), \
/linux-4.4.14/drivers/iommu/
DKconfig10 Say Y here if you want to compile device drivers for IO Memory
188 Supports Interrupt remapping for IO-APIC and MSI devices.
/linux-4.4.14/drivers/input/keyboard/
DKconfig26 tristate "ADP5588/87 I2C QWERTY Keypad and IO Expander"
36 tristate "ADP5585/ADP5589 I2C QWERTY Keypad and IO Expander"
224 for keys connected through TCA6416/TCA6408A IO expanders.
227 TCA6416/TCA6408A IO expander. Your board-specific setup logic

12