Home
last modified time | relevance | path

Searched refs:DRQ (Results 1 – 4 of 4) sorted by relevance

/openbmc/qemu/tests/qtest/
H A Dide-test.c69 DRQ = 0x08, enumerator
633 assert_bit_set(data, DRDY | DRQ); in test_identify()
641 assert_bit_clear(data, BSY | DF | ERR | DRQ); in test_identify()
756 assert_bit_clear(data, DF | ERR | DRQ); in test_flush()
770 assert_bit_clear(data, BSY | DF | ERR | DRQ); in test_flush()
804 assert_bit_clear(data, DF | ERR | DRQ); in test_pci_retry_flush()
820 assert_bit_clear(data, BSY | DF | ERR | DRQ); in test_pci_retry_flush()
987 assert_bit_set(data, DRQ | DRDY); in cdrom_pio_impl()
1010 assert_bit_set(data, DRQ | DRDY); in cdrom_pio_impl()
1024 data = ide_wait_clear(qts, DRQ); in cdrom_pio_impl()
[all …]
/openbmc/linux/Documentation/driver-api/dmaengine/
H A Dprovider.rst21 will want to start a transfer, it will assert a DMA request (DRQ) by
65 and whenever a DRQ will be asserted, it will go through the collection
75 The one last thing is that usually, slave devices won't issue DRQ by
/openbmc/linux/Documentation/driver-api/
H A Dlibata.rst634 - ATA_STATUS doesn't contain !BSY && DRDY && !DRQ while trying to
637 - !BSY && !DRQ during PIO data transfer.
639 - DRQ on command completion.
/openbmc/linux/Documentation/userspace-api/ioctl/
H A Dhdio.rst455 DRQ when interrupting for the command, NSECTOR * 512 bytes