Home
last modified time | relevance | path

Searched refs:DIO (Results 1 – 17 of 17) sorted by relevance

/openbmc/qemu/tests/qtest/
H A Dfdc-test.c63 DIO = 0x40, enumerator
85 assert_bit_clear(msr, DIO); in floppy_send()
95 assert_bit_set(msr, RQM | DIO); in floppy_recv()
204 if (msr == (BUSY | NONDMA | DIO | RQM)) { in send_read_no_dma_command()
217 assert_bit_set(msr, BUSY | RQM | DIO); in send_read_no_dma_command()
222 assert_bit_set(msr, BUSY | RQM | DIO); in send_read_no_dma_command()
240 assert_bit_clear(msr, BUSY | DIO); in send_read_no_dma_command()
436 assert_bit_set(msr, BUSY | RQM | DIO); in test_read_id()
479 assert_bit_set(msr, BUSY | RQM | DIO); in test_read_id()
/openbmc/linux/arch/m68k/
H A DKconfig.bus6 config DIO config
7 bool "DIO bus support"
11 Say Y here to enable support for the "DIO" expansion bus used in
H A DKconfig.devices109 depends on DIO && SERIAL_8250
/openbmc/linux/drivers/comedi/
H A DKconfig111 tristate "Advantech PCL-722/724/731 and ADlink ACL-7122/7124/PET-48DIO"
124 ADlink PET-48DIO 48 channels
126 Diamond Systems ONYX-MM-DIO 48 channels (PC/104)
150 ICP P8R8-DIO iso - 8 in/8 out
152 ICP P16R16-DIO iso - 16 in/16 out
209 PC272E ISA DIO boards
215 tristate "Amplicon PC36AT DIO board support"
218 Enable support for Amplicon PC36AT ISA DIO board.
584 National Instruments - PCI-DIO-96, PCI-DIO-96B, PXI-6508, PCI-6503,
775 tristate "Advantech PCI DIO card support"
[all …]
/openbmc/linux/Documentation/gpu/amdgpu/display/
H A Ddcn-overview.rst32 * **Display Output (DIO)**: Codify the output to the display connected to our
78 we have dc_stream, and the output (DIO) is handled by dc_link. Keep in mind
97 * DIO (DP/HDMI stream encoder and link encoder)
125 Eventually, we output data in integer format at DIO.
160 we have just a single **pipeline** where the data flows from DCHUB to DIO, as
H A Ddc-glossary.rst88 DIO
/openbmc/linux/drivers/net/ethernet/amd/
H A DKconfig9 depends on DIO || MACH_DECSTATION || MVME147 || ATARI || SUN3 || \
98 depends on DIO
/openbmc/linux/Documentation/sound/cards/
H A Dmaya44.rst41 - all inputs/outputs on the M/IO/DIO extension card
45 …ould appreciate testing of these functions by anyone who has access to an M/IO/DIO extension card.*
/openbmc/linux/Documentation/filesystems/caching/
H A Dnetfs-api.rst380 competing DIO writes to the same storage in the cache.
414 but it does have to align to DIO boundaries on the backing filesystem). The
443 page to say that a DIO write is underway from that page::
H A Dfscache.rst135 * Data I/O is done by asynchronous DIO to/from a buffer described by the
/openbmc/linux/Documentation/core-api/
H A Dpin_user_pages.rst131 CASE 1: Direct IO (DIO)
134 as DIO buffers. These buffers are needed for a relatively short time (so they
/openbmc/linux/drivers/gpio/
H A DKconfig674 tristate "TS-4800 DIO blocks and compatibles"
865 tristate "ACCES 104-DIO-48E GPIO support"
874 Enables GPIO support for the ACCES 104-DIO-48E series (104-DIO-48E,
875 104-DIO-24E). The base port addresses for the devices may be
982 tristate "TS-5500 DIO blocks and compatibles"
/openbmc/linux/drivers/eisa/
H A Deisa.ids683 ICU0680 "DFI DIO-500 Serial/Parallel I/O Card"
684 ICU0681 "DFI DIO-200 Serial/Parallel I/O Card"
1118 NIC0301 "AT-DIO-32F Digital I/O Board"
1119 NIC0400 "PC-DIO-24 Digital I/O Board"
1122 NIC0700 "PC-DIO-96 Digital I/O Board"
/openbmc/linux/Documentation/filesystems/
H A Dnetfs_library.rst433 * The cache may need to skip holes that it can't do DIO from.
446 * Any folios that need writing to the cache will then have DIO writes issued.
/openbmc/linux/Documentation/admin-guide/
H A Dext4.rst372 Controls whether or not ext4 should use the DIO read locking. If the
/openbmc/linux/drivers/video/fbdev/
H A DKconfig407 depends on (FB = y) && DIO
/openbmc/linux/
H A DMAINTAINERS215 ACCES 104-DIO-48E GPIO DRIVER