diff options
author | mav <mav@FreeBSD.org> | 2011-05-25 13:55:49 +0000 |
---|---|---|
committer | mav <mav@FreeBSD.org> | 2011-05-25 13:55:49 +0000 |
commit | ddcb287699d8c721f5ee3cd842206e477261d612 (patch) | |
tree | d7a62b5c971d72bfadd01b2a8d309adbe7494852 /usr.bin | |
parent | bd082ea669aca8f3e9ec34cd515f4aeef2d662a0 (diff) | |
download | FreeBSD-src-ddcb287699d8c721f5ee3cd842206e477261d612.zip FreeBSD-src-ddcb287699d8c721f5ee3cd842206e477261d612.tar.gz |
According to SATA specification, when Serial ATA Enclosure Management Bridge
(SEMB) is unable to communicate to Storage Enclosure Processor (SEP), in
response to hard and soft resets it should among other things return value
0x7F in Status register. The weird side is that it means DRQ bit set, which
tells that reset request is not completed. It would be fine if SEMB was the
only device on port. But if SEMB connected to PMP or built into it, it may
block access to other devices sharing same SATA port.
Make some tunings/fixes to soft-reset handling to workaround the issue:
- ahci(4): request CLO on the port after soft reset to ignore DRQ bit;
- siis(4): gracefully reinitialize port after soft reset timeout (hardware
doesn't detect reset request completion in this case);
- mvs(4): if PMP is used, send dummy soft-reset to the PMP port to make it
clear DRQ bit for us.
For now this makes quirks in ata_pmp.c, hiding SEMB ports of SiI3726/SiI4726
PMPs, less important. Further, if hardware permit, I hope to implement real
SEMB support.
Diffstat (limited to 'usr.bin')
0 files changed, 0 insertions, 0 deletions