diff options
| author |   Tejun Heo <htejun@gmail.com> | 2008-05-19 01:15:09 +0900 |
|---|---|---|
| committer |   Jeff Garzik <jgarzik@redhat.com> | 2008-05-19 17:51:47 -0400 |
| commit | e0614db2a398d4d0dc5fb47fe2c2783141262a3e (patch) | |
| tree | 57723d4765f04821c47e3e0859d90fc5d9ab51bc /include/linux/libata.h | |
| parent | libata: kill hotplug related race condition (diff) | |
| download | linux-dev-e0614db2a398d4d0dc5fb47fe2c2783141262a3e.tar.xz linux-dev-e0614db2a398d4d0dc5fb47fe2c2783141262a3e.zip | |
libata: ignore recovered PHY errors
No reason to get overzealous about recovered comm and data errors.
Some PHYs habitually sets them w/o no good reason and being draconian
about these soft error conditions doesn't seem to help anybody.
If need ever rises, we might need to add soft PHY error condition, say
AC_ERR_MAYBE_ATA_BUS and use it only to determine whether speed down
is necessary but I don't think that's very likely to happen. It's far
more likely we'll get timeouts or fatal transmission errors if
recovered errors are so prominent that they hamper operation.
Signed-off-by: Tejun Heo <htejun@gmail.com>
Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
Diffstat (limited to 'include/linux/libata.h')
0 files changed, 0 insertions, 0 deletions