summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/libsas/sas_event.c
diff options
context:
space:
mode:
authorDan Williams <dan.j.williams@intel.com>2011-11-30 23:23:33 -0800
committerJames Bottomley <JBottomley@Parallels.com>2012-02-19 14:09:32 -0600
commitb52df4174dff7e587f6fbfb21e3c2cb57109e5cf (patch)
tree1e53cb4a62519dda60babc240bbd3b7f69c5b1f4 /drivers/scsi/libsas/sas_event.c
parent3a2cdf391b62919d3d2862cdce3d70b9a7a99673 (diff)
downloadtalos-obmc-linux-b52df4174dff7e587f6fbfb21e3c2cb57109e5cf.tar.gz
talos-obmc-linux-b52df4174dff7e587f6fbfb21e3c2cb57109e5cf.zip
[SCSI] libsas: use libata-eh-reset for sata rediscovery fis transmit failures
Since sata devices can take several seconds to recover the link on reset the 0.5 seconds that libsas currently waits may not be enough. Instead if we are rediscovering a phy that was previously attached to a sata device let libata handle any resets to encourage the device to transmit the initial fis. Once sas_ata_hard_reset() and lldds learn how to honor 'deadline' libsas should stop encountering phys in an intermediate state, until then this will loop until the fis is transmitted or ->attached_sas_addr gets cleared, but in the more likely initial discovery case we keep existing behavior. Signed-off-by: Dan Williams <dan.j.williams@intel.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'drivers/scsi/libsas/sas_event.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud